You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 12: Recovery Protocols — When You're Behind, Stuck, or Burned #

I want to predict a specific pattern about your help-seeking behavior before you read this module, because the prediction is the diagnostic and the diagnostic is most of the cure. You wait three to five times longer than you should before asking for help. Not because you do not know help is available, but because some pre-conscious part of you has decided that asking is a referendum on your competence, and the referendum-feeling is more aversive than the cost of staying stuck. The pattern is documented across engineering populations, and it runs especially strong in engineers trained in cultures — family, school system, or national pipeline — that rewarded the appearance of independent capability and treated asking as a small admission of inadequacy. The cost is brutal: a two-day stuck-state that a twenty-minute message to the right person would have resolved, multiplied by hundreds of episodes across a career. The protocol that interrupts it is small and mechanical: when you have been stuck for thirty minutes without progress, write down what you would tell another engineer who was stuck on this. Roughly 40% of the time the writing surfaces the answer; the other 60% it produces a clean question someone can answer in minutes. Either way you are out in under an hour instead of two days.

The differential diagnosis is the part I want to press hardest, because the failure mode of recovery protocols is applying the right cure to the wrong problem. Behind-on-deadline is one shape, and the cure is proactive renegotiation, never silent slippage. Stuck-on-a-problem is a second shape, and the cure is smaller experiments plus help-seeking. Burning-out is a third, and the cure is structural load reduction, not better tools. The shapes overlap at the symptom level: a burnout-driven stuck-state looks like a problem-stuck-state from outside, but the cures are opposite — pushing through harder helps a hard problem and accelerates a burnout. Misdiagnose in one direction and you make the burnout worse; misdiagnose in the other and you take a vacation from a problem that needed an experiment. The differential takes ten honest minutes at the moment of recognition. Run it before you pick a protocol. And inside the burnout branch sits the differential most likely to surface signals you will want to dismiss: burnout is context-specific — depleted and cynical about the work, while you still light up around the people and things that have always mattered — whereas depression is global, the lighting-up not happening anywhere, plus persistent guilt disproportionate to circumstances. The Maslach Burnout Inventory measures the burnout dimensions; depression requires different instruments and a professional. If the MBI scores high and the global signals are present, both can be true, and the response is professional support, not a better protocol document. The engineer's instinct to absorb every difficulty into the technique frame and optimize it has a failure mode here that costs people years. I am naming it so you cannot un-see it.

The "I'm going to miss the deadline" script is the single most reputation-protective artifact in the module, and it should exist in writing before you need it, because at the moment you need it your body chemistry will be pushing hard toward avoidance. The script: the day you realize the deadline is at risk — that day, not closer to the date — you send the message. I committed to X by Y. Based on the work so far I now estimate Z, for these specific reasons. Three options: (a) extend to Z at full scope; (b) deliver on the original date with these specific items cut; (c) split delivery, first part on the original date and the remainder by Z. Which do you prefer? The script reframes the slip from a personal failure into a project decision and hands the other party agency. Clients and managers almost always respond well to this and almost never respond well to silent slippage, which is the pattern your avoidance chemistry will choose by default. Patrick McKenzie has written sharply on this; read his version. Then write yours, file it as a protocol document next to the stuck protocol and the load-reduction protocol, and keep all three where you can reach them on a bad day — the entire point of a protocol is that it runs when you are least capable of improvising.

One thing this module refuses, because the negative space is part of its honesty: do not absorb burnout signals into a story about insufficient discipline. Burnout is not a discipline failure. It is a load-and-recovery imbalance, and the cure is reducing load or increasing recovery, not trying harder at the same load. Whatever long arc your work is in service of — a career, a body of work, a family, a mission — it is a decades-scale project, and burnout-now is paid for out of capacity-then. The pace that holds for forty years is not the pace that maxes out the next forty days. M10 made that argument from arithmetic; this module makes it from the failure side. Take the MBI now as a baseline and re-take it monthly through any high-load window; the trajectory, not the snapshot, is the diagnostic.

Conclusion #

Module 12 is the recovery layer. Three failure modes — behind, stuck, burned — take three different protocols, and the ten-minute differential decides which one runs. You wait three-to-five times too long to ask for help; the write-it-down-for-another-engineer move interrupts the pattern at minute thirty. The missed-deadline script converts slips from reputation damage into project decisions, but only if it is written before the body chemistry arrives. Take the depression-versus-burnout differential seriously rather than absorbing it into the technique frame. The protocols must exist before the failure modes hit; on the day you need them, you will not be capable of writing them.

Predictions #

  • You will write the three protocol documents and run at least one on a real situation within two months. The first run will feel awkward; the second will feel like infrastructure.
  • The write-down-what-you-would-tell-another-engineer move will surface the answer on its own roughly 40% of the time. The ratio will surprise you.
  • The MBI will surface a non-zero signal on at least one dimension, and you will be tempted to retake it "on a better day." The first honest score is the baseline; keep it.
  • The missed-deadline script will save at least one professional relationship in the next twelve months, and you will only see the save in retrospect, by comparison with how the silent version used to go.
  • If the depression differential applies, you will be tempted to dismiss its signals as "just burnout" because burnout is the more flattering diagnosis for an engineer. Two global signals quietly true is the threshold for professional consultation. Honor it.
  • Your next high-load window will produce at least one genuine failure-mode episode, and whether it costs hours or weeks will be determined almost entirely by whether the protocols existed beforehand.
  • You will resist the load-reduction implication longest, because the engineer's instinct is to optimize harder at constant load. When the diagnosis is imbalance, the honest response is subtraction. M10 gave you the scripts for it.