Establish what was true before deciding what to build
The first task was not writing tickets or redrawing the prototype. It was reconciling regulation, specialist practice, customer expectations and commercial constraints so the team could see which decisions were fixed, which were product choices and which still needed evidence.
1. Reconstruct the current workflow
The consultancy spreadsheets showed how the service worked in practice, including information requests, calculations, professional judgement and outputs. That working process was compared with the source requirements rather than treated as the specification by default.
2. Separate compliance logic from experience design
Each important rule was traced to its source or interpretation. Product choices—such as sequence, language, progressive disclosure and where to ask for evidence—could then be challenged without losing the underlying obligation.
3. Shape and review a demonstrable journey
The product model became a working prototype that specialists, commercial stakeholders and delivery teams could review. The prototype made the sequence concrete; the specification carried the rules and exceptions a visual could not reliably hold.
4. Leave a buildable source of truth
The handover connected product flows, source decisions, expected behaviour, open questions, QA criteria and implementation scope. Engineering could work from the documentation without reconstructing the domain logic from meetings and spreadsheets.
What changed
In six weeks, the team moved from a spreadsheet-heavy consultancy process to a demo-ready product direction with clear documentation, a working prototype and implementation scope. It supported more than 20 client and partner demonstrations, while the specifications became the basis for engineering work.
Why this example matters
The difficult part was not turning a spreadsheet into screens. It was making the domain decisions visible enough for specialists to verify, commercial teams to explain and engineering teams to build. The same pattern applies wherever product work crosses regulation, data, professional judgement or complicated operational reality.
The reusable method
The companion guide explains how to turn specialist knowledge into a product workflow. The build-ready requirements test shows what the handover needs before development starts.