What This Template Is For
A product one-pager is the shortest formal document a PM writes. It fits on a single page (or a single screen) and answers the five questions every decision-maker asks: What is the problem? What do you propose? What is the expected impact? How much effort is required? What are the risks?
One-pagers are used to pitch new initiatives in product review meetings, to propose features for the next quarter's roadmap, or to get a quick "go / no-go / investigate further" decision from leadership. They are not a substitute for a PRD or Feature Specification. They are the document that earns you permission to write the PRD.
The constraint of a single page forces clarity. If you cannot make the case in one page, you either do not understand the problem well enough or the initiative is too complex for a pitch and needs a full product brief instead. See the Product Brief V2 Template for the longer format.
Score multiple one-pagers against each other using the RICE Calculator. For guidance on presenting one-pagers to leadership, see the Stakeholder Management Handbook.
How to Use This Template
- Write it in one sitting. A one-pager that takes a week to write is too complex for this format.
- Lead with the problem, not the solution. Decision-makers need to believe the problem is worth solving before they care how you plan to solve it.
- Quantify impact with numbers, not adjectives. "Reduce churn by 3 points" beats "significantly reduce churn."
- Be honest about effort and risks. Underselling effort erodes trust when the project inevitably takes longer than promised.
- End with a clear ask. What decision do you need? Approval to proceed? Resources? A meeting to discuss further?
- Format for scanning. Use tables, bold headings, and short sentences. Assume the reader has 3 minutes.
The Template
[Initiative Name]
Author: [Name] | Date: [Date] | Status: Proposed / Under Review / Approved
Problem.
[2-3 sentences. What user or business problem does this solve? Include one data point as evidence.]
Proposed Solution.
[2-3 sentences. What will we build or change? Describe the approach at a high level without implementation details.]
Impact.
| Metric | Current | Expected | Confidence |
|---|---|---|---|
| [Primary metric] | [Baseline] | [Target] | High / Medium / Low |
| [Secondary metric] | [Baseline] | [Target] | High / Medium / Low |
Revenue/retention impact. [1 sentence quantifying the business value: ARR, retention points, conversion rate, cost savings.]
Effort.
| Dimension | Estimate |
|---|---|
| Engineering | [Team-weeks or sprint count] |
| Design | [Days or sprints] |
| Dependencies | [Other teams, external services, none] |
| Timeline | [Start date to ship date] |
Risks.
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk 1] | Low / Medium / High | [Description] | [Plan] |
| [Risk 2] | Low / Medium / High | [Description] | [Plan] |
Alternatives Considered.
| Alternative | Why Rejected |
|---|---|
| [Option A] | [1 sentence reason] |
| [Option B] | [1 sentence reason] |
| Do nothing | [1 sentence on cost of inaction] |
Ask. [1 sentence. What decision do you need? "Approve for Q2 roadmap" / "Allocate 2 engineers for 4 weeks" / "Schedule a deep-dive meeting"]
Formatting Guidelines
Length. One page when printed or one screen when viewed on a laptop. If your one-pager scrolls significantly, cut content.
Font and spacing. Use your company's standard document font. No smaller than 10pt. Single spacing is fine. Tables compress information better than prose.
Visuals. One mockup or diagram is allowed if it replaces a paragraph of explanation. Do not add visuals for decoration.
Distribution. Share as a Google Doc, Notion page, or Confluence page with comment permissions. Do not attach as a PDF. Stakeholders should be able to leave inline comments.
Filled Example: Slack Integration for Task Notifications
Slack Integration for Task Notifications
Author: Marcus Johnson | Date: March 2026 | Status: Proposed
Problem.
Users manage tasks in TaskFlow but communicate in Slack. When a task is assigned, commented on, or completed, the assignee has to check TaskFlow to see the update. 72% of our daily active users also use Slack. In our Q1 user survey, "Slack integration" was the #1 requested feature (89 mentions).
Proposed Solution.
Build a Slack app that posts real-time task notifications to a user's DM or a designated channel. Users can configure which events trigger Slack messages (assigned, mentioned, due soon, status changed). The Slack message includes a deep link back to the task in TaskFlow.
Impact.
| Metric | Current | Expected | Confidence |
|---|---|---|---|
| Daily active users (DAU) | 12,400 | 14,200 (+15%) | Medium |
| Task response time (median) | 4.2 hours | 2.5 hours | Medium |
Revenue/retention impact. Slack integration is a check-box requirement for 3 enterprise deals in pipeline worth $210K combined ARR. Integration parity with Asana and Linear removes the most-cited switching reason in churn interviews.
Effort.
| Dimension | Estimate |
|---|---|
| Engineering | 3 engineers, 4 weeks (12 team-weeks) |
| Design | 1 designer, 1 week (notification preferences UI) |
| Dependencies | Slack App Directory review (2-3 week approval process) |
| Timeline | April 7 start, May 2 ship (beta), May 16 GA |
Risks.
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Slack App Directory rejection | Low | 3-week delay | Follow Slack design guidelines, submit early |
| Notification fatigue | Medium | Users mute the integration | Ship with sensible defaults (mentions only), add digest mode |
Alternatives Considered.
| Alternative | Why Rejected |
|---|---|
| Email notifications only | Already have email. Users want real-time in their primary communication tool. |
| Microsoft Teams first | Slack usage (72%) is 3x Teams usage (24%) among our users. Build Slack first. |
| Do nothing | Losing enterprise deals and churning mid-market accounts to competitors with Slack support. |
Ask. Approve for Q2 roadmap and allocate 3 engineers (Jordan, Alex, Priya) starting April 7.
Key Takeaways
- Fit the entire pitch on one page to force clarity and respect the reader's time
- Lead with the problem and evidence, not the solution
- Quantify impact with numbers and specify the confidence level
- Include "Alternatives Considered" to show you evaluated options
- End with a clear, specific ask: what decision do you need?
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use