The Ninth Woman.

Cue

The standup, grown long, and a task that will not divide. The team is larger now, and the day is filling with keeping it aligned, while the work on the critical path still waits on a single chain no crowd can split.

Action

Communicating: The Lead, holding the tech lead's seat, spends the day coordinating multiplying channels. Meanwhile partitioning fails at the critical task, and The Newcomer at the new hire's seat is still getting up to speed.

Stage

The Lead works Keep Everyone Aligned and The Newcomer works Get Up to Speed: the cross-talk grows as the square of the team, and the partition caps the hands the critical work can use. The added capacity is eaten by coordination and ramp before it reaches the line.

Tension

The team is bigger and the work is not faster. No one is idle: the lead is coordinating, the newcomers are learning, the veterans are teaching, and every hour is honestly spent. But coordination scales quadratically while output scales linearly at best, and the critical task cannot be parallelised at all, so the crowd's effort lands everywhere except where the schedule needed it.

Cue

The backlog, and someone who has stopped adding people and started removing work. The question has changed: not how many more hands will save the date, but how much less promise the date can actually hold.

Action

Descoping: The Cutter, holding the product owner's seat, cuts the scope to what a held team can truly ship and re-plans against it.

Stage

The Cutter tables Cut the Scope: shrink the promise rather than swell the team, so the descope makes the work fit the time and the man-month finally balances. The people who know the work are protected from dilution, and the date becomes real against a smaller promise.

Tension

The date is saved, and the promise it was made on is smaller. Cutting works, and it costs: it ships less than was promised, tells the customer the scope shrank, and looks like conceding while adding people looked like fighting harder. It trades the whole promise for a real one ... or the cut is refused as defeat, the crowd grows again, and the date recedes by the same move that moved it before.

Cue

The burndown, where the line that should fall has risen. The reinforcements have been on the project for weeks, and the forecast completion date is further out than it was before they came.

Action

Slipping: The Estimator, holding the planner's seat, re-forecasts and traces the movement to ramp-up and cross-talk, not slack.

Stage

The Estimator works Re-Forecast: report the date honestly, so the slip is shown to have widened under the additions and the man-month is named as the reason. Adding people made the project later, though everyone worked hard, exactly as the law says.

Tension

The one number that would open the cure is the one the crisis least wants to hear. To name the man-month is to say the additions slowed the project, which contradicts the visible response everyone approved; the easy move is to blame the new hires for not ramping faster and to demand still more of them. So the plot turns on a choice that is not about staffing at all: whether the slip is diagnosed ... or answered with another round of the thing that caused it.

Cue

The war room, then the onboarding. The heads are approved and arriving: capable people, seated into a project they do not yet know, and the veterans turning to teach them.

Action

Staffing: The Manager, holding the project manager's seat, brings the people on and books them into the plan. Then onboarding: The Veteran at the senior engineer's seat stops delivering to bring them up.

Stage

The Manager works Add the Heads and The Veteran works Onboard the New: the reinforcements land as capacity on the schedule, and the ramp-up begins to drain the project through the people who knew it best. The team is bigger the day they start, and slower for weeks after.

Tension

Everyone acts in good faith, and the project loses ground. The new hires are capable and the manager is doing exactly as asked, so nothing looks wrong; but the schedule counts the heads on arrival while the work returns only later, and the veterans who were the project's speed are now its teachers. The plan improves on paper precisely as it worsens in fact.

Cue

The gantt, where the bars have drifted past the line. The project is behind, the date will not move on its own, and the pressure in the room is for someone to do something about it.

Action

Slipping: The Sponsor, holding the sponsor's seat, reads the slip as a shortage of capacity and calls for more people.

Stage

The Sponsor tables Save the Date: hold the commitment and resource the gap, so the deadline stands and the slip is answered with headcount. The order is given for hands, because hands are the lever the seat can pull today.

Tension

Nothing here is unreasonable, and it sets the whole trap. A slipping date and a call for capacity is the picture of responsible ownership: act, resource, save the commitment. But the lever that is fastest to pull is the one that pulls the wrong way, because a head can be added in a day and progress cannot, and from this order on, the project will get later by the very move meant to speed it.

