Frame scope, time, and quality explicitly
Make the fixed and flexible parts of a delivery commitment visible so stakeholders understand what can move, what cannot, and who can approve changes.
- Situation
- A team is making or revising a delivery commitment and the real trade-offs are not explicit.
- Goal
- Prevent hidden trade-offs by turning delivery commitments into explicit scope, time, quality, and risk choices.
- Do not use when
- the work is still pure discovery
- Primary owner
- delivery lead
- Roles involved
delivery leadproduct ownerengineering managertech leadquality leadstakeholder sponsor
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.
- A date is socially or politically important
- Scope is being negotiated under pressure
- Teams disagree about what done means
- Stakeholders want certainty across several constraints
Stakes
Why this matters
What this playbook protects against, and why skipping or half-running it tends to be expensive.
Most delivery conflict starts when different people believe different constraints are fixed. Making the constraint explicit lets the team manage reality instead of discovering it late.
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
- Everyone can say which constraint is fixed
- Scope cuts are recorded in plain language
- Quality guardrails are named
- Decision authority for trade-offs is explicit
- Status reports mention changes to the trade-off, not only progress
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.
- Delivery goal
- Stakeholder commitments
- Scope list
- Quality and risk guardrails
- Dependency map
Prerequisites
Conditions that should be true for this to work.
- A named delivery outcome
- Stakeholders willing to discuss trade-offs
- Minimum understanding of constraints
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.
Name the outcome and constraints
Separate the desired result from the constraints around it.
Actions
- Write the delivery outcome in one sentence
- List time, scope, quality, staffing, and risk constraints
- Mark which constraints are believed to be fixed
Outputs
- Constraint map
- Delivery outcome statement
Choose what can flex
Make the adjustable dimension explicit before pressure arrives.
Actions
- Identify scope that can be cut or deferred
- Name quality bars that cannot be lowered
- Agree who can approve each kind of trade-off
Outputs
- Fixed-vs-flexible record
- Trade-off authority map
Convert scope into promises
Avoid vague commitment language.
Actions
- Classify work as must-have, candidate, or deferred
- Write what each cut means for users or operations
- Remove ambiguous items from the committed promise
Outputs
- Commitment scope
- Deferred scope list
Review the trade-off regularly
Keep the commitment truthful as delivery reality changes.
Actions
- Review constraint changes during status meetings
- Record approved trade-offs
- Communicate changes in plain language
Outputs
- Trade-off log
- Updated commitment note
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.
- Is date, scope, quality, or risk the fixed constraint?
- Who can approve scope reduction?
- Which quality bars are non-negotiable?
- What user value remains if candidate scope is cut?
Questions worth asking
Prompts to use on yourself, the team, or an AI assistant while running the procedure.
- Which constraint is fixed in this plan?
- What scope can move without destroying the core outcome?
- Where does this status update imply a trade-off without naming it?
Common mistakes
Patterns that surface across teams running this playbook.
- Calling everything fixed
- Cutting scope without naming the user consequence
- Letting quality become the silent flexible constraint
- Using planning artifacts that hide trade-offs
Warning signs you are doing it wrong
Signals that the playbook is being executed but not landing.
- Nobody can say what is fixed vs flexible
- Scope cuts reappear at delivery
- Status sounds green but risks are rising
- Stakeholders interpret the same commitment differently
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.
- Fixed-vs-flexible record
- Scope commitment list
- Quality guardrails
- Trade-off authority map
- Trade-off log
Success signals
Observable changes that mean the playbook landed.
- The team can explain the current trade-off in plain language
- Stakeholders know what changed and why
- Scope cuts do not silently return
- Delivery confidence is tied to evidence and constraints
Follow-up actions
Moves that keep the playbook's effects compounding after it finishes.
- Review trade-off drift weekly
- Update scope records after stakeholder decisions
- Connect this framing to delivery status reports
Metrics or signals to watch
Longer-horizon indicators that the underlying problem is receding.
- Unapproved scope changes
- Age of unresolved trade-offs
- Quality guardrail breaches
- Stakeholder interpretation mismatch
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 options
- Drafting trade-off language
- Finding ambiguous commitment wording
- Comparing plan changes over time
AI can make worse by
Distortions AI introduces that make the underlying problem harder to see.
- Making unrealistic plans look coherent
- Turning hard trade-offs into soft alignment language
- Generating status summaries that hide constraint changes
Relationships
Connected playbooks
Failure modes this playbook tends to address, decisions behind the situation, red flags that motivate running it, and neighboring playbooks.