BUSINESS REQUIREMENTS · WORKING DRAFT · 2.1.0

Prodninja

Plan, design, and build products and workflows people can use.

Product studio and productised-services brandDraft — owner review required17 sections
Explore the document
01

Executive intent and business opportunity

01

Supplied brief - unverified: Working hypothesis: founders and small teams need a coherent brief, identity and requirements before execution; scattered inputs make handoff difficult.

02

Define the business problem, affected stakeholders, current process and intended outcome. Separate business need from a chosen implementation.

02

Stakeholders and decision rights

01

Supplied brief - unverified: Product owner, brand reviewer and engineering owner: to confirm. Each approves their own scope, claims and release evidence.

02

Name sponsor, accountable owner, users, operational partners, reviewer and approver only when supplied. Record responsibilities, approval state and escalation path.

03

Current and proposed operating model

01

Supplied brief - unverified: Draft -> review -> owner approval -> distribution. Local output does not establish feature availability or approve marketing claims. Resolve placeholders before client handoff.

02

Describe as-is and proposed to-be process, handoffs, business rules, exceptions and support ownership. Confirm policy and capability before implementation.

04

Options, competitive context and SWOT

01

Supplied brief - unverified: Options to evaluate: existing document workflow, local generator, authenticated workspace. Competitive positioning and SWOT require dated external evidence; none supplied.

02

Compare do nothing, process improvement and product options. Source and date competitor claims; use Unknown when unverified. Record strengths, weaknesses, opportunities and threats with supporting evidence.

05

Costs, benefits and feasibility

01

Supplied brief - unverified: Existing Azure resource reuse is verified in release documentation. Usage is billable under existing subscriptions. Cost per draft, benefit baseline and ROI are not measured.

02

Record cost categories, assumptions, benefit hypotheses, funding owner and feasibility dependencies. Amounts, ROI and timelines require evidence and approval.

06

Business scope and exclusions

01

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.

02

Identify included outcomes, excluded work, constraints, dependencies and change-control decision owner.

07

Research evidence and limitations

01

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.

02

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.

08

Audience, persona and jobs to be done

01

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.

02

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.

09

Empathy map

01

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.

02

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.

10

User journey and opportunities

1

Discover tool

2

choose example or enter brief

3

inspect draft

4

resolve evidence gaps

5

export

6

stakeholder review. Proposed opportunity: preserve source notes and make incomplete inputs visible at handoff.

01

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.

02

For each stage record action, touchpoint, friction, emotion hypothesis, opportunity, owner and measure. Include before-use, core task and support or follow-up.

11

Task flow and recovery

01

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.

02

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.

12

Information architecture and card sorting

01

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.

02

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.

13

Cross-channel strategy and constraints

01

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.

02

Identify supported channels, devices, connectivity, permissions, integrations and fallback paths. Verify actual capabilities; do not infer mobile apps or GPS requirements from a reference.

14

Success measures and instrumentation

01

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.

02

For each measure record definition, baseline, target, event/source, owner and review window. Unknown values stay unresolved; do not invent targets or improvements.

15

Validation, usability testing and iteration

01

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.

02

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.

16

Evidence to requirement traceability

01

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.

02

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.

17

Business acceptance and change control

01

Supplied brief - unverified: Product owner, brand reviewer and engineering owner: to confirm. Each approves their own scope, claims and release evidence.

02

Record business acceptance criteria, open risks, approval decision, version, owner and next review. Discovery, definition, ideation, design and testing are proposed phases; estimate dates only after scoping.