What does it mean that capacity recovery after overload?

After a period of overcommitment you need extra recovery time to restore baseline capacity.

Example: A product manager finishes a three-week launch crunch — twelve-hour days, weekends consumed, sleep cut to five hours. The launch ships on Friday. On Monday she opens her laptop expecting to resume normal operations: roadmap planning, stakeholder meetings, backlog grooming. Instead, she stares at a blank document for forty minutes and produces nothing. She misreads a straightforward email and sends a reply that creates a two-day conflict. She sits in a strategy meeting and cannot hold the thread of the conversation. This continues for two weeks. She tells herself she is "just tired" and pushes harder, which extends the fog. The problem is not laziness or motivation. She depleted her capacity reserves during the crunch, and capacity restoration operates on a timeline measured in weeks, not weekends. She needed a deliberate recovery protocol — reduced load, extended sleep, low-demand tasks — and she needed it before she opened that laptop on Monday.

Try this: Recall your most recent period of overcommitment — a crunch, a deadline sprint, a season of sustained overload. Write down three things: (1) how long the overload period lasted, (2) how long it took you to feel genuinely restored to your normal output level afterward, and (3) what you actually did during the recovery period (did you rest deliberately, or did you try to push through?). Now calculate the ratio: recovery duration divided by overload duration. Most people find ratios between 1.5x and 3x — meaning recovery took significantly longer than the overload itself. If you tried to push through without deliberate recovery, the ratio is likely even higher. Write this ratio down. It is your personal recovery asymmetry coefficient, and you will use it to plan future recovery periods.