One problem. Two design directions. Which would you choose?
For AEGIS / 001.05 . Traffic Operations, we explored two approaches to the same challenge: helping city operators understand congestion, incidents and network-wide disruptions without overwhelming them with information.
Both solve the same operational problem. Different approaches to hierarchy and interaction.
If you were behind the control desk . Option A or Option B?
I’ve been working on a concept called Respira, focused on making breathing and recovery data feel easier to understand and less clinical.
The main challenge was not the visuals. It was deciding what the user should understand first. So I structured the experience around three things: current recovery, supporting health signals, and the next action. Recovery stays central, secondary metrics remain easy to scan, and the guided breathing session is always close enough to act on.
The interface and motion were created in Figma, with a lot of attention on hierarchy, data visualisation, component behaviour and micro-interactions. The goal was to make the product feel calm, responsive and useful, not just visually polished.
I’m sharing a short video of the interaction here. Would be interested to know which part of the experience stands out to you most.