Balancing Complexity for Engineers
Lead UX
Designer
Introduction
In 2023, I led the design of two new Simulink applications (Feature Modeling & Authoring Apps) that challenged my outlook of UX. Traditionally, my focus was on making interfaces intuitive and visually appealing. However, designing for engineers (highly precise thinkers) required a different approach.
Instead of prioritizing minimalism, I needed to create tools that were functionally robust and seamlessly integrated into users complex workflows.
Our team at MathWorks set out to design the modeling environment engineers use for system design and simulation…
Challenge
Our users, including those at Bosch and Cummins, struggled with the limitations of existing UML diagramming tools, often cluttered and requiring extensive training.
These users needed a tool to create and maintain “product lines” or a set of all possible features, parameters, requirements, assets, and constraints that together create a high-level collection of the parts of a system
The challenge: how could we design a tool that was powerful yet easy to navigate?
Before designing, we conducted user interviews and contextual inquires to observe workflows. I led a kick-off with PMs and developers that helped define the challenges and opportunities for this project.
Cluttered interfaces
made data hard to interpret
Rigid workflows
slowed down efficiency
Limited customization
restricted usability
Steep learning curves
extensive documentation
Key User Metrics (Attitudinal & Behavioral):
Qualititative
"I can’t find what I need without clicking through multiple menus."
Quantitative
60% requested better feature organization for faster workflows.
Quantitative
40% of engineers spent extra time navigating instead of designing.
Quantitative
100% of engineers agreed that they would benefit from a streamlined modeling and authoring tool for complex system designing.
Qualitative
"There’s too much information, but I don’t want to lose depth."
Qualitative
"This takes so long to load I leave and go make myself a cup of coffee and it still hasn't loaded"
Who is this for and how is it being used?
Product Line Engineer
Create and manage a feature
model which can be used to
create various catalogs/variations of the same solution type.
Build an application/product based on a set of features. This catalog is used for testing, feasibility, analysis, etc.
Component Engineer
to develop and test reusable components. These components are key parts of a feature solution.
Feature Model: a high-level model of all the possible parts and characteristics that build a general type of system (ex. Water filtration system model not a specific type like Hospital Water Filtration System)
Feature Catalog: a hierarchical collection used to organize all the parts of a specific model (ex: parts of a Water Filtration System)
Toolstrip framework
for easy navigation and task completion
Working area
for multi-document support for seamless workflow
Essential controls
that display essential information & actions for better decision-making
Customizable catalogs
to streamline engineering workflows
Sketching a shared vission
I facilitated cross-functional sketching sessions using Miro, involving designers, engineers, and product managers. We:
Mapped pain points and feature priorities.
Used dot voting & affinity diagrams to identify key functionalities.
Debated trade-offs between simplicity and technical depth.
Ideation & Design
Our initial research helped me create a prioritized list of requirements for the products including:
Engineers needed all critical data visible upfront but in an organized structure.
UI elements should be designed to support, not obscure, complexity.
The tool needed to be adaptive to different expertise levels.