Tenor

Urgent, capable, sure the answer is more hands. The date is slipping, so bring in help: pull in the extra engineers, borrow the other team, all hands on deck until it ships. The voice of a project that trusts effort and reads a shortfall of time as a shortage of people.

Undertow

Under the urgency, a month that will not hold more people. The new hands must be taught, and the teaching is paid by the ones who were fastest; the channels multiply as the square of the team; and the task on the critical path cannot be split at all. No one is idle and no one unskilled: the help is real and arrives at the one moment the project cannot spend it, so the date it was meant to save moves further out.

Nerve

The feeling of a team that keeps growing and keeps falling behind, every added hand raising the effort and lowering the pace, and no one able to say why working harder is working slower.

Echo

After the run: a bigger team, a later date, a forecast that went backward the sprint the reinforcements landed, and the one move that would have made the date real, promising less or staffing early, still unmade, because a project in crisis would rather add people than admit it will do less.

Projection

Clear-eyed, unsentimental about scope. Willing to say the promise was too big before the team was too small. Reaches for the backlog, not the org chart, because the backlog is the lever that pulls toward the date.

Action

Cuts the scope to what a held team can truly ship, and re-plans against it. Protects the people who know the work from being diluted, and staffs early or not at all. Makes the date real by shrinking the promise, not by swelling the crowd.

Shadow

The cure looks like defeat and the disease looks like effort. The Cutter must ship less, visibly, while the alternative of adding people looks like fighting harder, so the honest move is the one hardest to defend in a room that wants the whole promise kept.

Tell

"We can't do all of it by the date. We can do the half that matters." Trades the whole promise for a real one, and wears the look of giving up.

Projection

Precise, honest, unwelcome. Keeps the schedule and the velocity, and reports what they actually show. Wants the forecast to improve after the hiring, and finds it worse.

Action

Re-runs the numbers after the reinforcements land and sees completion move further out. Traces the slip to ramp-up and cross-talk, not to slack. Names, out loud, that adding people made the project later.

Shadow

The true forecast is the one the crisis least wants to hear. To report that the additions slowed the project is to contradict the visible response everyone approved, so the honest number reads as pessimism and the easy story blames the new hires.

Tell

"We added six people and the date went out two weeks." The sentence that is either the diagnosis or the reason to hire six more.

Projection

Coordinating, conscientious, increasingly underwater. Holds the technical picture and keeps everyone aligned to it, a job that was manageable when the team was small. Watches the channels multiply and the day fill with keeping people in step.

Action

Runs the standups, reviews the work, answers the cross-team questions the larger team now generates. Spends more of each day coordinating and less building, as the paths between people grow. Keeps the team aligned at the cost of the throughput alignment was meant to protect.

Shadow

The coordination that holds the team together is the coordination eating its output. The Lead cannot cut the meetings without losing alignment, and cannot keep them without losing the day, so the team's size costs it speed in a way no one is doing wrong.

Tell

"I spent the whole day in sync meetings and shipped nothing." Names the quadratic tax, from the seat that pays most of it.

Projection

Responsive, organised, doing as asked. Given a mandate to add capacity, finds the people, clears the seats, and gets them started. Believes a bigger team is a faster team, because that is what the plan says.

Action

Staffs the late project: onboards the reinforcements and assigns them work. Books the new capacity into the schedule as though it were productive on arrival. Turns an order for speed into a larger team, in good faith.

Shadow

The team is bigger the day they start and slower for weeks after. The Manager adds capacity the schedule counts immediately and the work returns only later, so the plan improves on paper exactly as it worsens in fact.

Tell

"We've doubled the team. We should see it in the next sprint." Counts the heads on arrival and waits for a speed that is still ramping.

Projection

Eager, competent, keen to contribute. Arrives ready to work and finds a system they must learn before they can move in it. Will be genuinely productive, later, and knows it is not yet.

Action

