Research
Defined a representative user and mapped the questions, frustrations and decision points involved in selecting a robotic system.
← Selected work
Industrial UX + Information Architecture
Making Industrial Automation Products Easier to Find and Compare
Reframed a deep robotics and automation catalog around user goals, clearer navigation and reusable responsive templates spanning discovery, product landing and product detail.
09RoleUX Strategy + Product Design
TeamBusiness, content, product and technology stakeholders
ScopePersona, journey, sitemap, navigation, responsive templates and product UX
Research ledPersona and journey foundation
Deep catalogRobotics and automation content
ResponsiveDesktop and mobile structures
ReusableTemplate and component strategy
DESIGN EVIDENCE
The work, in the order it was designed.
The work is sequenced from research through information architecture, wireframes and final responsive product screens.
01
Research foundation
Persona and journey work clarified how technical buyers evaluated complex robotics and automation products.
02
Navigation and information architecture
The sitemap, menu system and page templates reorganized a deep product ecosystem around user decisions.
03
Wireframes
Responsive wireframes established page hierarchy and behavior before visual design.
04
Final responsive product
Desktop and mobile screens translated the architecture into a coherent industrial product experience.
THE BUSINESS PROBLEM
Technical depth was valuable, but the product ecosystem had to become easier to navigate.
Industrial buyers, engineers and integrators often arrive with different levels of knowledge. Some know the exact product family they need, while others are still trying to understand which robotic system fits an application.
The experience needed to support both behaviors without flattening the technical information that makes a complex B2B purchase possible.
MY MANDATE
Own the experience, not just the screens.
The work connected user understanding to the structure of the site. Persona and journey artifacts informed the sitemap, menu system, responsive templates and detailed product experiences, creating a consistent path from broad exploration to technical evaluation.
HOW THE WORK MOVED
Research translated into decisions teams could build from.
Architect
Reorganized the sitemap and primary navigation around applications, products, services, education and support.
Systematize
Created reusable page templates and responsive structures so content teams could scale the experience consistently.
Design
Translated the system into desktop and mobile home pages, product landings and product-detail experiences.
OUTCOME
The design system connected discovery, education and product evaluation.
The resulting architecture made it easier to move from a broad automation need to relevant products and supporting information. Reusable templates also gave the organization a more consistent foundation for maintaining a large, technical content ecosystem across screen sizes.
REFLECTION
For technical products, simplification does not mean removing detail. It means helping the right person reach the right level of detail at the right time.