Supplied brief - unverified: Working hypothesis: founders and small teams need a coherent brief, identity and requirements before execution; scattered inputs make handoff difficult.
PRODUCT REQUIREMENTS · WORKING DRAFT · 2.1.0
Prodninja
Plan, design, and build products and workflows people can use.
Explore the document
Product overview and executive intent
Define the user problem, product outcome and boundaries. The supplied brief is not validated research.
Scope, non-goals and prioritisation
Supplied brief - unverified: Proposed MVP: source-aware brand guide, BRD and PRD drafts with safe local exports. Exclusions: automatic approval, fabricated research, automatic project delivery or guaranteed outcomes.
Separate MVP requirements, later candidates and exclusions. Record priority rationale and dependencies; do not invent delivery dates.
Research evidence and limitations
Supplied brief - unverified: Source: existing ProdNinja website, tool interfaces and canonical tokens. No interviews, survey dataset or measured customer outcomes supplied. Validate the fragmentation hypothesis with target users.
Record source ID, method, recruitment, date, sample size, denominator and limitations for each finding. Separate observation, hypothesis and decision. Do not invent survey results, interviews or quotes.
Audience, persona and jobs to be done
Supplied brief - unverified: Proposed role-based persona: a founder or product lead preparing a launch. Job: turn scattered context into a reviewable brief. Goal: align collaborators; friction: uncertain scope and unsupported claims.
Describe a role, context, goal, motivation, friction and job to be done. Label untested personas as hypotheses; avoid invented identities, portraits, demographic or health details.
Empathy map
Supplied brief - unverified: Says: no sourced quotes. Thinks/Feels (hypotheses): wants confidence in what is ready to share. Does (hypothesis): assembles sources and iterates drafts. Validate in task observation.
Capture Says, Thinks, Does and Feels separately. Quote only sourced statements; label inferred thoughts and feelings. Link each insight to a source ID and validation question.
User journey and opportunities
Discover tool
choose example or enter brief
inspect draft
resolve evidence gaps
export
stakeholder review. Proposed opportunity: preserve source notes and make incomplete inputs visible at handoff.
Supplied brief - unverified: Discover tool -> choose example or enter brief -> inspect draft -> resolve evidence gaps -> export -> stakeholder review. Proposed opportunity: preserve source notes and make incomplete inputs visible at handoff.
For each stage record action, touchpoint, friction, emotion hypothesis, opportunity, owner and measure. Include before-use, core task and support or follow-up.
Task flow and recovery
Supplied brief - unverified: Open studio -> enter required brief -> choose document -> build locally -> inspect -> edit and rebuild -> export. Recovery: missing required inputs show validation; stale drafts disable exports; optional AI failure leaves local output available.
Specify entry, prerequisites, decisions, success, empty/loading/error states, retry, cancellation and support. Check branch labels and avoid forcing account creation when the task does not require it.
Information architecture and card sorting
Supplied brief - unverified: Proposed groups: Brief; Identity; Research and experience; Review; Exports. Brand guidelines, BRD and PRD share a brief but serve different decisions. No card-sort study has been conducted.
List navigation groups, content labels and relationships. A proposed grouping is not a completed card-sort study: record method, participants and results only when supplied.
Cross-channel strategy and constraints
Supplied brief - unverified: Public web studio, printable HTML and Markdown. Optional Azure editorial pass uses seven listed brand fields after explicit consent. No automatic saving in the public studio; authenticated tools save workspace artifacts separately.
Identify supported channels, devices, connectivity, permissions, integrations and fallback paths. Verify actual capabilities; do not infer mobile apps or GPS requirements from a reference.
Success measures and instrumentation
Supplied brief - unverified: Proposed measures: task completion (successful reviewed export / started sessions), revision errors and evidence-gap resolution. Baseline, targets, collection consent, owner and review window are not supplied.
For each measure record definition, baseline, target, event/source, owner and review window. Unknown values stay unresolved; do not invent targets or improvements.
Validation, usability testing and iteration
Supplied brief - unverified: Proposed: observe founders completing one brand guide and one PRD; test empty input, changed-input export guard, narrow viewport, keyboard operation and HTML print. Record findings before setting improvement claims.
Proposed plan: recruit representative users with consent; test the primary task and one recovery path; record completion, errors, time and feedback. Set acceptance thresholds before testing, document findings and retest fixes.
Evidence to requirement traceability
Supplied brief - unverified: Proposed R-01: generate from supplied inputs with explicit gaps. AC-01: no research figures appear when absent. R-02: export current draft only. AC-02: editing a field disables export until rebuild. Evidence and measurement owners remain open.
Use E-01 evidence -> N-01 user need -> R-01 requirement -> AC-01 observable acceptance -> M-01 measure. Record source, priority, owner and unresolved questions. Missing links require review; this draft is not approval.
Functional requirements and acceptance
Supplied brief - unverified: Proposed R-01: generate from supplied inputs with explicit gaps. AC-01: no research figures appear when absent. R-02: export current draft only. AC-02: editing a field disables export until rebuild. Evidence and measurement owners remain open.
For every R-ID record actor, trigger, preconditions, expected result, data changes and Given/When/Then acceptance. Include permissions, validation, duplicate submission and recovery.
Non-functional requirements and data
Supplied brief - unverified: Public web studio, printable HTML and Markdown. Optional Azure editorial pass uses seven listed brand fields after explicit consent. No automatic saving in the public studio; authenticated tools save workspace artifacts separately.
Agree accessibility, performance, security, privacy, retention, reliability and support requirements. Define collected data, permission boundaries and failure handling; unknown numeric budgets remain open.
Delivery, dependencies and release readiness
Supplied brief - unverified: Product owner, brand reviewer and engineering owner: to confirm. Each approves their own scope, claims and release evidence.
Proposed phases: discover -> define -> ideate -> design -> test -> release. Record owners, dependencies, risks, rollout, rollback, support and review decisions. Validate locally, then integration, then production separately.