Learns the codebase, the conventions, the context, asking the questions only the veterans can answer. Takes small tasks, checks often, ships little while the map is still forming. Consumes more attention than they return, through no fault, for as long as ramp-up lasts.

Shadow

Being added late is not the same as being useful late. The Newcomer is a good engineer whose value is real and deferred, and the project needed value now, so their arrival is help the deadline cannot yet spend.

Tell

"Once I'm up to speed I'll be able to take real load off you." True, and dated after the milestone the hiring was meant to hit.

Projection

Decisive, accountable, out of patience. Owns the commitment to the customer and the board, and will not be the one to move it. Reads a slip as a resourcing problem, because resourcing is what a sponsor can authorise.

Action

Sees the project behind and calls for capacity: more people, now. Approves the headcount, signs the budget, and expects the curve to bend. Treats hands as the fastest lever, because it is the fastest one to pull.

Shadow

The lever that is fastest to pull is the one that pulls the wrong way. The Sponsor can add people in a day and cannot add progress in a day, and the difference between the two is the whole misfit, invisible from a seat that reads headcount as speed.

Tell

"Whatever it takes. Get more people on it." The most natural order to give, and the one that makes the date recede.

Projection

Skilled, generous, quietly stretched. Knows the system deeply, which is exactly why the newcomers are routed to them. Wants the project to ship and is now the bottleneck for everyone learning how.

Action

Stops delivering to onboard the reinforcements: answers questions, pairs, explains the context that lives in their head. Transfers knowledge one conversation at a time, because that is the only speed it moves. Becomes the project's teacher at the cost of being its fastest builder.

Shadow

The person best able to move the work is the person taken off it to grow the team. The Veteran's time is the scarce resource the additions consume, so adding hands subtracts the one pair that was already productive.

Tell

"I'd be done already if I weren't answering questions all day." Names the drain precisely, from the seat the drain runs through.

Shown

A list of what was promised, and a hand deciding what will not be done. The features ranked, the release narrowed, the cut line drawn through the middle of the plan.

Holds

The one lever that pulls toward the date, and the concession it costs. The place work can be shortened instead of the team lengthened, where the promise is made to fit the time and the team that already knows it.

Offers

A date that can actually be met. Here the schedule stops being a wish: cut to what the held team can ship, and the line becomes real for the first time.

Withheld

The whole promise. The backlog buys a real date with a smaller one, and takes, in return, the features cut and the look of having given up, which is why it is the last place the crisis is willing to go.

Shown

A line that should fall to zero, flattening, then rising. Velocity by sprint, the forecast completion, the honest picture of whether the work is closing or opening.

Holds

The slip, and the proof that the additions did not help. The place the man-month is caught in the act: the date after the hiring further out than the date before it.

Offers

The truth about the trade. Here, and nowhere in the war room, the effect of adding people can be seen as it was, the schedule going backward while everyone worked harder.

Withheld

A comfortable reading. The burndown shows the slip plainly and offers no way to blame it on slack, so the room must either name the law or reach past the chart for a story that spares the decision.

Shown

Bars across a calendar, dependencies as arrows, a hard line for the date. The plan as management sees it: tasks, durations, and the people assigned, all in one picture that reads capacity as time.

Holds

The deadline, and the critical path that no crowd can shorten. The place the man-month lives, where ten people for a month and one for ten look like the same bar.

Offers

A plan that looks resourceable. Here a slip appears to have an obvious fix: a task waiting, a bar to fill, another pair of hands to assign.

Withheld

The sequence that caps the hands. The Gantt shows a task as assignable and hides that its constraint is order, not availability, so the one bar that cannot be parallelised looks exactly like the ones that can.

Shown

Pairing sessions, setup guides, a queue of questions. The place a new hand becomes a working hand: context transferred, conventions absorbed, the map slowly drawn.

Holds

The ramp-up, and the drain it takes from the people who knew the work. The weeks where a newcomer produces little and a veteran produces less, because teaching is where their time now goes.

Offers

A more capable team, later. Here capability is genuinely built, an investment that will pay back once the ramp is climbed.

