Say No by Forcing a Choice: The Decision One‑Pager
Convert stakeholder asks into clear choices with a decision‑grade one‑pager that ends stalling and protects focus.

This guide is for working PMs who field a steady stream of asks. You want to keep focus without burning trust. You will leave with a decision one‑pager you can send the next time someone asks for a quick add. It converts a vague yes/no into a clear choice or a short test.
- A one‑pager is a decision vehicle. Not a brochure.
- Show the ask, the goal metric, options, evidence, and criteria.
- Offer a binary: fund with constraints, or run a short pilot.
- Include three sign boxes: Fund, Pilot, Defer. Each with trade‑offs and next steps.
Why this works
A good no is a concrete choice with visible consequences. It protects focus and keeps the relationship clean.
Build the decision one‑pager
Open with the outcome metric
State the single metric the request aims to move. Define how it is measured. Keep it observable within one cycle. Examples: sign‑up completion rate, day‑1 activation, weekly retention, average order value.
List alternatives and success
Write 2–3 options, including do nothing for now. For each, define what success would look like on the outcome metric and guardrails. Use clear thresholds, not ranges like “meaningful”.
Show evidence, unknowns, and the minimum test
List signals you have (user quotes, past tests, benchmarks you own). Call out the key uncertainty. Propose the smallest test that resolves it. Name the leading indicators, events to instrument, sample, and run time.
Recommend action and timeline
Give a clear recommendation with a path to a decision. If you suggest a pilot, say how long it runs and exactly what will trigger ship or stop. If you suggest fund, set scope and constraints.
Add Fund / Pilot / Defer boxes
Put three sign boxes with trade‑offs and next steps. Defer must include when you will revisit, or it becomes a stall. Treat signatures as a contract.
Compare your decision paths
| Path | What you commit | Trade‑offs | Decision trigger |
|---|---|---|---|
| Fund | Build scoped version now under stated constraints. | Opportunity cost; higher immediate engineering load. | Outcome and guardrails hit by end of first release window. |
| Pilot | Run a short test with clear metrics and stop/go rules. | Small delay to learning if sample is too narrow; keep scope tight. | Pre‑set thresholds on leading indicators and the outcome metric. |
| Defer | Do not work on it now; place a review on the calendar. | Risk of missing a hidden upside; preserves focus. | Revisit by the stated date or trigger. No date, no defer. |
Checklist before you send
- Outcome metric is first, defined, and observable within the cycle.
- 2–3 options, each with success and guardrails in numbers.
- Evidence and the key unknown are both visible.
- Minimum viable test is named with events and sample.
- Recommend action with a short timeline and owner.
- Three sign boxes: Fund, Pilot, Defer. Each has next steps.
- Defer has a concrete revisit point. No open‑ended stalls.
- Link the working doc and dashboard. Keep the one‑pager tight.
Worked example: turn “add social invites to sign‑up” into a decision
Ask: “Let’s add social invites to sign‑up.” Goal: increase day‑1 activation without hurting sign‑up completion.
Outcome metric
Day‑1 activation rate: percent of new users who complete the first key action within 24 hours of sign‑up.
Guardrail: sign‑up completion rate must not drop. Support tickets must not spike during test.
Options
1) Fund: Ship full feature now
Scoped build of a social invite step during or right after sign‑up (UI, providers, rate limits, help content).
Success: +2 percentage points in day‑1 activation with no drop in sign‑up completion. Guardrail: support tickets stable.
2) Pilot: 10% exposure with referral codes
Post‑sign‑up module shows a personal referral link. No third‑party auth needed.
Success: ≥2 percentage‑point lift in day‑1 activation in exposed cohort. Guardrails as above.
3) Defer: Not now
Revisit in the next planning cycle or after the current activation work concludes, whichever comes first.
Success: N/A. Decision is to delay with a firm revisit point.
Evidence and unknowns
- Evidence: Past referral campaigns lifted activation on existing users. New‑user flow impact is unknown.
- Unknown: Does adding an invite step distract and reduce sign‑up completion?
Minimum test (for the Pilot option)
- Exposure: 10% of new sign‑ups see a post‑sign‑up invite module with a copyable referral code and one share button.
- Run time: Until the exposed cohort reaches a stable read on day‑1 activation (e.g., two full weeks of traffic or agreed sample size).
- Instrumentation:
- signup_started, signup_completed
- invite_module_viewed, invite_clicked, invite_sent
- referral_signup_started, referral_signup_completed
- first_key_action_completed (for activation)
- Event properties: user_id, timestamp, variant (pilot/control), referral_code, source_channel.
- Success thresholds:
- Day‑1 activation: +2 percentage points in exposed vs control.
- Sign‑up completion: drop no worse than −0.5 percentage points.
- Support tickets: no material change during the pilot window.
- Decision rule: If thresholds met, queue scoped build. If not, stop and document learnings.
Recommendation
Run the Pilot. It answers the main unknown with a small surface area and no third‑party dependencies. If it clears thresholds, fund a scoped build that keeps invites post‑sign‑up to protect completion.
Sign one box
Fund
We commit: Build the scoped feature now. Limit to post‑sign‑up. No social auth integration in this release.
Trade‑offs: Uses capacity from current activation sprint. Opportunity cost on other items.
Next: Kickoff with design and eng. Instrument events as listed. Review metrics at the end of first release window.
Signed: ____________
Pilot
We commit: 10% exposure. Events instrumented above. Pre‑set thresholds and a stop/go decision meeting on the calendar.
Trade‑offs: Small delay before any full build; fast learning with minimal scope.
Next: Enable variant, run to stable read, review against thresholds, decide ship or stop.
Signed: ____________
Defer
We commit: Not doing it now. We will revisit in the next planning cycle or once current activation goals ship, whichever comes first.
Trade‑offs: Preserves focus; risk of missing upside if the idea is strong.
Next: Add a dated review to the plan. If not reviewed by then, the item closes.
Signed: ____________
Common mistakes
- Turning the one‑pager into a spec. Keep specs in a linked doc.
- Hiding assumptions. Name them and say how the test resolves them.
- Vague decision criteria. Write thresholds in numbers.
- Treating it like a handshake. Get a name on a box.
- Letting Defer be open‑ended. Always add a revisit point.
You can draft this fast with a simple template. The One‑pager helps you keep it tight and decision‑ready.


