My team was not small in what it carried. We maintained the system that powered wait times, people counts, and operating schedules across the parks — the platform of record for operations data. When a guest checks how long a line is, a system answers. Ours. It was one of the most important applications in the company.
For a long stretch, the entire permanent engineering staff of that system was me. I was the lead, and I was the only cast member developer on the team — the only Disney employee among a sea of temporary workers on short-term contracts. I was the defense.
But I could not pick my players, my coach, or the strategy.
The claim in this essay comes in two halves, and I want to be precise about which is which. I do not know that return to office was implemented to push people out. Nobody handed me a memo. What I know is that every stated justification failed on the record — the productivity theory could be read as false straight off the floor plan (Part 2), and the evidence for the mandate never existed anywhere the mandated AI could find it (Part 5). When every stated reason for a policy collapses, you are left guessing at the real one, and my best remaining guess is attrition: make the job unbearable enough and people remove themselves from payroll, no severance required. That half is inference, and I will keep calling it inference. The other half is not. Whatever the intent, the effect was an avalanche of brain drain, and leadership’s own choices accelerated it at every turn. That half I watched.
The Sea of Sixteen Months
The players I could not pick were the contractors. The company staffed the platform of record with temporary workers on contracts capped at roughly sixteen months, and it is worth spelling out what that cap means on a system with twenty years of legacy code, tech debt, and thin documentation. A new developer needs months before they stop being dangerous, more months before they are genuinely useful. By the time a contractor reached useful, the offboarding was already in motion. Their last day was on the calendar before their first day.
So my job ran on a loop: onboard, train, answer every question, watch them finally get good, wave goodbye. Repeat with the next one. It was a waste of my time, the team’s effort, and the company’s money — and I say money deliberately, because the arrangement was defended in exactly those terms. When the staffing model was questioned, the answer from leadership was: “There’s no way we do this without the people.”
The people. Any people. Part 3 covers the fallacy underneath — the belief that a developer is a developer, swappable at will. The sixteen-month cap was that fallacy converted into a staffing model. The knowledge walked out on schedule. Every schedule.
The Lead They Fired and the Lead They Bought
The coach I could not pick was the lead they hired. But first, the one they already had.
The team had a lead in Washington state, and she was excellent — she knew the system, and the team trusted her. She was laid off. Not for performance. For geography: she would not relocate to Orlando, so she was gone. Read that against the rest of this series. The office mandate that no evidence supported, enforced into the office that was not ready, cost the platform of record a proven lead. If the guess I am making in this essay needs a single data point, it is this one. When the mandate and the talent conflicted, the mandate won — on the record, with a layoff.
They created the leadership vacuum themselves. Then they filled it. Three of us interviewed the replacement candidate, and all three of us came back iffy — not a no, but nowhere near a yes. It did not matter. Leadership had extended the offer before anyone else was even interviewed. The search was over before it started.
It did not work out, and everyone could see it was not working out, and nothing was done. We watched him drive out team members who carried legacy knowledge of a twenty-year system, the kind of knowledge that does not survive a handoff document. Leadership watched too. When he was finally out, they turned back to me — the demotion in Part 3 had not moved the responsibility anywhere, only the title. I stepped back into the gap because the system mattered. But the damage was done. The people who left did not come back.
The Coward’s Layoff
The strategy I could not pick was the one nobody would say out loud.
If the goal was fewer people, there was an honest tool for exactly that. It is called a layoff. It comes with severance, notice, a clean story, and a leader’s signature on the decision. It costs the company money and it costs the leader something too — a hard conversation, a number on a report with their name attached. That cost is what makes it honest. The person deciding pays part of the price.
Engineering misery until people quit on their own is the same headcount reduction with the courage removed. No severance. No signature. No story to own. The company books it as voluntary attrition and every hand upstairs stays clean. And it is worse business, not just worse ethics, because misery does not select at random. The people who leave first are the ones with options, and the ones with options are your best. The research on return-to-office mandates found exactly this: turnover spikes afterward, concentrated among the most senior and most skilled, and the vacancies they leave take far longer to fill. A layoff aims. Attrition by misery fires backward into your own talent.
That was the hard load to bear. Not the commute, not the noise, not the office. Knowing that our leaders were sacrificing us to make themselves more comfortable. It should be the other way around. Absorbing discomfort so your people do not have to is not a perk of leadership. It is the job description.
Just do the layoffs. Have the courage.
A Slowly Contracting Org
I watched the avalanche from the inside. The best people went first, exactly as the incentives predicted, and the legacy knowledge went with them — the unwritten map of a twenty-year system, carried out one resignation at a time. The team that remained was me, for a long while, plus whoever was passing through on a sixteen-month clock. Then I left too. What remains is a slowly contracting org, defending one of the most important applications in the company with less every year.
The last time I onboarded a new contractor, I opened the team calendar to schedule the first walkthrough — wait times, people counts, schedules, the platform of record. The end date was already on it. Sixteen months out, marked before the first walkthrough, before the first commit, before I had learned to spell their name.
Further Reading
- Yuye Ding, Zhao Jin, Mark (Shuai) Ma, Betty (Bin) Xing, and Yucheng (John) Yang, Return to Office Mandates and Brain Drain (SSRN working paper, 2024) — tracking three million tech and finance workers: abnormally high turnover after RTO mandates, concentrated among senior and skilled employees, with vacancies taking roughly 23% longer to fill afterward
- David Van Dijcke, Florian Gunsilius, and Austin L. Wright, Return to Office and the Tenure Distribution (SSRN working paper, 2024) — RTO mandates at large tech firms followed by departures of longer-tenured employees, shifting the workforce junior