Withheld

Now. The onboarding gives the project value on the far side of the ramp and withholds it in the exact window the deadline needed it, so its payback lands after the milestone it was meant to save.

Shown

A circle that used to be quick, now long. The daily sync, the review queue, the threads: the ceremonies that keep a team aligned, swelling as the team does.

Holds

The cross-talk, and the channels that multiply as the square of the head count. The place the communication tax is paid, where each added person adds paths faster than they add output.

Offers

Alignment. Here everyone stays in step, decisions are shared, and no one is left out of the loop that a large team needs to stay coherent.

Withheld

The hours it takes. The standup keeps the team aligned and takes from the day the time that alignment costs, so the coordination that holds the team together is the coordination eating its throughput.

Shown

A tense meeting, a red status, a date under threat. The room where a slipping project is escalated and something must be decided, now, in front of everyone who owns the outcome.

Holds

The pressure, and the reach for the fastest visible lever. The moment a slip turns into a call for capacity, because capacity is the thing the room can authorise on the spot.

Offers

A decisive response. Here a project in trouble can be seen to act: heads approved, budget released, a plan that looks like it is being saved.

Withheld

The weeks between the decision and its cost. The war room delivers a fast answer and cannot show the ramp-up and cross-talk it sets in motion, so the move that feels like rescue is the move that deepens the slip.

Place

At the standup, grown long, in the syncs and threads that now take a share of every day. The meetings that used to be quick, the decisions that now need more people in the room, the n paths becoming n times n-minus-one over two: coordination that scales as the square of the team.

Load bearing

Without it a bigger team would simply be more output and adding people would always help. With it output grows linearly at best while coordination grows quadratically, so past a point each new person costs more in cross-talk than they add in work. The Cross-Talk is load bearing because it is the second tax on size: even after ramp-up, the team is slower per head than it was small, and the slowdown is structural, not slack.

Apparent

Good communication. It looks like a well-run team: everyone in sync, decisions aligned, no one left out of the loop. And it is real coordination, honestly needed, which is why its cost is so hard to cut, the meeting that must happen is also the meeting eating the day.

Yearbook

Felt most by the lead through communicating, across a team that keeps growing. It is the second cost of the reinforcements: the Cross-Talk eats the capacity the ramp-up did not, and together they are why the man-month does not add up.

Place

At the gantt, a hard line drawn down the calendar that the work keeps failing to reach. The launch, the release, the promise to the customer: a commitment made when the plan looked achievable, now standing over a project that has fallen behind it.

Load bearing

Without it lateness is just a rate, and no one reaches for a lever. With it there is a fixed point the schedule must hit and is missing, so pressure builds toward the one move that looks like more speed: add people. The Deadline is load bearing because it is what turns a slip into a crisis, and a crisis into the decision that deepens it.

Apparent

A reasonable commitment. It looks like discipline, a date to rally around, the thing that keeps a project honest. And it is, until it becomes the reason to add hands to work that cannot take them.

Yearbook

Held over the project by the sponsor, and missed through slipping. It is the pressure the play opens under: the Deadline is what the slip measures against, and the promise the descope must shrink to make real.

Place

At the backlog, where scope is removed rather than capacity added. The features cut, the release narrowed, the honest re-plan against what a held team can truly ship: the retreat that makes the date a date again.

Load bearing

Without it the only lever the schedule believes in is headcount, and the slip has no honest floor. With it there is a move that actually shortens the work instead of lengthening the team: cut the scope so the remaining work fits the time and the team that already knows it, or add the people early enough that ramp-up finishes before the deadline matters. The Descope is load bearing because it is the one lever in the play that pulls toward the date instead of away from it.

Apparent

Giving up. Admitting defeat. It looks like failure: shipping less than promised, telling the customer the scope shrank, conceding the plan was wrong. That reading is why it is the last resort, because cutting the promise is visible and swallowing the slip is not, and a project would rather add people than say it will do less.

Yearbook

