Say No Like an Editor: Kill Lists and Tighten Passes
A practical workflow to cut low-value features, tighten the rest, and protect focus without burning trust.

Editors cut pages so the story lands. Product managers can use the same craft. This guide shows how to run a two‑pass edit on your roadmap: a Kill List for firm cuts, and a Tighten Pass for smaller, safer versions. You will protect focus and keep trust.
- Two passes: Kill List (cut), Tighten Pass (shrink or merge).
- Rank the Kill List by harm avoided, not lost value.
- Pair every no with a trade‑off line and a clear if/when to reopen.
- Hold a regular manuscript review to propose, edit, and publish.
Who this is for and what you leave with
This is for working PMs who face a flood of small asks and strong feelings. You need to guard a mid‑term roadmap and still be fair. At the end you will have a one‑page Kill List template, a set of tightened proposal shapes, a trade‑off sentence you can reuse, and a 30‑minute review ritual you can run.
Borrow the editor’s frame
First cut what does not serve the story. Then tighten what remains so each line earns its place.
— The editor’s two‑pass ruleThink of your quarter as a manuscript. Stakeholder asks are paragraphs. Your job is not to please each request. Your job is to deliver a clear story with the resources you have.
The two‑pass workflow
List all live asks in one place. Use the same title pattern: who it serves, the action, the outcome.
Mark items that break focus, add debt, or fragment UX. Be blunt on criteria. No soft maybes here.
For each cut, add one short note: metric risk, support volume, dependency, or opportunity cost.
For what remains, propose a smaller scope, a later tranche, or a pilot with a metric gate.
Pair each no or tighten with one sentence that states the trade and the condition to revisit.
Meet, propose, edit, and sign the list. Share it in the open the same day.
Build the Kill List: rank by harm avoided
The Kill List is not a value ranking. It is a harm shield. You cut the items that would do the most damage if they shipped now.
- Focus drift: pulls engineers off the main bet.
- UX fragmentation: adds a one‑off pattern.
- Time debt: many coordination hours for small user impact.
- Support risk: likely to create new how‑do‑I tickets.
- Dependency risk: blocks or delays a core sequence.
State criteria in plain words. Keep the Kill List to one page. Share it early, even as a draft.
| Approach | What it optimises | Common failure | Better move |
|---|---|---|---|
| Lost value ranking | What we give up if we say no | Adds many small items that feel good but dilute the bet | Ask: what harm do we avoid by cutting this now |
| Harm avoided ranking | Risk, debt, fragmentation you prevent | Can feel harsh if not explained | Publish criteria and one‑line evidence per cut |
The Tighten Pass: make smaller, safer shapes
Tightening is not delay. It is design. You offer a shaped alternative that fits the current story.
Use this pattern
Timebox a short build window with a stop date
Metric one measure to judge the pilot
Gate what must be true to expand later
Unblock strip dependencies you cannot carry now
Offer three tighten types, in this order:
- Smaller scope now.
- Later tranche that does not block the main work.
- Pilot with a metric and a decision date.
Say no without drama: trade‑offs and conditions
Pair each decision with one sentence. Keep it dry and specific.
- We are choosing X over Y this quarter to protect Z; we will reopen if/when C.
Replace X, Y, Z, C with the main bet, the ask, the focus, and the condition. Conditions are facts you can check. For example: dependency done, metric hit, support volume changed, or a partner commits to a clear input.
Make it a ritual: the manuscript review
- Cadence: 30 minutes, mid‑quarter and then bi‑weekly as needed.
- People: PM, EM, Design, Support lead, and one business owner.
- Input: the live list, with harms noted and early tightens sketched.
- Rules: timebox each ask to two minutes; decisions in the doc; no hallway follow‑ups.
- Output: a dated Kill List and three to five tightened proposals.
Worked example: a 30‑minute kill/tighten session
Context: it is mid‑quarter. The team is building the core activation flow. You have a flood of side asks.
- Minutes 0–5: read the list and mark likely cuts.
- Minutes 5–15: confirm cuts, attach one‑line evidence.
- Minutes 15–25: tighten the top three survivors.
- Minutes 25–30: publish trade‑offs and conditions.
-
Custom color themes — Cut. Harm avoided: UX fragmentation during activation work. Evidence: adds a new settings surface and pattern.
Trade‑off: We are choosing activation quality over themes this quarter to protect onboarding; we will reopen if activation metrics hit the target.
-
Bulk export v1 — Cut. Harm avoided: time debt and new support paths. Evidence: touches permissions and file storage paths we are refactoring next quarter.
Trade‑off: We are choosing stability over bulk export to protect the refactor; we will reopen when the storage refactor is complete.
-
Partner‑only toggle — Cut. Harm avoided: dependency risk on partner auth. Evidence: requires a third‑party review not yet scheduled.
Trade‑off: We are choosing predictable delivery over the toggle to protect schedule; we will reopen if the partner signs the auth spec.
-
Advanced filters → MVP filter set
- Scope: include 3 core filters used in activation; exclude save‑views and share.
- Timebox: 1 sprint.
- Metric: activation completion rate does not drop; time‑to‑first‑result under a set threshold.
- Gate: if support tickets on search rise, pause expansion.
Trade‑off: We are choosing a basic filter MVP over the full set to protect activation speed; we will expand if we clear the metric gate. -
In‑app tour → later tranche
- Scope: only a single start‑here cue on day one; no branching tips.
- Timebox: 1 week in the last sprint of the quarter.
- Metric: click‑through to the main task over a set rate.
- Gate: only if engineering has two days free buffer.
Trade‑off: We are choosing a small cue later over a full tour now to protect build focus; we will do it if buffer appears. -
Notifications → pilot
- Scope: email only, for one event tied to activation failure.
- Timebox: 1 week build, 2 weeks run.
- Metric: reduce drop‑offs by a set percent among pilot users.
- Gate: if the pilot meets the metric, expand to two more events next quarter.
Trade‑off: We are choosing a narrow pilot over a full notifications system to protect platform work; we will expand if the pilot meets its metric.
Common mistakes and simple fixes
- Being vague. Fix: publish plain criteria and one‑line evidence.
- Emotional wording. Fix: avoid blame; speak in harms and trades.
- Private lists. Fix: share drafts early and date them.
- Tighten means delay. Fix: add metrics, timeboxes, and gates so it is a decision, not a stall.
Tools that help
Use your existing prioritisation model to check that tightens do not hide risk. If you need a simple way to compare options, try the Prioritisation tool once to sanity‑check the survivors.


