Week three: the reorg lands

The first two weeks were a good sprint in a stable org. Monday of week three, the stability ends: an all-hands announces a reorg, the checkout roadmap is cut, and the card-management work the team planned (and Ravi's half-built token overhaul with it) is shelved. This chapter is the language of the bad times: criticizing a management decision without torching yourself, venting that stays survivable, and holding a team's morale up with sentences instead of slogans.

Monday, 10:00: the all-hands, and the public question

The VP of Engineering announces: two product lines merge, checkout absorbs the billing team's backlog, card management moves "below the line" indefinitely. Then: "Questions welcome."

A colleague from another team goes first, and gets it wrong:

Eng:   So management spent six months telling us card management
       was critical, and now it just isn't? Who exactly got this
       wrong, and why should we trust the new roadmap?

VP:    (visibly tightening) Priorities change when the business
       changes. Next question.

The question contained a real concern and was engineered to be unanswerable: "who got this wrong" demands a public sacrifice, so the only possible answer is a wall. Alex asks the same concern, built to be answerable:

Alex:  Two-part question on card management. First, for planning:
       is "below the line" this quarter's call or a direction, so
       we know whether to preserve the half-built work or clean it
       out? Second, for the team: the people who built the vault
       integration made calls based on the old priority. What's
       the best way to feed what we learned into the new plan so
       that work compounds instead of evaporating?

VP:    Genuinely useful questions. This quarter's call; preserve
       the work, don't extend it. And send the learnings through
       Dana; I'd honestly like a one-pager. That vault work is why
       the merger is even feasible.

The mechanics: the concern (was our work wasted? is the plan real?) arrives intact, but framed as requests for information the asker needs to act, not as a demand that someone confess. "For planning" and "for the team" declare legitimate purposes (Chapter 3's purpose tags at all-hands scale). And the second question deliberately hands the VP a chance to say something good about the team, which the VP takes; that sentence ("why the merger is even feasible") is now on the record in front of the whole org. You can advocate and extract value in the same breath, and the hostile version got neither.

Other askable versions of angry questions: "What would have to change for this to be revisited?" (converts a grievance into criteria) / "What's the strongest version of the case for this that we on the ground might not be seeing?" (invites the missing context instead of asserting there is none) / "When the last reorg happened, X suffered; what's different this time?" (history as evidence, not as accusation).

Monday, 10:40: the channel, on fire

The team channel, ninety seconds after the all-hands:

Ravi:  So that's six weeks of my work in the bin. Cool. Love the
       strategy. Really felt valued just then.

Sam:   The same leadership that "deeply values craftsmanship" btw

Alex:  It stings, and Ravi, yours stings most; the token overhaul
       was real work and it deserved to ship. Two things I know:
       the VP said out loud that the vault work made the merger
       feasible, so it's not "in the bin", it's load-bearing. And
       I'd rather we design the salvage than perform the grief;
       I'm as annoyed as anyone, but annoyed in a meeting where
       it can change something. Dana's asking for our take at
       2pm; bring the sharp versions there.

Ravi:  ...fine. But I'm bringing the REALLY sharp version.

Alex:  Bring it. Sharp and aimed beats sharp and sprayed.

What Alex's message does, in order: validates the feeling specifically (naming Ravi's loss as the largest, per Chapter 22: receive first), corrects the factual despair with evidence already on the record, and redirects the energy to the venue where it has power, without ever scolding anyone for venting. Note what he does not do: he does not defend management ("they must have their reasons" reads as betrayal from a peer), does not pile on (his name in a pile-on screenshot is worth nothing), and does not use the word "unprofessional" about his own teammates, ever.

The channel rule under bad news is the screenshot test (Chapter 17) with its stakes raised: reorg-week messages get screenshotted, forwarded, and remembered. Sam's sarcasm is at the survivable edge; one notch darker (naming executives, "clown show", resignation threats) creates a permanent artifact of a temporary feeling.

Monday, 14:00: the team meeting, criticizing upward

Dana opens the team meeting with unusual bluntness:

Dana:  Ground rules for this hour: I will tell you everything I'm
       allowed to, I'll tell you clearly when I've hit the edge
       of that, and I'm carrying our collective view up on
       Thursday. So make it a view worth carrying. What I can't
       do is pretend I get a veto. Ravi, you first; you paid the
       most for this.

Ravi:  Sharp version, as promised. We told customers card
       management was coming. Support has tickets referencing it.
       Killing it isn't just internal whiplash, it's a broken
       external promise, and nobody upstairs seems to have
       checked. That's not strategy, that's carelessness.

Dana:  That's sharp AND carriable. I need the ticket numbers.

Alex:  Building on it: I don't think we can reverse the call, and
       honestly the merger logic holds; billing and checkout
       share more code than either shares with anything else. So
       my ask is narrower than "undo it." One: a public-facing
       line for support, so Marta's team isn't improvising
       apologies. Two: the below-the-line work gets a real
       preservation pass, one week, so restarting in Q3 costs
       days and not the whole six weeks again. Three: someone
       above us owns saying "we changed our minds" to the three
       customers who asked, because that message from support's
       mouth reads as a dodge, and from a director it reads as
       respect.

Dana:  All three are concrete and none of them require winning a
       philosophy debate. That's the memo. Sam, anything?

Sam:   Only the morale line, for the record: this team just
       shipped the best sprint I've seen here, into a
       announcement that made it feel pointless. Thursday's memo
       should say that plainly. Not as a threat. As data.

This is the upward-criticism masterclass the whole chapter builds to. Ravi's anger, aimed, becomes the strongest evidence in the memo (a broken external promise with ticket numbers is a fact pattern, not a feeling). Alex explicitly concedes what is not winnable ("the merger logic holds"), which is what buys his three narrow asks their credibility; criticism that concedes nothing purchases nothing (Chapter 26). And Sam's closer shows how to put morale on the record without hostage-taking: "not as a threat, as data."

Don't be confused: criticizing a decision and undermining a decision are separated by venue and tense, not by sharpness. Before and during the decision window, and in channels aimed at the deciders, almost any well-evidenced criticism is legitimate advocacy; that window is exactly what Dana's Thursday memo is. After the decision, in channels aimed at bystanders (your team, other teams, customers), continued relitigating stops being advocacy and starts being sabotage of the people who still have to execute. The professional pattern is loud in the window, then either disagree-and-commit or escalate formally; the whisper campaign that does neither is the only unprofessional option on the menu.

Tuesday, 12:30: lunch, and the colleague in a hole

Alex and Ravi, cafeteria. Ravi is quiet in the way that is not restful.

Alex:  Real answer, not channel answer: how are you doing with
       it?

Ravi:  Honestly? Six weeks. I skipped my brother's birthday for
       the rotation testing. And the worst part is everyone's
       already moving on, like, "preservation pass, great,
       next topic."

Alex:  Yeah. The speed of the moving-on is its own insult. For
       what it's worth, and I know it's worth a limited amount:
       the rotation testing is the reason the preservation pass
       is one week and not a fantasy. Nobody who reads that code
       thinks it was wasted. But mostly: that sucks, the birthday
       especially, and I'm not going to pitch you silver linings
       over a sandwich.

Ravi:  ...thanks for not doing the silver linings thing.

Alex:  One practical thing, only if you want it: the VP asked for
       a one-pager on the vault learnings. I think you should
       write it, with your name on it, and I'll review. If the
       work's getting archived, your fingerprints go on the
       archive lid.

Ravi:  ...yeah. OK. Send me the ask.

Comforting a colleague whose work was shelved: ask the real question and mean it, let the specific grief (the birthday) be heard without repair attempts, explicitly refuse toxic positivity (naming the refusal builds more trust than any silver lining would), and then, only then, one concrete dignity-restoring action with their name on it. The order matters; the one-pager offered first would have been "moving on" with extra steps.

Thursday, 16:30: the 1:1, morale said plainly

Dana:  The memo went up, all three asks accepted, director's
       calling the three customers personally. Now you: how are
       YOU, in all this?

Alex:  Honest version: my own morale is fine; the sprint win is
       still warm and the merger genuinely makes sense to me.
       What's costing me energy is being the deck everyone vents
       on while staying constructive in public. I'm choosing it,
       I'd choose it again, but I want you to know it's work,
       and if it goes on for weeks I'll need you to visibly take
       some of it.

Dana:  That's fair, and noticed, and I should have said so
       before you had to ask. Thursday's team meeting, I do the
       hard-truths segment, not you. And Alex: what you did in
       the channel Monday is the thing the senior label is
       actually for. It's in my notes with a timestamp.

The last skill of a bad week: reporting your own emotional load like any other capacity fact (Chapter 28's overload flag, aimed at invisible labor), before it curdles into resentment. It is neither complaint nor heroics: "I'm choosing it, and it costs something, and here's the support I'll need." Managers can resource what they can see.

👉 The reorg was fast pain from above. Week three's second act is slow pain from the middle: the security questionnaire, the access ticket that loops three times, the change-approval board, and the art of fighting bureaucracy without becoming either its victim or its imitation. On to Chapter 37.