Made by the cutter through descoping, against the pull of the deadline. It is the remedy the play holds: the Descope answers the slip by shrinking the work, and it is the only move that makes the man-month balance, a smaller promise the team can actually keep.

Place

At the gantt, where headcount and time are laid on the same axis and treated as one currency. Not one slip but the unit itself: the man-month, the assumption that ten people for one month equals one person for ten, held by every plan that converts people into time and time into people.

Load bearing

Without it the play is one unlucky project that hired badly. With it there is a named law it stands on: adding manpower to a late software project makes it later, because effort and progress are the same only when work partitions without communication, and real work does neither. The Man-Month is load bearing because it holds both the law and its remedy, that the schedule's error is the unit, and the fix is to spend less scope rather than more people.

Apparent

A sensible planning unit. It looks like arithmetic: budget in person-months, add capacity to buy time, the oldest move in project management. That is the disguise, because the unit quietly assumes the one thing the work refuses, that a month can be filled with any number of people, and the assumption is invisible right up to the slip.

Yearbook

Assembled from the ramp-up, the cross-talk, and the partition, and answered by the descope. It is the law the play runs on: the Man-Month is why the reinforcements deepen the slip, and why the only way out is a smaller promise, not a larger crowd.

Place

At the gantt, on the critical path, in the task with a dependency chain and no parallel seam. The integration that must follow the build, the design that must precede them both, the sequence that cannot be run at once: the bearing that takes nine months no matter how many are assigned.

Load bearing

Without it every task could be split across more hands and headcount would always buy time. With it there is work whose sequence caps the number of useful hands, so past that cap another person is not another day saved but only another channel to keep in sync. The Partition is load bearing because it is why the man-month is a myth: months and people trade evenly only where the work divides, and the work on the critical path is exactly where it does not.

Apparent

A task like any other, waiting for someone free. It looks assignable, a card on the board that another pair of hands could pick up, so adding people looks like it must help. That is the trap, because the task's constraint is not availability but sequence, and no amount of availability shortens a chain.

Yearbook

Met by every added hand through partitioning, and unmoved by any of them. It is the hard floor under the cross-talk: the Partition is why more people cannot finish the critical work sooner, the reason the man-month holds even when ramp-up and coordination are paid.

Place

At the onboarding, in the weeks a newcomer spends learning the system and the veteran spends teaching instead of building. The pairing sessions, the questions, the context that lives in heads and must be transferred one conversation at a time: real assimilation, which takes as long as it takes.

Load bearing

Without it added people would be productive the day they arrive and Brooks's Law would not bite. With it every addition subtracts twice at first: the newcomer produces little, and the person who could have been producing is teaching instead, so the project's output drops exactly when it needed to rise. The Ramp-Up is load bearing because it is why capacity added late is capacity lost first, and lost from the people who were the project's speed.

Apparent

Investment in the team. It looks like the right thing, growing capability, bringing people up, a cost that pays back later. And it does pay back later, which is precisely the problem, because later is on the far side of the deadline the additions were meant to save.

Yearbook

Paid by the veteran and the newcomer through onboarding. It is the first cost of the reinforcements: the Ramp-Up drains the project before it feeds it, and its bill comes due inside the exact window the deadline could least afford.

Place

At the war room, named as the answer to the slip and moved onto the project. The extra engineers, the borrowed team, the new headcount approved in a hurry: real capacity, honestly meant to help, arriving into a system they do not yet know.

Load bearing

Without it the late project stays its own size and the schedule finds no false lever to pull. With it there is capacity added exactly where capacity cannot be absorbed cheaply, so the help arrives as a cost first: the Reinforcements are load bearing because they are the intervention the law turns against, not a worse class of worker but the right people at the wrong moment.

Apparent

Help arriving. It looks like relief: more hands, more capacity, a visible response to a slipping date that everyone can point to. That reading is the trap, because the hands are counted as speed the moment they are hired, and paid for as drag for weeks after.

Yearbook

Brought on by the manager through staffing, into a project already behind. It is the move the play turns on: the Reinforcements trigger the ramp-up and the cross-talk, and their arrival is what the man-month counts as capacity and the work counts as cost.

