Re-scope without lying
Cut or reshape scope by making the trade-off explicit, preserving the core value, and naming what is no longer promised rather than hiding the loss inside ambiguity.
- Situation
- You need to reduce or reshape scope while preserving trust.
- Goal
- Protect trust while adjusting commitments to reality.
- Do not use when
- the change is only cosmetic and does not materially alter the promise
- Primary owner
- product lead
- Roles involved
product leaddelivery leadengineering leaddecision-maker for commitment changes
Context
The situation
Deciding whether to reach for this playbook: when it fits, and when it doesn't.
Use when
Conditions where this playbook is the right tool.
- Timeline or capacity changed materially
- Dependencies proved larger than expected
- The team can still preserve core value but not the original package
- Stakeholders need clarity more than reassurance
Stakes
Why this matters
What this playbook protects against, and why skipping or half-running it tends to be expensive.
Teams lose trust not only because scope changes, but because scope changes are disguised. Honest re-scoping protects credibility and helps better decisions happen earlier next time.
Quality bar
What good looks like
The observable qualities of a team or system that is actually doing this well. Not just going through the motions.
Signs of the playbook done well
- The team can say what remains, what moved out, and why
- The core outcome is preserved as much as possible
- Stakeholders understand the trade-off clearly
- The new scope is simpler and more defensible than the old one
- Future reporting uses the new promise, not the old ghost promise
Preparation
Before you start
What you need available and true before running the procedure. Skipping this is the most common reason playbooks fail.
Inputs
Material you'll want to gather first.
- Original scope and intent
- Current constraints
- Risk picture
- Must-have versus nice-to-have view
- Stakeholder dependencies
Prerequisites
Conditions that should be true for this to work.
- Clear understanding of the core outcome
- Authority to change commitments
- Willingness to state loss explicitly
Procedure
The procedure
Each step carries its purpose (why it exists), its actions (what you do), and its outputs (what you produce). Read the purpose. It's what keeps the step from degenerating into checklist theatre.
Re-state the purpose
Protect the real value instead of preserving every item.
Actions
- Write down what user, business, or operational value the work was meant to create
- Separate that core purpose from the full original package
- Identify which elements are essential to that purpose
Outputs
- Core outcome statement
Classify scope by value and coupling
Cut intelligently, not randomly.
Actions
- Mark items as essential, supporting, optional, or deferrable
- Note dependencies and sequencing constraints
- Look for scope that is expensive but not core
Outputs
- Scope classification
Create explicit re-scope options
Turn vague disappointment into real choices.
Actions
- Prepare 2 to 3 scope options with trade-offs
- Show what each option preserves and loses
- Include impact on timeline, quality, and dependencies
Outputs
- Re-scope options brief
Decide and say the loss clearly
Preserve trust through precision.
Actions
- Choose one option with accountable decision-makers
- Write down what is no longer in the promise
- Update all delivery and stakeholder artifacts to match
Outputs
- New scope statement
- Updated commitment language
Align execution to the new promise
Stop the old promise from surviving unofficially.
Actions
- Remove out-of-scope work from active planning
- Re-baseline milestones and definitions of done
- Watch for quiet re-expansion
Outputs
- Updated execution plan
Judgment
Judgment calls and pitfalls
The places where execution actually diverges: decisions that need thought, questions worth asking, and mistakes that recur regardless of good intent.
Decision points
Moments where judgment and trade-offs matter more than procedure.
- What is the minimum scope that still preserves the real value?
- What should be deferred versus discarded?
- How much disappointment now is better than confusion later?
- Who must explicitly approve the trade-off?
Questions worth asking
Prompts to use on yourself, the team, or an AI assistant while running the procedure.
- What is the core outcome we are protecting?
- Which scope items are expensive but not essential?
- What exactly are we no longer promising?
Common mistakes
Patterns that surface across teams running this playbook.
- Softening the change so much that nobody understands the loss
- Leaving cut scope in planning tools as unofficial future work
- Trying to preserve every stakeholder concern equally
- Describing the change as a minor adjustment when it is a real reduction
Warning signs you are doing it wrong
Signals that the playbook is being executed but not landing.
- Different stakeholders describe the new scope differently
- The team still feels pressure to deliver the old promise
- Status updates still compare progress to the original commitment
- Cut items keep returning through side conversations
Outcomes
Outcomes and signals
What should exist after the playbook runs, how you'll know it worked, and what to watch for over time.
Artifacts to produce
Durable outputs the playbook should leave behind.
- Core outcome statement
- Scope classification
- Re-scope options brief
- New scope statement
- Updated plan
Success signals
Observable changes that mean the playbook landed.
- Stakeholders can repeat the new scope accurately
- Planning and reporting reflect the new promise cleanly
- The team feels reduced ambiguity, not just reduced ambition
- Work outside the new scope stops reappearing quietly
Follow-up actions
Moves that keep the playbook's effects compounding after it finishes.
- Review whether the original scope was under-specified or under-priced
- Capture how re-scoping decisions will be triggered earlier next time
- Re-evaluate deferred items later as fresh choices, not hidden obligations
Metrics or signals to watch
Longer-horizon indicators that the underlying problem is receding.
- Scope churn after reset
- Stakeholder alignment quality
- Reintroduced out-of-scope requests
- Milestone confidence after re-scope
AI impact
AI effects on this playbook
How AI-assisted and AI-driven workflows help execution, and the ways they can make it worse.
AI can help with
Where AI tooling genuinely reduces the cost of running this playbook well.
- Summarizing scope and dependency clusters
- Drafting option briefs and stakeholder communications
- Comparing original and revised commitments
AI can make worse by
Distortions AI introduces that make the underlying problem harder to see.
- Softening direct language into vague euphemisms
- Making scope changes sound cleaner than they are
- Creating too many option variants and delaying the decision
Relationships
Connected playbooks
Failure modes this playbook tends to address, decisions behind the situation, red flags that motivate running it, and neighboring playbooks.