Scope and Sequencing
Protect the outcome while cutting the implementation. · Product Judgment · Lesson 10 · 3 min
Scope and Sequencing · 3 min
Situation
One deadline, three kinds of work.
A team is launching shared reports. The plan includes secure links, permission settings, custom branding, scheduled delivery, and a visual report builder.
The immediate need is to let account managers send a reliable weekly report. Treating every item as essential makes the date fictional.
Mental model
Must have, later, never.
“Must have” means the outcome cannot be achieved responsibly without it. “Later” means useful but unnecessary for this release. “Never” means outside the intended product direction, even if someone requested it.
These are decisions for a specific outcome and context. They are not permanent rankings of abstract features.
Example
Cut flexibility before correctness.
A fixed report template may serve the initial workflow. Custom branding and a report builder can wait. Access control and accurate numbers cannot if sensitive customer data is involved.
Manual sending might replace scheduling during a small pilot. Give the task an owner and a capacity limit so hidden work does not become an unbounded obligation.
Sequence
Deliver a complete path.
A thin slice connects creation, access, viewing, and error recovery for one report type. Building all the settings first creates visible progress but no usable workflow.
Ask which dependency must exist before users can receive value. Sequence around that path, including support and operational readiness.
PM question
What breaks if this is omitted?
For each item, describe the consequence of leaving it out. If the answer is merely “the product feels less complete,” investigate whether that matters to the chosen user and task.
Write down deferred requests and the conditions for revisiting them. Otherwise “later” becomes a promise nobody intended to fund.
Remember this
Cut scope by preserving a coherent outcome.
A smaller workflow that works end to end is often more useful than many unfinished capabilities. Protect safety and correctness while reducing breadth.