Week four: politics, reversals, and the good week
The month closes with the oldest weather in any org: two directors in a turf fight, with Alex's queue numbers wanted as ammunition; a shelved decision that un-shelves itself; and then the good times, which have their own etiquette: a launch, a toast, public praise, and career news that asks for grace in both directions.
Monday, 11:00: "can you get me numbers?"
The platform director (Ines' chain) and the product director (Priya's chain) both claim ownership of the queue roadmap in the merged org. Monday, the platform director's chief-of-staff DMs Alex:
CoS: You built the per-tenant queues. We're putting a doc
together for the org design discussion; could you pull
together the numbers showing the queue work was
platform-led? It would really strengthen the case.
Alex: Happy to provide numbers; here's my one condition, stated
up front so nobody's surprised: I'll write up what the
data actually shows (who built what, when, with which
team's review stamps on it), and I'll send the identical
write-up to both directors' staffs, since both sides have
asked me variations of this question this week. The
history has fingerprints from both orgs on it, and I'm
not useful to anyone as a partisan source; I'm useful as
an accurate one.
CoS: ...that's fair, and honestly the other doc will misquote
the history worse without it. Send it to both.
The proxy-war defense in one move: be a source, never a weapon. Alex neither refuses (refusing information to a director's office is its own political act) nor complies with the framing ("showing the work was platform-led" is a conclusion shopping for evidence). He supplies the same facts to both sides, announces that symmetry in advance, and by doing so exits the crossfire entirely; nobody wages a proxy war through a source both sides can see. Note the honesty about why: "I'm not useful as a partisan source" is self-interest and integrity in the same sentence, which is what makes it believable (Chapter 28's daylight test).
Monday, 12:30: "whose side are you on?"
Lunch. Sam, who reports up the platform chain, half-jokes:
Sam: So. Queue wars. You're platform in your soul, right?
Tell me you're not going over to the product side.
Alex: I'm on the side of the queue surviving whoever wins.
Genuinely: I think org-chart-wise it fits platform
better, and I said so in my write-up, with reasons. But
I sent the same write-up to both, and if it lands under
product, I'll make that work too and you'll still be
stuck having lunch with me.
Sam: Diplomatic AND an actual answer. Annoying combination.
The side-taking question, answered without the two classic failures: the dodge ("I don't do politics", which insults the asker and fools no one) and the pledge ("platform forever!", which is a promissory note someone will eventually cash). Alex gives his actual opinion with its reasoning (having one is allowed; hiding it is what reads as slippery), wrapped in the commitment that outranks it: the work, and the relationship.
Wednesday, 15:00: the reversal
All-hands follow-up, VP speaking: a major customer escalated to the CEO; card management is back on the roadmap, expedited, top priority for Q3. Exactly what the team argued three weeks ago. The channel, seconds later:
Ravi: I have typed and deleted "told you so" four times. Someone
acknowledge my restraint.
Alex: Restraint acknowledged and correct. Here's the play: we
won. Winning gracefully means the memo we send today
reads "glad this is back; here's how the preservation
pass pays off," not "as we said all along." Dana's memo
and Ravi's one-pager are why the restart costs days
instead of weeks; THAT's the story, and it makes us look
like the people to bet on, which is worth more than being
the people who were right.
Sam: Drafting the "glad this is back" note now. Ravi, your
one-pager is about to become the most-read doc in the
org; try to look surprised.
Ravi: I will be gracious. I will ALSO be printing the timeline
and framing it. For my home office. Where it's legal.
Don't be confused: "told you so" and closing the loop convey the same fact with opposite effects. When a decision you opposed gets reversed, the record already shows you were right; restating it purchases nothing and taxes the people who now must reverse themselves publicly, which makes the next reversal (maybe one you need) more expensive for everyone. Closing the loop is the professional form: "glad this is back; here's what we preserved and how fast we can move," which banks the same credibility while making the deciders' climb-down cheap. Make it cheap for people to agree with you late; the alternative teaches them to never agree with you at all. (The private victory lap with your team is legal, encouraged, and framed in Ravi's home office.)
Thursday, 16:00: the launch, and the toast
The billing merge ships Thursday, clean; eleven-minute rollback never needed. The director books a private room at a restaurant. Two small scenes from the good times:
The public praise, redirected in real time. The director, glass raised:
Dir: To this team, and especially to Alex, who ran the
cleanest migration this org has seen.
Alex: I'll take a third of that. The rollback rehearsals that
made the board say yes were Yuki's idea. The reason we
had a billing sandbox at all by launch week is that Noor
fought the ticket system to a draw. And the vault work
everyone now agrees was "load-bearing" is Ravi's. I did
the narrating. To the team.
Dir: (laughing) Fine. To the narrator and the load-bearers.
Credit redirection at a celebration: fast, specific, three names with three facts (Chapter 2 at its highest-leverage venue: praise redirected in front of the praiser is credit multiplied, not divided; everyone named will remember that sentence longer than the launch).
The toast, and the glass of sparkling water. Alex does not drink. Nobody needs to know why, and the mechanics are two sentences:
Sam: We're doing rounds; what are you having?
Alex: Sparkling water for me; I'm toasting at full volume
regardless. First round of actual drinks is on my tab
though.
Full participation, zero explanation, zero apology (Chapter 20); the tab gesture (optional) buries the topic in generosity. And the closing skill of every work celebration: leave well. "This was great; I'm calling it a night while I'm still the good kind of memorable. See everyone Monday." First-leaver takes a little chirping and does everyone who wanted to leave a favor.
Friday, 15:00: career news, both kinds
The month ends in the 1:1, with the calibration outcome:
Dana: Two pieces of news and I'm giving you both straight. The
committee agreed the senior case is real AND deferred it
a cycle; the reorg froze half the promotions org-wide.
Not performance, timing. I know that distinction pays
zero of your rent. The second piece: I got you an
out-of-cycle comp adjustment instead, effective next
month, and the case file carries over intact.
Alex: Give me a second with the first part. ... OK. Honest
reaction: disappointed, and I'd rather feel it here than
pretend. Three questions, none rhetorical. Is "deferred"
load-bearing, as in, does the case restart or resume?
What's the failure mode where next cycle finds a new
reason? And what should I do differently in the next six
months, if the answer isn't "nothing"?
Dana: Resume, not restart; it's in writing. The failure mode
is the org freezing again, which I can't rule out, and
if it happens twice I will personally sponsor you
looking at sister teams with headcount, and I'll say
that in front of my own director. Do differently:
nothing on the work. Keep the month-three habits; the
channel moment, the memo, the both-directors write-up.
That's the file.
Alex: Then I'm disappointed and fine, in that order. Thank you
for the comp fight; I know that wasn't free. Put the
resume-not-restart in the notes, and let's talk Q3
scope on Monday; if the case is resting, I want it
resting on a bigger project.
Receiving mixed career news: take the beat out loud ("give me a second") instead of performing instant grace; feel the disappointment in the room where it can be answered, not in a resignation letter where it cannot; then convert it into three askable questions (terms, risks, actionables: Chapter 19's gap analysis under pressure). Dana's side is the model for delivering it: both pieces straight, no euphemism sandwich, the mitigation already fought for, and the escalation promise ("in front of my own director") stated with a trigger condition. The close ("a bigger project") is the tell that Alex heard "resume" as real: people who believe in the resume invest; people who do not, interview. Both are legitimate; only one is decided in this room.
The month, tallied
Four weeks: one great sprint, one reorg, one machine fought to a draw, one proxy war exited, one reversal won gracefully, one launch, one deferred promotion. The good times needed as much technique as the bad ones (the toast redirect, the "told you so" swallowed), and the bad ones were survivable with the same small kit the good weeks ran on: purpose tags, early flags, costed asks, receive-first listening, and the screenshot test. Careers are just months like this, compounding.
👉 The month is over; what remains is range. The next part is the response banks: every band of answer to "how's it going?" (from "great, actually" down to "nah, stayed home, didn't do much"), a full technical debate run through every register from both chairs, and the hard parts: negotiating, criticizing, and standing corrected, each in many mouths. On to Chapter 39.