Q2 hit plan. Three engineers paid for it.

Q2 hit plan. The deck went to the board in early July with a clean green column on revenue and a confident slide on engineering velocity. The CEO called it execution. The CTO, in a one-on-one that same week, called it a debt. The CEO didn't see the debt yet. The bill came due in Q3.

Three senior engineers had carried Q2 on weekends through May and June. Sprint planning had looked fine on paper. The sprints hadn't. Each two-week sprint missed its planned scope by roughly a third, and the three closed the gap in the evenings and on Saturdays. By mid-June they were running 60-hour weeks. By late June, two of them had stopped answering non-urgent Slack. By early July the quarter shipped, the launch went out, and the board update said strong quarter on execution.

The bill arrived on three timelines. The first landed within a month: engineering velocity dropped through July as the three took the recovery week they'd earned and never asked for. Q3 scope had been built on the assumption that Q2's output was the team's real capacity. It slipped in the first sprint. By mid-July the Q3 commitment to the board was already off pace.

The second bill landed within ten weeks: one resignation. The engineer who'd carried the most overtime gave notice in mid-September. He cited exhaustion to the CTO in private and seeking new challenges in the exit interview. Nobody logged the departure as a consequence of the hero quarter. In operational fact, that's what it was.

The third bill landed within five months: a second resignation, plus a third engineer dropping to four-day weeks on an arrangement the company approved quietly, because losing a third senior engineer in one fiscal year wasn't survivable. By Q4, team capacity sat below where Q1 had started. The team that carried Q2 wasn't the same team anymore, and what remained couldn't carry another quarter shaped like it.

This is the arithmetic of hero quarters, and most boards never run it. A quarter that hits plan on overtime borrows from the next quarter's velocity. The loan gets repaid in slipped scope, with interest paid in resignations. The interest rate varies. Sometimes the team recovers with no departures. Sometimes one exit papers over the whole thing. But the loan is real, and the repayment lands on a schedule the company can't accelerate.

Boards reach for strong quarter on execution because the accurate sentence is uncomfortable. The accurate sentence is: the team carried this quarter on unsustainable hours, so expect a velocity drop next quarter. Most CEOs won't say it, because it reads as a forward miss. The board would rather grade the present and deal with the future when it shows up.

The correction isn't better project management. Better project management doesn't manufacture capacity the team doesn't have. The correction is honest scoping at quarterly planning. A quarter that needs overtime to hit plan was scoped against the wrong capacity number. The right scope is what the team ships in normal hours, with a buffer for unplanned work and senior attention reserved for the work only seniors can do.

Hero quarters are planned, not staffed. The team didn't run short of people. It committed to more work than its people could ship. The over-commitment came from a pipeline projection that demanded engineering throughput the team couldn't produce, which created the implicit demand for overtime, which produced the quarter.

The deeper habit is to surface hero quarters out loud during reviews. For every function, leadership asks: did this quarter need overtime, who absorbed it, and what's the recovery plan? Those questions catch the pattern while it's forming. Skip them, and hero quarters accumulate silently until the resignations make them visible — by which point the operational damage is months ahead of anyone's awareness.

Before your next board update, ask:

• Did this quarter hit plan through normal operations or through unsustainable effort?
• Which specific people carried the effort, and what are they owed?
• What's next quarter's plan, calibrated against recovered capacity, not peak capacity?
• If a resignation lands in the next ninety days, will it be a surprise or a confirmation?

The board update that names the hero quarter for what it was is the one that earns trust on a long horizon. The update that calls it strong execution is the one that produces next quarter's slipped plan, which the same board then grades harshly. Name it. The bill is already in the mail.