Endurance & the Body: Run 30 Years, Not a 100-Meter Sprint
Topic: Sustainability & Endurance·4 Principles
"Almost everything will work again if you unplug it for a few minutes, including you." — Anne Lamott
This week's thesis: the hidden bottleneck of a super-individual isn't ability — it's endurance. You can sprint, but what the organization actually needs is for you to still be here, and still growing, thirty years from now. Sprinters usually lose to their own bodies and to a collapse of meaning. This week's four cards skip the "self-care" platitudes and get to executable, physical design: reading the clinical signals of burnout (not "a bit tired"), swapping time management for energy management, designing rest as part of the training, and jumping to the second curve before someone younger pushes you off the first.
PRINCIPLE 01
Burnout Is Not "Tiredness": Read the Three Dimensions
Burnout Is Not Tiredness — Read the Three Dimensions
Maslach's 3 DimensionsEarly Signals6 Mismatches
Principle + Master's Words
Burnout has a clinical structure; it is not a mood. It only counts as burnout when three dimensions appear together: emotional exhaustion, cynicism (depersonalization), and a collapse of efficacy. Just being tired is exhaustion; treating burnout as fatigue makes you miss the real lesion.
"Burnout is not a problem of the people themselves but of the social environment in which they work."— Christina Maslach & Michael Leiter,《The Truth About Burnout》(1997)
Diagnosis: 3 Dimensions & 6 Mismatches
Scene
Context: an engineer who's usually the most upbeat has started saying defeated things.
✗ Deny + attribute to the individual
Report: "It makes no difference whether I do this project — nobody looks at it anyway." You: "Don't be so negative, just take a break; you need to build resilience." — You've read a cynicism signal as a mood, and an environmental problem as his weakness.
✓ Own the signal + separate context vs. person
"I heard you say 'it's pointless' — that's not like you. Let's not rush to fix it. I want to understand: is this about this project (no users, direction changed), or about how you feel about the whole thing? What I can do differs completely."
(Differential diagnosis: a local mismatch means adjust the project; broad cynicism means moving workload, reward, or values.)
Self-check (score each 1-10; ≥7 for two weeks → intervene)
Exhaustion: Sunday-night dread — physically tired at the thought of Monday? Still tired after sleeping enough?
Cynicism: Are you using "anyway," "them," "whatever" more and more?
Efficacy: Output hasn't dropped, yet everything feels meaningless and worthless?
Body: Worse sleep, irritability, constant minor illness (the body alarms before the emotions)?
Withdrawal: Starting to cancel social plans, keep the camera off, avoid whatever you can?
Pitfalls + Female Perspective
Treating burnout as a resilience problem. Maslach's core finding: it's an environmental disease, not a willpower one. "Push through" just lets the lesion keep burning.
Treating symptoms only. A vacation patches the exhaustion, but the six mismatches are unchanged — it recurs in two months.
Waiting until collapse. Burnout is chronic; the early signal (cynicism) shows up months before the crash, and that's when it's still reversible.
Female Leader's Note
Research consistently shows women and minorities carry more "emotional labor" and office housework (soothing, coordinating, note-taking, organizing birthdays) — uncounted as output yet genuinely draining, raising burnout risk. Worse, their exhaustion is more readily attributed to "not resilient enough" rather than "unfair load distribution." As a manager, don't just ask "are you okay" — audit whether invisible labor is being systematically piled on the same few people.
This Week's Exercise + Question
Action: Run a three-dimension self-check on yourself this week, and pick one team member you're vaguely worried about — watch specifically for their "cynicism signals" (word choice, how perfunctory their code reviews are).
Reflect: Is your burnout the exhaustion type (doing too much) or the values-mismatch type (you no longer believe in what you do)? The fixes are opposite — the first needs load reduction, the second needs a change of mission.
PRINCIPLE 02
Manage Energy, Not Time
Manage Energy, Not Time
Four EnergiesOscillate, Not LinearRecovery Rituals
Principle + Master's Words
Time is fixed and only depletes linearly; energy is renewable and oscillates. The best don't squeeze out more hours — they refill four kinds of energy across the "spend → recover" wave: physical, emotional, mental (focus), and spiritual (meaning). You're an oscillating creature, not a battery discharging at a constant rate.
"Energy, not time, is the fundamental currency of high performance."— Jim Loehr & Tony Schwartz,《The Power of Full Engagement》(2003)
Linear Depletion vs. Oscillating Recovery
Scene
Context: you've worked 12-hour days for three straight weeks racing a release.
✗ Wearing "I can take it" as a badge
Running on caffeine and willpower, working weekends, telling yourself "it'll be fine after the release" — but the next release is always waiting. Three weeks in, your body is present, your mind isn't, and decision quality falls off a cliff.
✓ Schedule recovery like it's part of training
Admit you're an oscillating creature. Cut the day into 90-minute deep blocks, each followed by a forced break: stand up, get off-screen, take a walk, no phone. Schedule recovery as seriously as the sprint, not "when I get a chance." You can go into debt during a sprint, but mark clearly when you'll repay it — debt you can't repay is chronic.
Refueling Checklist for the Four Energies
Physical: Sleep 7 hours, exercise regularly, don't run on junk food and caffeine.
Emotional: Schedule one small thing that "refills" you each day (even 15 minutes).
Mental: At least one 90-minute single-task block daily; notifications and Slack off.
Spiritual: Ask weekly "which thing this week did I actually care about?" — none is an alarm.
Recovery ritual: Do you have a clear "off signal"? (Close the laptop, change clothes, a commute.)
Pitfalls
Treating recovery as a reward. "Rest after I finish" — but the work never finishes, so you never rest. Recovery goes first, not last.
Wearing "busy" as an identity badge. Using overtime hours as the measure of self-worth is the most expensive self-deception.
Refilling only the physical. Slept enough and still empty — because what's drained is emotion and meaning, and those refill in completely different ways.
This Week's Exercise + Question
Action: Schedule 3 blocks of 90 minutes on your calendar this week, each followed by a forced 15-minute off-screen recovery (walk, water, look out the window — no phone).
Reflect: Which of the four energies is your real bottleneck right now? (Often it's not physical but meaning or emotion — yet we instinctively refill the one that's easiest.)
PRINCIPLE 03
Design Rest as Training: Deload & Real Disconnection
Design Your Rest — Deload & Real Disconnection
Deliberate RestDeload WeekSabbatical
Principle + Master's Words
Rest is not the absence of work — it's its counterpart. Elite athletes have deload weeks; knowledge workers wear "never resting" as a virtue. Real recovery must be designed: fully disconnect, periodize, and take at least one long detachment a year. Half-disconnecting equals not disconnecting.
"Rest is not work's adversary. Rest is work's partner. They complement and complete each other."— Alex Soojung-Kim Pang,《Rest: Why You Get More Done When You Work Less》(2016)
Scene
Context: you've finally approved two weeks off for yourself.
✗ "Just in case" half-rest
You bring the laptop, check email and Slack morning and night "just in case," and stay reachable. Two weeks later you're more tired than before — because your brain never truly went offline, it just idled on low power the whole time.
✓ Set a disconnection protocol first
Before leaving: name a backup and publicly authorize them, set an auto-reply, delete work apps from your phone. Tell the team clearly: "Call me only for a P0 incident; everything else waits until I'm back — go to X for decisions." Give the team a drill without you, and give yourself a real offline.
Periodization Checklist for Recovery
Daily: A clear "no-screen" window (meals, a walk, the hour before sleep).
Weekly: A half-day fully off work (the brain needs continuous offline to reach deep recovery).
Quarterly: A truly disconnected long weekend — no laptop, no "quick glance."
Every vacation: A handover protocol + authorized backup, not "reach me anytime."
Every year or few: Seriously consider one 4+ week detachment (sabbatical, parental leave, a gap).
Pitfalls
"Just in case" half-rest. Worse than not resting — body away, brain on duty, gaining neither.
Postponing the sabbatical to "a less busy time." That day never comes. Schedule recovery actively, like a release.
Resting with guilt. Half-resting while guilty never lets the parasympathetic system kick in — no recovery. Allowing yourself to fully leave is the prerequisite for recovering.
This Week's Exercise + Question
Action: Run a "real disconnection" experiment this week — pick one weekend, fully power off work devices and apps for 48 hours, then observe your Monday-morning state and decision clarity.
Reflect: If you vanished for two weeks, would the organization collapse? If so, is that the glory of being "irreplaceable," or the debt of never having built the system and the delegation? (The former is a risk, not a badge.)
PRINCIPLE 04
Jump to the Second Curve Before You're Pushed
Jump to the Second Curve Before You're Pushed
Fluid vs. CrystallizedFrom Strength to StrengthTurn to Teaching
Principle + Master's Words
Technical ability (fluid intelligence) peaks in your 30s-40s and slowly declines; while judgment, synthesis, and teaching (crystallized intelligence) keep rising into old age. The tragedy is clinging to the first curve until someone younger pushes you off. Wisdom is jumping early to the second curve — "coach / advisor / legacy." Not exiting, but changing tracks.
"Your professional decline is coming (much) sooner than you think."— Arthur C. Brooks,《From Strength to Strength》(2022)
The Two Intelligence Curves
Scene
Context: you're a senior tech lead, noticing your coding speed and memory are worse than three years ago — and far worse than the 25-year-old on your team.
✗ Racing your younger self
Doubling down to prove you can still out-grind the young ones, staying up to drill problems, fighting to take the hardest coding tasks. This is racing your peak self and younger people on the fluid-intelligence track — mathematically, you lose.
✓ Migrate your edge to the crystallized track
Shift your ground from "write code fastest" to "see furthest, connect widest, grow people." Your leverage is no longer personal output but making ten people produce better: set technical direction, run design reviews, mentor, turn the pits you fell into org assets. The same experience appreciates on this track.
Second-Curve Self-check
Did my value growth these five years come from personal output or amplifying others?
Am I systematically turning knowledge into inheritable things (docs, mentees, talks, reviews)?
Is my financial runway enough to let me do what I "want to" rather than "have to"? (See Day 33)
Am I retiring to something, or just wanting to retire from the current grind? (Toward vs. away)
Have I built a second identity beyond the job title? (See Day 22 — retirement shouldn't be identity collapse.)
Pitfalls
Racing your younger self. Grinding on the fluid track is a fight you're destined to lose and that drains you most.
Treating retirement as "escaping from work." Bronnie Ware records the top deathbed regret as "I wish I hadn't worked so hard," but pure escape falls into emptiness — you must retire to something.
Betting your whole identity on the title. Lose the title and the person collapses. Switch the curve while you still hold chips, not passively after a layoff.
This Week's Exercise + Question
Action: Draft your "second curve" this week — if in five years you no longer stand on personal coding output, what do you stand on? List 3 crystallized-intelligence assets you can start compounding.
Reflect: Is each of your days prolonging the peak of the first curve, or paving the second? In an era where AI shortens the half-life of tech, is that switching window earlier than it was for the last generation?
Deeper Questions
Is burnout an environmental problem or a personal one? As a manager, which of the six mismatches can you actually change?
Maslach locates the lesion in the environment (workload, control, reward, community, fairness, values), but as a mid-level manager your authority is limited. The reality is triage: workload, community, and local fairness you can mostly adjust; compensation and company-level values are often beyond your hands. Fix what you can immediately (redistribute invisible labor, give autonomy, recognize publicly), and for what you can't, tell your report the boundary clearly — don't pretend to be omnipotent, and don't pretend to be powerless. Admitting some mismatches you can only help them escalate or exit gracefully isn't failure — it's not deceiving them.
Does "manage energy, not time" still hold in a release season with hard deadlines?
It holds, but convert it into a "debt–repayment" model. The problem isn't the overdraft but whether there's a repayment plan. Healthy sprint: clear start and end, a forced deload after, the team repaying the debt together. Chronic burnout comes from the "permanent sprint" — every release is an emergency, debt never repaid. Your job as a leader is to protect the repayment window from being swallowed by the next emergency, and to rest first yourself, giving the team permission.
Endurance demands the long game, but org promotion mechanisms often reward short-term sprinters. What then?
A real trade-off with no cost-free answer. Short-term, sprinters are more visible and rise faster; long-term, endurers last longer, compound more, and take over after sprinters burn out. The pragmatic move is selective sprinting — go all-in on the few battles with real leverage to buy visibility, and hold a sustainable pace the rest of the time. Treat sprinting as scarce ammunition, not a default state. Meanwhile manage up so that "sustainable delivery" is also counted as value, not only firefighting heroes rewarded.
In a high-pressure big-company context, is a sabbatical a privilege? What about people without FU money?
Honestly: long detachment does have a threshold — it needs a financial buffer and some job security. For those without a buffer, "real disconnection" must scale down — not a four-week sabbatical, but recovery broken into affordable grains: truly disconnected weekends, fully used annual leave, deep recovery blocks within the week. Meanwhile, run your financial runway (see Day 33) as endurance infrastructure — it buys not luxury but the option to "dare to rest" and "dare to leave." Admitting this inequality is more useful than pretending everyone can gracefully take a gap.
Does the second curve arrive earlier and more brutally in the AI era?
Very likely. In traditional industries, crystallized intelligence (industry judgment, networks, synthesis) accumulates slowly and depreciates slowly; in AI/tech, the half-life of a specific stack is measured in years, and the edge of pure fluid intelligence (memorizing APIs, hand-writing implementations) is being erased fast by tools. Two implications: the switching window is earlier — don't wait for 45; and "crystallized intelligence" must be redefined — not remembering old knowledge, but judgment, cross-domain connection, and leading a team to use new tools well. What compounds in the AI era is exactly the judgment and human parts machines can least replace.