Project overview
Translating sensor signals into a user-friendly product
How should user use it?
The scenario
When an alert goes off in a bakery's back kitchen, it means a lot of things at once.
Delays in reaching alerts lead to slower responses and unresolved issues.
Solution direction
How might we unify scattered alert workflows into a system that works across teams and devices?
Design challenge
Defining a mobile dashboard for quick decisions
Team challenge
Reaching alignment between team reorg
The project also underwent several phases where mobile and desktop designs were owned by two different teams, each addressing unique user requirements. To stay aligned, I led weekly check-ins with other designers, conducted screen-by-screen reviews and walkthroughs with engineers.
Re-mapping IA
Reviews with PM & Engineer
My contributions at a glance
Balancing systems thinking and UI polishment
My takeaways
1) Team collaboration
Maintain an active communication channel with engineers
As someone new to sensor management, I've had many struggles early on when firmware engineers' explanations left me puzzled. Framing my own understanding via workflow mapping and asking about feasibility helped me build clarity .
2) Design flexibility
Prepare to design for multiple scenarios
Hardware can run into tech issues. Whether a sensor fails to pair, is offline, or syncs late, I have to account for edge cases to ensure the interface accounted for these realities. I gradually learn to think ahead, prioritize key user flow, but also include other options to support troubleshooting.