← Complex requirements to product direction
Choosing the product artefact

Prototype, PRD or full specification?

These artefacts answer different questions. Choose the smallest combination that helps the team make the next decision without hiding material product logic or delivery risk.

Short answer

Start with the decision, not the document name

Use a prototype to make an experience concrete, a PRD to align the problem and product direction, and a detailed specification when rules, exceptions and acceptance conditions must survive the handover.

What each artefact does

Use the format that exposes the next uncertainty

The useful distinction is the job the artefact performs, not how polished it looks.

Prototype

Test the experience and direction

Use a prototype to explore a flow, make an interaction discussable and learn whether people understand or value the proposed response.

PRD

Align the problem, scope and outcome

Use a PRD to connect evidence, intended users, product decisions, boundaries and success criteria around one coherent direction.

Detailed specification

Preserve behaviour through delivery

Use a specification when rules, permissions, states, exceptions, data and acceptance conditions must be explicit enough to build and verify.

What each one misses

No single artefact removes every kind of uncertainty

A document can be detailed and still leave the team guessing. A prototype can look convincing while the underlying rules remain unresolved.

  • A prototype does not reliably preserve every business rule, permission or failure route.
  • A PRD does not automatically make a complex interaction testable or its edge cases complete.
  • A detailed specification cannot prove that customers understand or value the proposed experience.
  • More documentation does not compensate for an unresolved product decision or missing owner.
A practical sequence

Combine artefacts when the risk changes

Early in the work, a short brief and rough prototype may be enough to test whether the team is solving the right problem. Once the direction is credible, the PRD can hold the evidence, scope and decisions. Detailed specification should concentrate on the behaviour that would otherwise be invented during design, development or QA.

Use a prototype first when the interaction is the uncertainty

If the team needs to compare journeys, explain a new workflow or observe how somebody responds, make the experience concrete before documenting every rule. Record what the prototype is testing and which parts remain illustrative rather than agreed.

Use a PRD first when alignment is the uncertainty

If people disagree about the problem, intended outcome, audience or first useful slice, a polished interface is premature. Establish the evidence, choices, non-goals and decision owner before moving into detailed interaction or implementation work.

Use a detailed specification first when behaviour carries the risk

Regulated, data-heavy and permission-sensitive products often fail in the conditions around the main journey. Make calculations, decision rules, exceptions, evidence and acceptance conditions explicit, then use a prototype where the team still needs to test presentation or flow.

The handover may need all three

The final set should feel like one source of truth rather than three competing versions. Link each visual state to the relevant decision or rule, keep assumptions labelled, and remove detail that no longer affects the next commitment. The goal is not a larger pack. It is a handover that another team can act on without inventing essential product logic.

Next step

Bring the artefacts that no longer agree

A prototype, draft PRD, source document or open decision is enough to start.