Place

At the burndown, in the line that should fall and instead flattens, then climbs. The forecast that keeps moving out, the velocity that dropped the sprint after the team grew, the completion date further away in the review than it was before the reinforcements came.

Load bearing

Without it adding people is at worst neutral and the law is only caution. With it the outcome is perverse and measured: the project is not merely un-helped by the additions, it is later because of them, ramp-up and cross-talk together outrunning the capacity added. The Slip is load bearing because it is the harm the play exists to show, the date going backward while everyone works harder.

Apparent

Just a project that was always going to be late. It looks like the lateness that prompted the hiring, ongoing, so the additions escape blame and even seem to have softened it. That reading is the trap's defence, because it credits the reinforcements with slowing the slide they widened, and calls for yet more of them.

Yearbook

Tracked by the estimator through slipping, against the deadline. It is the reckoning of the play: the Slip is what the reinforcements produced, the number that names the man-month, and the date the descope must shrink the promise to meet.

Has

Genuine skill, and a system to learn before the skill can land. A willingness to help, and a ramp that must be climbed before the help arrives.

Orders

Get up to speed: learn the codebase, the conventions, the context. Take small tasks, ask the questions, ship what you safely can. Become productive, on the ramp's timetable, not the deadline's.

Loses

The present, which is when the project needed the value. A seat whose worth is real and deferred cannot serve a milestone that has already passed by the time the ramp ends.

Drives

Toward a capable contributor later, and away from the help the date could spend now. Toward attention consumed before work returned, through no fault of the seat.

Has

The schedule, the velocity, and the duty to report them truly. The one view that can compare the date before the hiring to the date after.

Orders

Re-forecast honestly: run the numbers after the reinforcements and say what they show. Trace the slip to its causes, ramp-up and cross-talk, not slack. Name the direction the date actually moved.

Loses

The welcome of the room, when the true number contradicts the visible fix. A seat that reports the additions slowed the project speaks against the response everyone approved, so honesty reads as pessimism.

Drives

Toward the slip named plainly, or toward the easy story that blames the new hires and buys more of them. Toward the diagnosis, from the one seat that can see the date go the wrong way.

Has

Authority over scope, and the standing to shrink the promise. The one lever in the play that pulls toward the date: the backlog, not the org chart.

Orders

Cut the scope to what a held team can truly ship, and re-plan against it. Protect the people who know the work from dilution, and staff early or not at all. Make the date real by promising less, not by crowding more.

Loses

The whole promise, and the look of fighting hard. A seat that ships less on purpose must defend a visible concession against the invisible cost of the slip it avoids.

Drives

Toward a smaller promise the team can keep, and away from the crowd that makes the date recede. Toward the one move that shortens the work instead of lengthening the team, at the cost of the scope given up.

Has

The mandate to staff the project and the schedule to book them into. The levers of delivery: assignments, seats, a plan that counts capacity as it arrives.

Orders

Add the heads the sponsor authorised and get them working. Book the new capacity into the schedule as productive, and expect the next sprint to show it. Turn the order for speed into a larger team.

Loses

The lag between a head starting and a hand producing. A seat that counts capacity on arrival cannot see the weeks of ramp-up before it returns, so the plan improves exactly as the project worsens.

Drives

Toward a bigger team booked as faster, and away from the truth that the work returns later than the headcount. Toward a schedule that reads full and a project that runs slow.

Has

Deep knowledge of the system, and therefore every newcomer's questions. The scarce context the project runs on, held in one head and transferable only slowly.

Orders

Onboard the reinforcements: pair, explain, answer, transfer what you know. Bring the new people up, because you are the one who can. Grow the team's capability out of your own delivery time.

Loses

The hours that were the project's fastest output. A seat routed every question cannot also be the fastest builder, so the additions subtract the one pair of hands that was already producing.

Drives

Toward a team that will be capable later, and away from the delivery the deadline needed now. Toward knowledge transferred one conversation at a time, at the price of the work only this seat could do.

Has

