Prototype Elicitation

Purpose

Use sketches, mock-ups, or prototypes to expose assumptions and refine requirements.

Use when

• stakeholders struggle to react to text-only requirements
• interface, workflow, or interaction detail matters
• ambiguity remains after interviews/workshops

Inputs

• problem context
• available evidence and constraints
• known stakeholders or actors
• desired output format

Procedure

1. Clarify the decision or deliverable.
2. State assumptions before analysis.
3. Apply the technique explicitly rather than implicitly.
4. Capture findings in a structured table or list.
5. Separate facts, inferences, and unknowns.
6. End with implications for next actions.

Outputs

• prototype goals
• prototype fidelity recommendation
• test scenarios
• feedback questions
• requirement changes log

Guardrails

• Do not present the technique as the answer; use it to inform a decision.
• Flag missing evidence and weak assumptions.
• Keep terminology consistent with the project glossary.
• Where tradeoffs exist, rank them explicitly.

Completion criteria

• technique applied correctly
• assumptions visible
• findings actionable
• next step clear