William Bruno
← Back to work

Cognex

Verndale · 2024–2025 · Senior Experience Designer

A multi-property redesign built around how buyers actually search, unifying cognex.com marketing, MyCognex support, and the information architecture connecting them — now live in production.

Redesigned cognex.com homepage on a MacBook

Everyone typed a model number. So search became the front door.

Background

Cognex’s marketing, support, and product catalog lived in separate properties that didn’t agree with each other. The catalog is too large for any buyer to remember.

Factory operators and procurement engineers search by model number. The site made them browse like consumers.

cognex.com

The marketing site and product catalog, redesigned around how buyers actually search.

MyCognex support

The support hub, which shipped essentially one-to-one with the designs.

My role

I helped lead a multi-property redesign built around how buyers actually search, unifying cognex.com marketing, MyCognex support, and the information architecture connecting them.

Tested in four languages. The same answer every time.

Moderated testing in English, Japanese, Mandarin, and Korean showed the same pattern every time: users went straight to the search bar, typed “DM375,” and judged us by the results. Many ignored the navigation we thought was most important.

Users called the old account profile “wasted space.” They wanted a description and a date before downloading a large file. Most came for documentation and drawings, so that is what we designed for.

Cognex header search with model-number autocomplete and product suggestions
Search treats a model number like a destination and takes you straight there.

A guided path from product type to the exact download.

Few users touched the filters, so we couldn’t rely on them for discovery. The Product Finder steps users from product type to the exact file, showing type and size before the click, with a path for discontinued products.

This is the live, working version. Pick a category and try it.

The mega-nav stayed, and earned its keep.

It would have been easier to remove the navigation. Instead we made it more useful: a Product Finder entry point in Products, applications organized the way people think, and articles inside the menus, not just links.

Support moved onto the product itself. Contact Sales, Download Data Sheet, and View Product Support sit at the top of complex pages, designed to answer questions before they become tickets.

Redesigned Cognex desktop mega-navigation
The nav serves two audiences at once, so products are organized the way engineers spec them, not the way marketing names them.
Cognex application detail page with top-of-page support actions
Specs, downloads, and a path to support on one screen.
Cognex applications listing filterable by function and industry
Applications framed by the problem being solved on the factory floor.

Search-first, everywhere.

The MyCognex hub starts with a search and adapts to each user. Members see their registered products, open cases, and favorites. Everyone else sees popular and recent resources.

The shipped hub matched the designs essentially one-to-one.

Shipped MyCognex support hub
Support starts from the product, not from a ticket form, because most questions are really questions about a specific model.
Cognex global support search results
A model number is a destination.
Logged-out support hub leading with search
The same pattern carries into MyCognex.
Resource listing with file type, size, and date columns
Every row: what it is, what it does, what next.

Three directions, one chosen.

The visual system reads beams of light as color gradients over black, white, and Cognex yellow. The direction was tested with real users, from category newcomers to automation experts.

Concept 1, clean and airy
Concept 1: clean & airy.
Concept 2, dark and restrained
Concept 2: dark & restrained.
Concept 3, bold and disruptive
Concept 3: bold & disruptive.
The approved direction, concept 3 dark
The approved direction: concept 3 dark, client-signed 07.11.2024.

A visual language, built into a component library.

One visual language with two very different jobs: factory operators on cognex.com, procurement engineers inside MyCognex. I helped define the system and turn it into a documented library both properties share.

Cognex component library board
The component library.
Cognex graphics and components in context
Graphics & components in context.

Most users skipped the navigation we worked hard on. We designed for that too.

We kept the mega-nav for people who browse, and made search and the guided Product Finder the main tools for everyone else.

We also prototyped an AI assistant, ai12z, for vague queries like “I bought one, but can’t remember the name.”

The ai12z AI assistant concept on the support home
An answer engine for users who don’t have a perfect search term.

Outcome

Live at cognex.com and support.cognex.com. A clearer path from discovery to support, with engineering, marketing, and customer success working from one system.

Live

two sites shipped — cognex.com and support.cognex.com, in production.

4

languages — English, Japanese, Mandarin, Korean prototypes and scripts.

~12

interviews per topic — moderated sessions across four core experiences.

1:1

design to ship — the support hub shipped essentially one-to-one with the designs.

The calls that shaped it

Designed for search-first, not nav-first.

Users typed model numbers before touching navigation. Search and the Product Finder became the main tools of both sites.

Put support on the product, not three clicks away.

Product pages lead with the support path, the datasheet, and a jump-to nav, heading off tickets before they start.

Cut the wasted space, lead with what’s useful.

The hub now opens with personalized, popular, and recently updated resources, adapting to the signed-in user.

Next project CDM Smith →

Let’s make something work.

Boston & remote · Open to full-time & contract

will.a.bruno@gmail.com