The commitment to the customer, and the budget to add people to keep it. The authority to pull the fastest visible lever the moment the project slips.

Orders

Save the date. Add whatever capacity it takes and expect the curve to bend. Read a slip as a resourcing problem, and resource it. Do not be the one who moves the commitment.

Loses

The distinction between headcount and progress. A seat that can approve heads in a day and cannot approve progress in a day cannot see why the first does not buy the second.

Drives

Toward more people on a late project, counted as more speed, and away from the smaller promise that would actually fit. Toward the lever that is fastest to pull and pulls the wrong way.

Has

The technical picture, and the duty to keep everyone aligned to it. The coordination surface of the whole team, which grows as the team does.

Orders

Keep everyone aligned: run the standups, review the work, answer the questions the larger team generates. Hold the shared picture as the paths between people multiply. Coordinate first, because misalignment is worse than a lost hour.

Loses

The hours coordination takes from building. A seat whose alignment work grows as the square of the team spends more of each day in sync and less in delivery, and cannot cut either without cost.

Drives

Toward a team held together and a day eaten by holding it, and away from the throughput coordination was meant to protect. Toward the quadratic tax that turns a bigger team into a slower one per head.

Initiated by

A team large enough that alignment can no longer be assumed. The moment the paths between people multiply, coordination becomes work.

Direction

From easy alignment toward expensive alignment. It moves toward more meetings, more reviews, more threads, as the channels grow.

Lever

The need to stay coherent meeting the arithmetic of n(n-1)/2. The force is the honest need to align; the resistance is that channels grow as the square while output grows at best linearly.

Echo

A team aligned and a day consumed aligning it. It hands forward coherence bought with the very hours that would have been delivery, slower per head the larger it gets.

Initiated by

Someone deciding to change the promise rather than the headcount. When the slip is faced honestly, the work of cutting scope can begin.

Direction

From the whole promise toward one the team can keep. It moves toward a smaller release, re-planned against the held team and the real date.

Lever

Authority over scope meeting the pull of the original commitment. The force is the will to promise less; the resistance is that cutting is visible and swallowing the slip is not.

Echo

A date made real, and a promise made smaller. It hands forward a plan the team can actually meet, bought with the features cut and the concession owned.

Initiated by

A newcomer arriving into a system they do not yet know. The moment they are seated, the transfer of context must begin.

Direction

From a net drain toward an eventual gain. It moves toward a productive engineer, slowly, on the ramp's own timetable.

Lever

The veterans' knowledge meeting the newcomers' need for it. The force is real assimilation; the resistance is that it moves one conversation at a time and spends the scarce hands to do it.

Echo

Capability built, and delivery drained meanwhile. It hands forward a team that will be faster later, at the cost of the output the deadline needed now.

Initiated by

More hands than the task can use, looking for a way to split it. Once capacity exceeds the parallel work, the search for divisible pieces begins.

Direction

From one task toward many, until the sequence refuses. It moves toward parallelism up to the point the dependencies cap, and no further.

Lever

Available hands meeting a critical path. The force is the wish to parallelise; the resistance is a chain of dependencies that no number of people can shorten.

Echo

A hard floor under the schedule. It hands forward the truth that beyond the partition, another person is another channel, not another day saved, the ninth woman on a nine-month task.

Initiated by

Work taking longer than the plan assumed. The moment actuals diverge from the schedule, the date begins to move.

Direction

From a plan on track toward a date that keeps receding. It moves toward pressure, and pressure toward the reach for a lever.

Lever

Reality meeting an optimistic estimate. The force is the work's true difficulty; the resistance is a schedule that will not admit it and a room that wants it hidden.

Echo

A crisis, and a demand for capacity. It hands forward a slipping date and the instinct to save it with headcount, the instinct the law turns against.

Initiated by

An authorised demand for more capacity. Once the crisis calls for hands, the work of finding and seating them begins.

Direction

From a small late team toward a larger late team. It moves toward more headcount on the schedule, booked as productive on arrival.

Lever

Available capacity meeting a project that cannot yet absorb it. The force is real hiring power; the resistance is that a late project is the worst place to put a new hand.

