Equal Disappointment Algorithm
Spread unavoidable disappointment evenly so no single life domain catastrophically fails.
The Equal Disappointment Algorithm reframes an impossible situation—demand exceeding supply across all life domains—into a deliberate resource-allocation decision. The core insight is that when total demand exceeds available hours, disappointment is not a risk to avoid but a resource to distribute. The algorithm replaces reactive guilt-driven scrambling with an explicit inventory of all demand sources, a clear-eyed reckoning with the hours gap, and a conscious decision to distribute micro-disappointments equally rather than letting one domain be devastated. The goal is not satisfaction but proportional and predictable underperformance, which is far less damaging than random failure.
- In peak demand phases, disappointment is not optional—only its distribution is
- Concentrated disappointment causes catastrophic failures; distributed disappointment enables sustainable function
- All life domains deserve explicit representation in your allocation model
- Intentional underperformance is superior to reactive failure
- Naming the constraint removes shame and enables clear agreements
- Equal distribution is a success condition, not a consolation prize
- Inventory every demand domainList every area that makes regular time demands on you: career, partner, children, aging parents, personal health, friendships, finances, skill development. Make the list complete—invisible domains still consume time.Pro tipInclude yourself as a domain. Recovery, sleep, and personal maintenance are not optional—treating them as residual causes the algorithm to fail at the foundation.
- Quantify the gap explicitlyEstimate hours demanded per week by each domain and sum them. Compare to your actual available hours and write the gap down. Most people discover demand exceeds supply by 30–60%.WarningIf you skip this step and stay in a vague sense of too much, you cannot make decisions—you just feel guilty without a mechanism to change anything.
- Reframe from 'satisfy all' to 'distribute disappointment'Explicitly accept that full delivery across all domains is mathematically impossible. Your goal shifts from satisfaction to proportional, predictable underperformance. This reframe is the psychological core of the algorithm.Pro tipSay it out loud or write it: 'I will equally disappoint everyone. That is my success condition right now.' The explicitness matters.
- Set minimum time floors per domainAssign each domain a non-negotiable minimum weekly time investment that is meaningful enough to maintain baseline function—not a token allocation. Floors are commitments, not targets.Pro tipEverything above the floor is bonus. This prevents a domain from dropping to zero under pressure, which is what causes catastrophic failures.
- Communicate constraints to stakeholders explicitlyTell key stakeholders in each domain—your manager, partner, close friends—what you have and how you have allocated it. Without setting expectations, others fill the vacuum with assumptions you cannot meet.Pro tipFrame it as information, not apology: 'Here is what I have. Here is what you can expect from me. Here is what I cannot do right now.'
- Review and rebalance weeklyAt week's end, note which domains over- or under-received versus their floors. Adjust the following week's allocations intentionally. The algorithm improves through iteration, not initial precision.WarningWithout a weekly review, the algorithm drifts back to reactive guilt-driven scrambling within two to three weeks and the floors become meaningless.
A senior product manager with two young children and a demanding team needed to add daily AI upskilling to an already full life. Using the Equal Disappointment Algorithm, she mapped her demand gap, set a 45-minute daily learning floor, and explicitly told her partner and manager what each could expect. The clarity ended nightly guilt and allowed her to protect her learning window consistently.
An engineering manager simultaneously navigating a parent's health crisis and a career shift to product leadership used the algorithm to set explicit floors: one weekly family call, two hours career learning, one hour health minimum. He communicated these allocations to his team and partner, framing it openly as distributing his capacity intentionally rather than randomly.
Articulated by Nikhyl Singhal on Lenny's Podcast as a framing for product managers and tech professionals trying to pursue skill reinvention during the most demanding years of their careers and personal lives.