Feature One-Pager

A feature one-pager is a single-page summary executives and cross-functional leads can read in under three minutes. It answers: why now, for whom, what we will build, how we measure success, what is out of scope, and what decision you need today.

It is not a PRD, not a slide deck, and not a roadmap — it is a direction contract before you invest in specification.

Full PRDs stall steering committees; vague verbal pitches get misremembered. One-pagers force clarity on the problem and the ask (approve, defer, or kill) while alignment is still cheap. Consultants use them as client-facing summaries; product teams use them to gate PRD work.

Internal feature pitches, steering committees, portfolio prioritisation, or client deliverables where the reader will not read twenty pages. Write after a product brief or discovery slice; before /prd depth.

1. Headline outcome — measurable direction in one line.
2. Problem + evidence — user quote, data point, or journey pain ID.
3. Target user — persona or segment in one sentence.
4. Proposed solution — three bullets maximum; no architecture essay.
5. Success metric + target — one primary KPI with baseline if known.
6. Scope boundary — explicit non-goals and dependencies.
7. Timeline / phase — when value lands, not every sprint task.
8. Ask — approve, defer, or kill with named decision owner.

• Readable in under three minutes on one screen or printed page.
• One primary metric; secondary metrics in footnote if needed.
• Clear ask at the bottom — not "thoughts?"
• Links to OKR, journey, or brief refs when they exist.

• PRD length with a one-pager title — loses the format's purpose.
• Multiple unrelated features on one page — split or escalate to brief.
• No ask — readers agree it is "interesting" and nothing ships.
• Solution before problem — executives reject without context.

Northvale Systems — ERP sync for vendor onboarding. Headline: cut supplier go-live from 18 to 7 days. Problem: "We still fax W-9s." User: procurement ops lead. Solution: self-serve portal + nightly ERP sync (3 bullets). Metric: 80% self-serve completion. Timeline: pilot two plants in Q3. Ask: approve Q3 eng allocation (2 squads × 6 weeks).

PulseWell — manager nudge cards. Headline: act before burnout shows in exit interviews. User: people manager, ~12 directs. Solution: weekly risk band + two suggested actions. Metric: 30% nudge action rate in 90-day pilot. Scope: UK HRIS only; no clinical claims. Ask: green-light five design partners.

Harbor — reshoring diagnostic SKU. Headline: paid diagnostic before six-week engagement. Problem: clients stall on grant paperwork. Solution: online scorecard + workshop outline in 48h. Metric: 25% diagnostic→workshop conversion. Ask: approve £4,500 list price for Q4.

Clearwater — borehole check-in workflow. Headline: donors see maintenance impact, not drill counts alone. User: regional WASH coordinator. Solution: SMS/photo check-ins + map. Metric: 20% faster repairs in pilot district. Out of scope: satellite IoT year one. Ask: defer national rollout until pilot KPI met.

Run /onepager for ONEPG-001, linked to backlog items, OKR-, or BRIEF- refs when available. Escalate approved one-pagers to /prd with traceability.