Phase 1 — Requirements Document

Team: Members:

Write this as a single, coherent synthesis of what you heard across all persona interviews (see interviews/) — not a transcript dump, and not just the easiest persona to satisfy.

The real need

Not “a dashboard of X” but the question your stakeholders are actually trying to answer, and why it matters to them. If any persona couldn’t articulate the underlying need, that’s a sign to go back and interview them further before writing this.

TODO

Audience

Who this is for — your personas and anyone else who’ll see it — and what each already knows.

TODO

Data

The dataset you’re using, with provenance (source, collection method, known gaps or biases). If you’re sourcing your own data, document how.

TODO

Where personas conflicted

Where two personas wanted different or incompatible things: what each wanted, and how you decided what the design should actually prioritize. This is the most important section — it’s the reconciliation work a real requirements process requires.

TODO

Must-have vs. nice-to-have

What makes the design a failure if it’s missing, versus what’s welcome but not critical, after the reconciliation above.

TODO

Acceptance criteria

The specific, checkable criteria this document’s client would use to judge the final design. Write these from the interviews, before you’ve designed anything — they are what you will be held to in Phase 4, when a real client reads this same document.

TODO