Skip to main content
Next Step PM
Back to the library

Build · Core

Make scope trade-offs without losing the goal

Every build hits surprises. When time runs short, cut or simplify work in a way that still meets the user need and the success metric, and make the decision openly.

About 1-4 hoursEvergreenLast reviewed 5 November 2026

Who this applies to

Skills it builds
Prioritisation and roadmappingDelivery and execution
PM types
All
Product types
All
Starting points
All
Ways of working
All
Experience
All
Size of organisation
All

Steps, by experience

Beginner (under 1 year)

  1. When the team raises a problem, first ask what it affects: the date, the scope or the quality.
  2. Go back to the goal and the main user need. Which items are essential to meet it?
  3. Look for simpler versions of the hard parts, such as a manual step behind the scenes for the first release.
  4. Never cut accessibility, security or legal requirements to save time.
  5. Agree the change with the team, then tell stakeholders what changed and why.
  6. Move anything cut to the 'next' list so it is not lost.

Intermediate (1 to 4 years)

  1. Assess the impact of each issue on date, scope and quality.
  2. Use the goal and metric to decide what to simplify or defer.
  3. Protect non-negotiables such as accessibility and security.
  4. Record and communicate each trade-off.

Experienced (5+ years)

  1. Set trade-off rules with stakeholders before the build starts.
  2. Spot scope creep early and challenge it with evidence.
  3. Use trade-off decisions to keep the team focused and morale high.
  4. Review trade-offs at the end to improve future planning.

Who can do this

Owner: Product manager

Can be delegated to

  • Tech Lead or Full-stack Engineer: Propose simpler technical options
  • UX Designer: Design a simpler version that still meets the user need
  • Delivery Manager or Scrum Master: Show the impact on the plan

Reviewed by: Tech Lead, UX Designer

Tool examples

Jira
Move deferred items to the next release version so the decision is visible.
Confluence
Keep a short decision log with each trade-off and the reason.
Linear
Label deferred issues and move them to a later cycle.

Definition of done

  • Trade-off decided against the goal and metric
  • Non-negotiables protected
  • Decision recorded and shared, with deferred work kept

Common pitfalls

  • Cutting quality or accessibility quietly
  • Adding scope without removing anything
  • Making trade-offs without telling stakeholders

If you lead the team

What good looks like: When time runs short, teams cut or simplify scope while still meeting the user need.

Ask your PM

  • What did we cut or simplify, and does the release still meet the need?
  • Who agreed the trade-off?

Warning signs

  • Quality or accessibility is quietly cut to hit a date.
  • Scope never changes, so dates always slip.

Do these first

Sources