Enterprise Product Design
Designing complex support and analytics experiences that help network teams understand issues faster and make better decisions.
The problem
Support environments bring together dense technical information, changing conditions and multiple paths to resolution. The design challenge was to make that complexity easier to navigate without removing important context.
The solution
When information is fragmented or presented with equal weight, people spend more effort interpreting the interface before they can begin solving the problem.
Background
Support environments bring together dense technical information, changing conditions and multiple paths to resolution. The design challenge was to make that complexity easier to navigate without removing important context.
When information is fragmented or presented with equal weight, people spend more effort interpreting the interface before they can begin solving the problem.
My role
Research
The process brought together available product context, research artifacts, journey thinking and usability observations to identify where clarity mattered most.
Research synthesis
Identifying recurring pain points and opportunities.
Journey mapping
Connecting information needs across the experience.
Early concepts
Making assumptions visible enough to discuss and test.
Research insights
Define
Help users quickly understand important support insights and confidently decide what to do next?
Ideation
A broad overview before moving into detail.
A guided path organized around key tasks.
Prioritized signals connected to context and action.
Design direction: The final approach combines a useful overview with insight-led paths, balancing orientation and action.
Design
Create a clear hierarchy around the insights most relevant to the current situation.
Let people move naturally from understanding an issue to investigating it.
Group related information into sections that can be understood at a glance.
Improve the experience while maintaining consistency with the established product language.
From wireframes to high-fidelity
Final design
Testing & iterations
Concepts were evaluated around task flow, navigation and comprehension. The examples below describe qualitative design iterations rather than unverified results.
Dense summaries made scanning harder than expected.
The hierarchy was simplified and secondary detail moved into progressive layers.
Insight labels alone did not provide enough context.
Supporting explanation and next actions were brought closer to each insight.
Before / After
Impact
Clearer information hierarchy
More intuitive paths through complex support information
Stronger alignment between user needs and product goals
Final thoughts
The strongest simplification comes from understanding which decisions people need to make—not from removing detail indiscriminately.
I would continue exploring how adaptive explanations could support different levels of technical expertise.
I’m most proud of creating structure around a complex domain while respecting the depth experts need.
Next project
