The Scope Cut That Saved the Project

P64.tradeoff-narratives.03 · Audience: guest, it-ml, language-pro · Prerequisites: Saying No — and Being Thanked for It

Deciding at 60% Information The Failure Story That Builds Trust

LLM grading (this page):Real gradingOff — no LLM calls

Three weeks before a museum's audio-guide relaunch, the project is a month behind and the team is quietly working weekends to deliver everything anyway. The lead does the unpopular arithmetic instead: the guide in four languages ships polished on launch day, four further languages and the quiz move to a dated phase two, and the kids' version is cut outright with a written explanation to the education officer — who, six months later, cites that explanation as the reason she still trusts the team. A rival project "protects morale" by cutting nothing, slips the date twice, and ships everything at three-quarters quality — nothing anyone is proud of. A scope cut is not the project failing. Done deliberately, it is the trade that spends the parts to save the whole — and this module teaches how to choose the cut, announce it without the smell of defeat, and tell the story afterwards, including the hardest version: a quarter with three stakeholders and one deliverable.

🗺️ So far you have built: the professional no (module 01) — constraint, cost of yes, alternative, and asks ranked against one agreed criterion — and the 60%-information machinery (module 02): fog maps, reversible doors, smallest committing steps, announced tripwires. Both dealt with trades made at the start, when the plan is drawn. This module is about the trade made in the middle, when the plan is already slipping and every option costs something someone was promised.

In this module you will: the deliberate scope cut. You will learn to find the core promise before touching anything, so the cut protects it instead of wounding it; to choose which piece goes using recovery value, distance from the core, and whether the cut can be a defer rather than a delete; to announce the cut so it reads as the plan adapting, not the plan failing — protected thing first, affected party told personally, return date named; and to tell the scope-cut story, including the quarter where three stakeholders wanted three things and one shipped. The ladder closes it: choose and defend a cut in an overrun project you are given, then tell your own scope-cut story where the cut protected the core.

Step 1 / 6 — The cut is a decision, not a defeat

When a project overruns, the options are always the same four: move the date, add people, lower the quality, or shrink the scope. The first is often not yours to move, the second famously makes late projects later, and the third is the coward's cut — quality reductions are scope cuts made secretly, discovered by users instead of decided by you. That leaves scope: the one lever that can be pulled deliberately, visibly, on your terms. An overrun project sheds something no matter what; the question is whether what it sheds is chosen (a feature you name, this week, with a plan) or unchosen (the date, the quality, or the team, silently). Cutting scope is not admitting the plan failed. It is refusing to let the failure pick the sacrifice.

ⓘ Concept: Something will be cut — choose it, or it chooses itself

overrun → the trade happens regardless; deliberate scope cut = the only version where you pick what is spent and what is saved

Why it matters — Teams that treat scope as sacred do not actually protect it; they just transfer the cut to whichever variable has no defender in the room, and that is usually quality or the team's health — the two cuts hardest to see and slowest to heal. Naming this out loud ('we are shedding something; let's pick') is what makes the rest of the module possible, because it moves the conversation from whether to cut to what to cut, which is a decision with criteria instead of a fight about optimism. It also changes the emotional register: a chosen cut is an act of control and reads like one, to the team and — told properly — to an interviewer. The lead who cut the kids' version made a decision; the rival who cut nothing had three-quarters quality decided for them.

✅ Key takeaways

An overrun project sheds something regardless — date, quality, or team health if not scope. The deliberate cut is the only version where you choose what is spent and what is saved; refusing to cut is choosing the three-quarters-quality ship.
Write the core promise as one sentence — who gets what, or the project failed — then cut whole pieces from the edges. Never salami-slice everything evenly to spread the pain: a core shipped at eighty percent is a broken promise with good intentions.
Choose the piece on three axes: real recovery (does it actually close the gap?), distance from the core (who loses it?), and defer versus delete (a real date with a named owner costs a fraction of a delete — a fake phase two costs double).
Announce protected-thing-first, as a decision with reasoning shown, and the affected party hears it from you personally — before the general channel — with the return date. The announcement is the project, as far as most stakeholders can see.
In the three-stakeholders quarter story, the two no's are the story: criterion agreed, ranking shown, refusals delivered personally with dated alternatives, the one yes shipped well, the deferred asks returned unprompted — and the people who lost stay on stage to the end.
The reasoned no, the sixty-percent decision, and the deliberate cut complete the track's trilogy of trades — each one a judgment call you could defend; the next pillar takes the branch where the call went wrong, and teaches owning the failure so honestly that the telling itself builds trust.

Next: P65.owning-failure.01 — The Failure Story That Builds Trust

None of this needs a technical field: the asymmetric cut runs on syllabi and model roadmaps alike, wherever a plan meets a calendar that will not move.

Ask the mentor about this module

Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.

Images, PDF or text. Kept on this device only.

Keeping your files on this device

Keep a copy of the files I attach, in this browser

Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.

Ctrl/Cmd + Enter to send

🎓 Practice ladder

2 graded rungs · ~20 min

Two mentor-graded craft rungs. Rung 1 hands you an overrun community-centre website relaunch and three candidate cuts with real numbers attached — choose the cut, justify it against the core promise, write the announcement. Rung 2 is your own scope-cut story, told so the cut visibly protected the core; a low-stakes story is always an accepted substitute. The mentor grades the telling, never your history.

Rung 1 — Choose the cut, write the announcement (explorer)

Loading exercise…

Rung 2 — Your cut, and the core it saved (practitioner)

Loading exercise…

Try it yourself

A scratch console for this page's ideas — ungraded, nothing you run here is recorded.

Scratch console

A scratch console with the scientific stack (pandas, numpy, scikit-learn). Runs on the server — no network, resource-limited and measured.

Output appears here.

My notes on this module

Loading your notes...

Where next?

Continue

The Failure Story That Builds Trust →

Owning Failure · P65

Go up a level