Vidhisha KediaPrioritize the working context
Group information around the task rather than treating every detail as equally prominent.
TEKION · ENTERPRISE SAAS
Designing for clarity in complex workflows
My work as a Senior Product Designer in automotive software.
- YEAR
- 2022 to 2023
- ROLE
- Senior Product Designer
- PLATFORM
- Enterprise SaaS
THE BRIEF
Make complex work feel familiar
Dealership teams work with detailed information and time sensitive tasks. A major part of the challenge was designing for an older user group accustomed to straightforward, established software patterns.
The goal was not to make the product look novel. It was to make the work easier to understand and complete, using the familiarity of classic Microsoft Office style layouts as a reference.
MY APPROACH
Build on familiar ways of working
I worked with product and engineering to understand workflow requirements, organize information and explore clearer interactions. I prioritized explicit labels, readable hierarchy and predictable controls over unfamiliar interaction patterns.
Familiarity was a design constraint, not an assumption about age. The aim was to respect existing habits while reducing unnecessary effort.
THE USER
User persona
Mark Bennett
About
An experienced parts professional balancing customer requests, stock information and accurate order preparation. Values familiar, straightforward software patterns.
Goals
- Find relevant information quickly.
- Complete routine work efficiently and accurately.
- Use clear controls without relearning established habits.
Frustrations
- Information scattered across the task.
- Unclear labels or unexpected control behaviour.
- Unfamiliar interactions that interrupt routine work.
DESIGN PRIORITIES
Familiarity, clarity and continuity
Familiarity
Build on recognizable desktop software patterns.
Use explicit labels and predictable controls.
Clarity
Make the information hierarchy easy to scan.
Keep related details and actions together.
Continuity
Keep relevant task context within reach.
Support efficient repetition without surprises.
INTERACTION PRINCIPLE
Keep the task connected
- UnderstandEstablish the task and its context.
- ActKeep relevant information available during the work.
- ReviewMake the next action and completion state clear.
DESIGN DECISIONS
Clarity comes from structure
Respect experienced users
Balance discoverability with efficient repetition and predictable interactions.
Design beyond the main path
Consider states, exceptions and documentation alongside the core interaction.
DELIVERY
Carry the intent into implementation
My contribution included interface design, UX writing, documentation and collaboration with product and engineering. I also supported junior designers.
LEARNINGS
Simplify the effort, not the expertise
Complex products do not always need less information. They need a clearer structure that helps people find what matters at the right moment.
This work reinforced the importance of balancing visual clarity with operational depth, and involving product and engineering in the decisions that shape both.