Situation walkthrough: the hard conversations

The last chapter of the book is the five conversations engineers lose sleep over, played out in full: slipping a date face to face, reclaiming taken credit, being put on the spot by an executive, receiving a harsh review, and refusing a colleague. Each scene shows the words, the annotation shows the machinery, and a "if it goes sideways" note covers the branch where the other person does not cooperate.

Scene 1: slipping the date, in person

The 1:1, Tuesday. Alex has known since Monday morning that the migration will miss Friday.

Alex:  Before anything else: the migration won't make Friday. Tuesday
       is the honest date. The backfill runs 4x slower against prod
       data than staging predicted; I found out yesterday and spent a
       day confirming it's real before bringing you a false alarm.
       Two options: take Tuesday, or hold Friday by skipping the
       audit table and backfilling it next week. Both are safe; I
       lean taking Tuesday.

Dana:  Marketing has the announcement queued for Friday.

Alex:  Then option B may genuinely be better; the audit table isn't
       user-visible. What I don't want is to discover a third
       constraint on Thursday. Who else is planning around Friday?

Dana:  Let me find out. Good flag; I'd much rather redo a plan today
       than apologize on Friday.

Annotations: bad news first, no throat-clearing (Chapter 10); the delay between knowing and telling is explained (confirming, not hiding); options arrive with the news; and Alex's question ("who else is planning around Friday?") treats the date as a shared system, not a personal failing. Note what is absent: apology spirals, blame of the staging environment, and optimism theater ("we might still make it if everything goes perfectly").

If it goes sideways: if the response is anger ("this is unacceptable"), do not absorb it as a verdict on you; return to the decision: "I hear that, and Friday still isn't real. Which option hurts less?" Anger at bad news is weather; the date is climate.

Scene 2: the credit that walked away

In the sprint review, a director praised "Sam's caching design". The design was Alex's; Sam presented it. Alex, in a DM the same afternoon:

Alex:  Small thing I'd rather handle directly: in the review, the
       caching design came up as yours. I designed it, you presented
       it, and the room came away with the wrong picture. I don't
       think you did it deliberately, but I'd like it corrected.
       Would you rather fix it in the channel, or should I?

Sam:   Ugh, you're right, that's on me; I said "my design" out of
       habit. I'll post the correction now and cc Dana.

Alex:  Thanks. For the next one: happy to co-present, which also
       solves it structurally.

Annotations: private first, facts stated without a character verdict ("came away with the wrong picture", not "you stole my work"), intent explicitly given its most charitable reading while the correction is still required, and the ask is specific with an either/or that makes correcting easy. The closer converts the incident into a structure ("co-present next time") instead of a grudge.

If it goes sideways: if Sam deflects ("does it really matter?"), the escalation is calm and named in advance, per Chapter 10: "It matters to me, and promotion packets are built from exactly these impressions. If you'd rather not correct it, I'll mention my role to Dana myself; I wanted you to hear that from me first." Documented contribution (Chapter 18's brag doc) makes this conversation factual rather than testimonial.

Scene 3: put on the spot by an executive

A quarterly review. A VP turns to Alex mid-meeting: "Can we have multi-region by March?"

Alex:  I don't want to hand you a bad number in a good meeting. The
       honest answer today is: the storage layer is the long pole,
       and I haven't sized it. I can have a real answer with a
       confidence range by Thursday noon. Directionally: March is
       possible only if we descope failover to read traffic first.

VP:    I'll take Thursday. Send it to me directly.

Annotations: the refusal to improvise a date is framed as protecting the VP ("a bad number in a good meeting"), not as unpreparedness; a concrete delivery time replaces the number; and the "directionally" sentence gives the room something real to plan around without becoming a commitment. This is Chapter 8's executive register plus Chapter 7's estimate-versus-commitment line, under stage lights. The one fatal move here is the reflexive "yeah, March should be fine", which becomes a plan of record before the elevator reaches the lobby.

Scene 4: the harsh review

Alex opens a PR and finds: "This whole approach is wrong. Did you read the architecture doc at all?"

Alex (after a deliberate hour, in the PR):
       There's a real objection in here and I want to engage with it
       properly. Which constraint from the doc does this violate?
       If it's the single-writer rule, section 3 of my description
       explains why this path is exempt; if I've misread that, I
       genuinely want to know.

Reviewer:
       ...it's the single-writer rule, and I hadn't read your
       section 3. The exemption argument mostly holds. My comment
       was harsher than the situation deserved; sorry. One real
       issue remains in the lock ordering.

Alex:  No harm done, and the lock ordering point is right; fixing.

Annotations: the deliberate hour is the whole trick; the first draft of any reply to that comment should never be sent. Alex's actual reply extracts the technical claim from the hostility and answers only that, with genuine openness to being wrong. Refusing to match tone is not submission; it is the move that makes the other person's tone visible to everyone reading, including themselves. Most such exchanges end exactly like this one: partial concession, small apology, one real issue that survives.

If it goes sideways: a reviewer who stays hostile after a clean reply is no longer a wording problem. Move channels (Chapter 6): "We're not converging in text; fifteen minutes on a call?" If the pattern is chronic, that conversation belongs in your 1:1, described with SBI (Chapter 18), not suffered in silence.

Scene 5: the no

Ines asks Alex to "quickly add" an export format her team needs this sprint.

Ines:  It's probably a day of work? It would really unblock us.

Alex:  I believe you that it's important, so let me be straight
       about the cost side. My sprint is committed to the retry cap,
       which is a postmortem action item with a date. A day of your
       feature is a day off that, and I don't get to make that trade
       alone. Two real paths: Dana can reprioritize me if this
       outranks the action item, or I can pair with someone on your
       team for an hour tomorrow so you can build it yourselves;
       the export interface is friendlier than it looks.

Ines:  The pairing option honestly sounds faster than waiting.
       Tomorrow at 10?

Alex:  Booked. And if it turns out gnarlier than an hour, I'll say
       so rather than disappear on you.

Annotations: the no never actually says no; it prices the yes and routes the priority call to its owner (Chapter 10's costed yes), while the pairing offer converts refusal into capability transfer, which is the version of no that builds relationships instead of spending them. The closing promise ("I'll say so rather than disappear") names and forecloses the failure mode that makes people fear asking engineers for anything.

Don't be confused: across all five scenes, keep apology, explanation, and excuse distinct. An apology owns impact ("I'm sorry I was short with you"). An explanation gives mechanism ("I'd been up since 4 with the pager"). An excuse deploys the mechanism to cancel the ownership ("well, I'd been up since 4, so"). The first two combine fine in that order; apology, then mechanism, then repair. The moment the mechanism arrives before the ownership, or instead of it, the listener hears an excuse, and the apology stops working.

The pattern under all five

Strip the scenes to their skeletons and one shape repeats: facts before feelings, options before verdicts, the other person's out prepared in advance. Alex never once argues about being a good engineer, a wronged colleague, or a trustworthy estimator; every conversation is steered onto ground where evidence can settle it. That is the deepest habit this book has to teach, and it is Chapter 16's final checklist item (read it as the recipient) running at the hardest difficulty setting.

👉 That is the end of the situation room and of the playbook. What remains is the References: the books, guides, and standards behind these chapters, each worth your time in full.