Hundreds of options, one fluid experience across screen sizes
Rolls Royce
2025
Overview
Approach
Using Structure to Align Teams and Decisions
To reduce ambiguity, I created a lightweight product requirements document that gathered features, components, user stories, and success signals in one place. This wasn’t about process overhead, but about giving the team a shared mental model.
That structure helped surface grey areas early, supported better trade-off discussions, and kept design, development, and brand conversations grounded in the same reality.
Design direction
I set up continuous syncs with the brand team to validate that design decisions stayed true to quality expectations, even as constraints shifted. This avoided late-stage rework and helped the team move faster with more confidence.
Documentation played a key role here, allowing us to zoom out or dive into detail without losing alignment.
Outcome
Key results
I clarified product requirements and success signals, it contributed to reduce time for teams to make decisions with fewer open questions, it also reduced friction despite complexity
I redesigned the confuguration experience around orientation and continuity, according to client feedback, users were more likely to complete the configurator journey, exploration felt manageable, not overwhelming
Back to Home