Echo

A bigger team and a heavier ramp. It hands forward capacity the schedule counts now and the work returns later, triggering onboarding and cross-talk.

Direction

Carry out the order: bring the people on, seat them, assign them, and book the new capacity into the schedule as productive from the start.

Orders

(The Manager onboards the reinforcements and slots them into the plan, expecting the next sprint to show the gain.)

Implementation

(The War Room; the staffing process; a schedule that counts a head on arrival and waits for a hand that is still ramping.)

Targets

• [ ] the authorised people are hired or borrowed and seated
• [ ] the new capacity is assigned work
• [ ] the schedule books the heads as productive now
• [ ] the lag between starting and producing is not modelled

Direction

Shrink the promise to what a held team can truly ship, and re-plan against it. Move the backlog, not the org chart, and staff early or not at all.

Orders

(The Cutter cuts scope to the half that matters, protects the people who know the work, and makes the date real by promising less.)

Implementation

(The Backlog; the descoping process; the one lever that shortens the work instead of lengthening the team.)

Targets

• [ ] the scope is cut to what the held team can ship
• [ ] the plan is remade against the smaller promise
• [ ] the people who know the work are protected from dilution
• [ ] the date is made real by promising less, not crowding more

Direction

Learn the system well enough to help: absorb the codebase, the conventions, the context, and take on real load as soon as the ground is solid.

Orders

(The Newcomer works small tasks, asks the questions only veterans can answer, and ships what they safely can while the map forms.)

Implementation

(The Onboarding; the onboarding process; a ramp that ends on its own timetable, not the deadline's.)

Targets

• [ ] the codebase and conventions are learned
• [ ] small tasks are taken and checked often
• [ ] questions consume the veterans' attention
• [ ] real productivity arrives after the milestone that prompted the hire

Direction

Hold the shared technical picture as the team grows: run the standups, review the work, and answer the questions a larger team generates, so no one drifts out of step.

Orders

(The Lead spends more of each day coordinating the multiplying channels, keeping alignment as the paths between people grow.)

Implementation

(The Standup; the communicating process; coordination scaling as the square of the team while output scales at best linearly.)

Targets

• [ ] the standups and reviews are run
• [ ] the growing team is kept aligned
• [ ] more of each day goes to coordination than before
• [ ] the quadratic tax is paid and cannot be cut without losing alignment

Direction

Bring the newcomers up: pair, explain, answer, and transfer the context the system runs on, because you are the one who holds it.

Orders

(The Veteran stops delivering to teach the reinforcements, moving knowledge one conversation at a time.)

Implementation

(The Onboarding; the onboarding process; the project's scarcest hands spent teaching instead of building.)

Targets

• [ ] the newcomers are paired and mentored
• [ ] system context is transferred from the veterans
• [ ] the veterans' delivery time is spent on teaching
• [ ] the project's fastest hands are off the work while they teach

Direction

Run the numbers again after the reinforcements and report the date honestly, whichever way it moved, and trace the movement to its real causes.

Orders

(The Estimator re-forecasts, finds completion further out, and names ramp-up and cross-talk rather than slack.)

Implementation

(The Burndown; the slipping process; an honest forecast the crisis least wants to hear.)

Targets

• [ ] the schedule is re-forecast after the hiring
• [ ] the date is reported truly, even if it worsened
• [ ] the slip is traced to ramp-up and cross-talk
• [ ] the finding is offered against the room's wish for good news

Direction

Hold the commitment and hit the date. Read the slip as a shortage of capacity, and authorise whatever headcount it takes to bend the curve back.

Orders

(The Sponsor sees the project behind, approves the budget for more people, and expects the schedule to recover.)

Implementation

(The War Room; the slipping project; the fastest visible lever, headcount, pulled without seeing it pulls the wrong way.)

Targets

• [ ] the slip is read as a resourcing problem
• [ ] capacity is authorised to save the date
• [ ] the commitment is held rather than moved
• [ ] headcount is counted as the speed it is not