← Complex requirements to product direction
From expertise to product behaviour

Turn specialist knowledge into a product workflow

Regulation and domain expertise rarely arrive in the order a user needs them. The product work is to preserve what must remain true while turning it into decisions, steps, evidence and exceptions people can use.

Short answer

Model the decisions before drawing the screens

Start with sources, actors, obligations and evidence. Make the decision logic and exceptions explicit, then shape the sequence a user can follow and test it with the people who understand the domain.

The translation method

Move from source material to observable product behaviour

The sequence keeps specialist truth connected to the experience without copying the source document into the interface.

01

Establish the source of truth

Separate binding requirements, customer evidence, internal policy, interpretation and preference. Record contradictions rather than silently choosing between them.

02

Model the decision logic

Identify actors, inputs, thresholds, dependencies, permissions, evidence and outputs. Show where judgement is required and who has authority.

03

Shape the usable sequence

Group decisions into a journey people can understand. Keep the main route simple without hiding material exceptions or compliance conditions.

04

Test and trace the result

Review worked examples, prototypes and acceptance criteria with specialists and delivery teams. Link important behaviour back to its source or decision.

The difficult distinctions

Not every statement carries the same authority

Treating all source material as equivalent makes the product harder to challenge, change and verify.

  • A regulation or contract states what must be true; it may not prescribe the best user experience.
  • A specialist interpretation explains how the rule works in practice; it should remain attributable and reviewable.
  • A product decision chooses how the workflow will respond; record the owner and the alternatives considered.
  • An assumption is a gap in evidence, not a settled requirement. Give it a test, owner and decision point.
What the product model needs

Capture enough structure to explain normal and exceptional work

The useful output is not a simplified summary of the source material. It is a model that lets product, design, engineering, QA and domain specialists discuss the same expected behaviour.

Actors and authority

State who starts the work, who provides evidence, who can edit or approve it, and where responsibility moves between people or organisations.

Inputs and evidence

Define the information the workflow needs, its source, acceptable formats, validation rules and what should happen when evidence is missing or contradictory.

Rules and decisions

Describe thresholds, calculations, branching conditions and specialist judgement separately. A formula and a professional interpretation should not look like the same kind of rule.

States, exceptions and recovery

Cover incomplete, invalid, disputed and failed routes as deliberately as the happy path. Explain how the user can recover and when the work must leave the automated flow.

Outputs and acceptance

Make the expected result observable: a decision, submission, report, approval, next task or audit trail. Define what evidence would show that the workflow behaved correctly.

Keep specialists close without making them the interface

Specialists should review the interpretation, examples and conditions that carry real risk. They should not have to translate the same rule from scratch in every product conversation. A traceable model lets them challenge what matters while the wider team works from a shared explanation.

Choose the artefact by the next decision

A workflow model may be enough to resolve the logic. A prototype helps test whether the sequence makes sense. A PRD or detailed specification preserves the agreed behaviour through delivery. The comparison between a prototype, PRD and full specification can help decide what the handover needs next.

Next step

Bring the source material and the decision it needs to support

A regulation, spreadsheet, policy, customer workflow or unresolved interpretation is enough to start.