"We support 40 business teams, we closed 2,000 tickets last year, availability was 99.95%." — all activity. The VP still has no idea what happens if you disappear, so at headcount time you get discounted as a pure cost center.
"Let me give you three layers. Activity: 2,000 tickets — I don't count that as an achievement; the higher it goes, the worse our self-serve docs probably are. Output: median deploy time across those 40 teams went from 22 minutes to 6. Outcome: those 40 teams doubled release frequency this year and cut rollback rate 30% — roughly 9 engineer-years recovered."
"Now the counterfactual: if the platform team froze for a quarter, the first thing to break isn't an outage — it's that curve sliding back, visible in about six weeks."
"And the self-incrimination: this ruler can be gamed — deploy time can be bought by cutting security checks. So I report security-check coverage alongside it. Please read the two numbers together."
Do: write one counterfactual sentence and send it to your boss: "If this team froze for a quarter, the first measurable failure would be ___, visible in about ___ weeks."
Ask: if you can't write that sentence, is the gap in your metrics — or in how the team is scoped?
"I know everyone is exhausted, but we're building the foundation for the company's next two years — chances like this are rare. Two more weeks of pushing." — this does two bad things at once: it trades mission for unpaid labor, and it silently converts anyone who declines into someone insufficiently committed.
"I'm asking for extra time over the next two weeks. I'll say the mission part once: this is the foundation for the next two years. Everything after this is consideration, and all of it is verifiable —"
"(1) I already got X and Y pushed to next quarter with the VP; notes are here. (2) The week after launch, nobody is on call and no meetings are scheduled. (3) Today I'll draft the exact sentences about each person's contribution that go into your perf packet, and send them to you to check the wording."
"(4) If you have something personal in these two weeks, just say 'I can't' — no reason required, and it affects no evaluation." — that last line is the whole point. Without a cost-free exit, the first three are just packaging.
Do: dig out the promises from your last rally, mark each kept / unkept, and make the unkept one your top priority this week.
Ask: if your team were replaced tomorrow by contractors who honor contracts and not missions, which of your current practices would collapse instantly? Those are the management debts mission has been subsidizing.
A 30-person channel, a weekly one-hour sync, and a "who owns what" spreadsheet — then you wait for homework. For a volunteer, the meeting is pure cost and the spreadsheet is pure burden; their perf is written by their own manager, and your spreadsheet has no force.
1. Build a 15-minute on-ramp: "I split the first 12 services to migrate into 12 independent PRs, each with a template and a single command — about 15 minutes of work. Links are here, and you can contribute without attending anything."
2. Outsource the credit to their manager (the only real currency you hold — and promise it at kickoff): "Every month I send each contributor's manager a three-sentence email spelling out what they did and how many teams it affected, cc'ing them."
3. Give them something with their name on it: the Authors line in the doc, the changelog acknowledgment, co-presenter slot at the internal tech talk.
And convert the sync from "60 minutes weekly" to "25 minutes every two weeks, with every decision written into the notes." Nobody falls behind by not attending, so the meeting stops filtering out your volunteers.
Do: pick one cross-org initiative, build a single first task that finishes in 15 minutes, and send the first three-sentence email to each contributor's manager.
Ask: if every volunteer withdrew tomorrow, where would this work stop? That stopping point is exactly what you should be asking funded headcount for.
Reassure each one privately: tell the VP you'll cut cost, tell A they'll get it in Q3, tell B you'll try for Q3 too, tell Security you'll do whatever they say. Three weeks later all four believe you lied to them — and you never told a single lie. You just never let them see each other.
"Capacity this quarter is six engineer-quarters. The four asks total eleven. My proposed ordering, with reasons: security gates (3) — a hard constraint, and not doing them blocks both A and B; A's X (2) — it also lowers B's future integration cost; cost reduction (1); B's Y moves to Q4, with a temporary workaround in the interim (link)."
"If you think the ordering is wrong, reply by Thursday naming the item you are willing to give up. I will not act on replies that only add."
That last line is the mechanism: it forces every "add" request into a "trade" request. Without authority it is the only boundary you can actually hold — and what it protects is capacity, not your ego.
Do: copy this quarter's commitments to every stakeholder into one page, mark the two that contradict each other, and make one of those trade-offs public to both parties this week.
Ask: does long-run legislative leadership erode your decisiveness? When was the last time your team wanted you to just decide, and you went and gathered input instead?