The Law of the Reservoir

Here is a detailed explanation of The Law of the Reservoir, framed specifically from the perspective of an engineer. This law is one of the most practical and forward-looking principles in Steven Bartlett's The Diary of a CEO, emphasizing preparation over reaction.

The Law of the Reservoir: "Build reserves before you need them. Crisis reveals poor preparation."

1. Definition: What Is the Law of the Reservoir?

The Law of the Reservoir (Law 7 in the 33-law framework) states that success, resilience, and the ability to seize opportunities are all functions of the reserves you build during times of abundance.

Core Principle: Most people and organizations operate in a state of scarcity—using every resource as soon as it becomes available, leaving no buffer for unexpected challenges or opportunities. When crisis hits, they have nothing to draw upon. The wise, by contrast, build reservoirs: stores of energy, time, money, knowledge, relationships, and goodwill that they can tap into when needed.

Bartlett draws the metaphor from ancient civilizations that built reservoirs to store water during rainy seasons so they could survive droughts. The same principle applies to every dimension of professional and personal life.

The insight: The time to build a reservoir is not when you are thirsty. It is when water is plentiful.

2. The Psychology of Scarcity vs. Abundance

Bartlett grounds the Law of the Reservoir in the psychology of how scarcity affects decision-making:

Mindset Behavior Outcome

Scarcity Mindset Uses resources immediately. Lives paycheck to paycheck—financially, emotionally, and temporally. No buffer. Every crisis becomes catastrophic. Opportunities are missed because there are no reserves to invest. Stress is constant.

Abundance Mindset Sets aside reserves deliberately. Lives below capacity to create buffer. Crises are manageable. Opportunities can be seized. Decision-making is calm because there is room to maneuver.

Bartlett argues that scarcity is not just a financial condition; it is a cognitive state. When you have no reserves, you operate in survival mode. You make short-term decisions. You cannot think strategically. Building reservoirs is what frees you to think long-term.

3. The Types of Reservoirs

Bartlett identifies multiple reservoirs that must be built. For an engineer, each has specific relevance:

Reservoir Description Why It Matters

Financial Reservoir 

Savings, runway, emergency funds. Allows you to take career risks, survive layoffs, invest in learning, and say no to bad opportunities.

Energy Reservoir 

Physical and mental capacity, sleep, fitness, recovery. Engineering requires deep focus. Burnout destroys productivity. Energy reserves allow sustained performance.

Time Reservoir 

Slack in schedules, buffer in estimates, margin in calendars. When everything is scheduled to the minute, any unexpected task creates crisis. Time reserves allow for emergencies and strategic work.

Knowledge Reservoir 

Deep expertise, broad understanding, learned skills. When a new problem arises, you draw on knowledge built in advance. You cannot learn cryptography the night before you need it.

Relationship Reservoir 

Trust, goodwill, network, mentorship connections. When you need help, advice, or a job, you draw on relationships built before you needed them.

Code/System Reservoir 

Clean architecture, documentation, tests, monitoring, technical debt paid down. When a production issue arises, you draw on the quality built into the system. Fragile systems fail under pressure.

Attention Reservoir 

Focus, deep work capacity, reduced context switching. In a crisis, you need clarity. Attention reserves allow you to think clearly when others panic.

4. The Reservoir in Engineering: Detailed Applications

Let us explore each reservoir through the lens of an engineer's daily work and career.

A. The Financial Reservoir

For an engineer, financial reserves are not just about personal savings—though that matters profoundly. They are about creating career optionality.

Scenario Without Financial Reservoir With Financial Reservoir

You want to leave a toxic job You feel trapped. You cannot afford to quit without another offer lined up. You stay, burn out, and accept poor treatment. You have 6–12 months of runway. You can quit, take time to recover, and find the right role, not just any role.

A startup opportunity arises You cannot take the risk. You need a steady paycheck. You pass on what could have been a life-changing equity opportunity. You can afford to take a calculated risk. You join the startup, accepting lower salary for potential upside.

You want to invest in learning You cannot afford a course, conference, or certification. Your skills stagnate. You invest in high-quality training, books, and conferences. Your skills compound.

Bartlett's advice: Build a financial reservoir that gives you the power to say no. The ability to walk away is the foundation of all other freedoms.

B. The Energy Reservoir

Engineering is cognitively demanding. It requires sustained focus, complex problem-solving, and the ability to hold multiple variables in working memory. Energy reserves are not optional; they are professional infrastructure.

Practice Depletes Reservoir Builds Reservoir

Sleep Sacrificing sleep to meet deadlines. Consistent 7–9 hours. Sleep as non-negotiable.

Recovery Working through weekends. Always being on call. Deliberate rest. Clear boundaries. Sustainable pace.

Fitness Sedentary lifestyle. No movement. Regular exercise. Physical energy supports mental energy.

Nutrition Caffeine and sugar as fuel. Skipping meals. Stable nutrition. Hydration. Avoiding energy crashes.

Focus Constant context switching. Open office chaos. Deep work blocks. Notification management. Protected focus time.

Bartlett's insight: Your code is only as good as the brain that writes it. Treating your energy reservoir as a professional asset is not weakness; it is optimization.

Example:

An engineer I know was known for working 80-hour weeks during crunch times. He was praised for his dedication. But his code quality declined. He made mistakes that caused outages. He burned out and took three months off. When he returned, he set boundaries: no work after 6 PM, no weekend work except true emergencies. His productivity actually increased. His code was cleaner. His decisions were sharper. He realized that his "dedication" had been self-destructive. He now teaches junior engineers that energy reserves are not selfish—they are professional discipline.

C. The Time Reservoir

In engineering, time reserves manifest as slack—buffer in schedules, margin in estimates, space in calendars.

Practice Depletes Time Reservoir Builds Time Reservoir

Estimating Padding-less estimates. Promising delivery dates without buffer. Adding 20–50% buffer for unknowns. Distinguishing between optimistic and realistic estimates.

Scheduling Back-to-back meetings. No gaps between commitments. Deliberate white space in calendar. Time for thinking, not just reacting.

Task Management Always at 100% capacity. No room for unexpected work. Operating at 70–80% capacity. Room for emergencies, learning, and strategic work.

Technical Debt Taking shortcuts to meet deadlines. "We'll fix it later." Allocating time for refactoring, documentation, and debt reduction.

Bartlett's principle: If you are always at 100% capacity, you have no room for the unexpected. And the unexpected always comes.

Example:

A engineering manager noticed that his team consistently missed deadlines. He assumed they were underestimating. But when he looked at their calendars, he saw they were booked solid with meetings, leaving no time for actual coding. Worse, any urgent bug or request would push everything back. He instituted "focus blocks"—four-hour uninterrupted coding windows, three times a week. He also added 30% buffer to all estimates. Suddenly, deadlines were met. Morale improved. The team had time to refactor, to document, to learn. They had built a time reservoir.

D. The Knowledge Reservoir

Engineering knowledge compounds. The skills you build today become the tools you use tomorrow. The knowledge reservoir is built through deliberate learning before it is needed.

Practice Depletes Knowledge Reservoir Builds Knowledge Reservoir

Learning Only learning what is immediately needed for the current task. Regular investment in learning—books, courses, side projects, conferences.

Depth Surface-level understanding. Copy-pasting from Stack Overflow. Deep understanding of fundamentals. Knowing why something works.

Breadth Siloed expertise. Only knows one language, one domain. Broad exposure. Understanding adjacent systems, business context, user needs.

Documentation Knowledge lives only in heads. No written record. Documenting decisions, patterns, lessons. Building a shared knowledge base.

Bartlett's observation: The best engineers are not the ones who know everything. They are the ones who have built a knowledge reservoir so that when a new problem appears, they have adjacent knowledge to draw upon. They can learn quickly because they have a foundation.

Example:

An engineer spent 20% of her time for two years learning about distributed systems—reading papers, building small prototypes, attending meetups. Her current job was in web development; none of this was directly applicable. Then her company decided to migrate to microservices. Suddenly, she was the only engineer on the team who understood eventual consistency, consensus algorithms, and failure modes of distributed systems. She became the technical lead for the migration. Her knowledge reservoir, built when it was not needed, became indispensable when it was.

E. The Relationship Reservoir

Engineering is often seen as a solitary discipline, but in reality, it is deeply collaborative. The relationships you build before you need help become the network you draw upon when you are stuck, when you need a job, or when you need advice.

Practice Depletes Relationship Reservoir Builds Relationship Reservoir

Mentorship Never asking for help. Trying to solve everything alone. Building relationships with senior engineers. Asking thoughtful questions.

Collaboration Working in isolation. Avoiding pair programming. Pairing regularly. Helping others. Being generous with knowledge.

Networking Only reaching out when you need something. Building genuine relationships. Offering help before asking for it.

Reputation Taking credit. Blaming others. Hoarding knowledge. Giving credit generously. Taking responsibility for failures. Sharing knowledge freely.

Bartlett's insight: Your network is not a list of contacts. It is a reservoir of trust. When you need a job, a reference, or help debugging a critical issue at 2 AM, you draw on that reservoir. If you have not deposited into it, you cannot withdraw.

Example:

An engineer was laid off during a company restructuring. His technical skills were solid, but not exceptional. However, over the years, he had built deep relationships. He had mentored juniors. He had helped colleagues debug impossible problems. He had written thoughtful post-mortems that helped the whole team. When he was laid off, seven former colleagues reached out within 48 hours with job leads. One hired him without a formal interview. His technical skills were not unique. But his relationship reservoir was so deep that he never experienced unemployment.

F. The Code/System Reservoir

This is the reservoir most familiar to engineers: the quality and resilience of the systems you build. A well-maintained codebase is a reservoir of reliability. A fragile codebase is a constant source of crisis.

Practice Depletes System Reservoir Builds System Reservoir

Testing No tests. Tests that are flaky or slow. Comprehensive tests. Fast, reliable test suite.

Monitoring No observability. Finding out about failures from users. Metrics, logs, traces. Dashboards. Alerts that signal before users notice.

Documentation No documentation. Outdated, misleading documentation. Clear, maintained documentation. Architecture decision records. Runbooks.

Architecture Spaghetti code. Tight coupling. No separation of concerns. Clean architecture. Loose coupling. Clear boundaries.

Technical Debt Accruing debt to meet deadlines. Never paying it down. Deliberate debt management. Scheduled refactoring. Debt tracked and prioritized.

Bartlett's principle: A system with no reservoir fails under the smallest pressure. A system with a reservoir—tests, monitoring, clean architecture—can absorb shocks, recover quickly, and scale.

Example:

Two teams were building similar features. Team A took shortcuts to ship faster. No tests. Minimal monitoring. Technical debt everywhere. They shipped first. Team B invested in tests, monitoring, and clean architecture. They shipped two weeks later. Six months later, Team A's feature was a constant source of outages. Every change broke something. The team was spending 80% of their time firefighting. Team B's feature ran smoothly. They added new features easily. The team had time for innovation. The "slower" team had actually been building a reservoir. The "faster" team had been creating future crisis.

---

G. The Attention Reservoir

In an age of constant notifications, open offices, and context switching, attention is the scarcest resource. The ability to focus deeply—to hold complex problems in your mind without interruption—is a reservoir that must be protected.

Practice Depletes Attention Reservoir Builds Attention Reservoir

Notifications Email, Slack, phone notifications always on. Scheduled notification checks. Do Not Disturb during focus work.

Context Switching Switching tasks every few minutes. Deep work blocks. Batching similar tasks.

Multitasking Believing multitasking is efficient. Single-tasking. Completing one thing before starting another.

Environment Open office with constant interruptions. Protected focus space. Noise-canceling headphones. Clear focus signals.

Bartlett's insight: Attention is the only non-renewable resource. Money lost can be earned again. Time lost cannot. But attention lost—the ability to think clearly—is the costliest of all.

5. The Compounding Nature of Reservoirs

Bartlett emphasizes that reservoirs do not just protect you; they compound. Each reservoir makes it easier to build the others.

Reservoir Enables

Financial Reservoir Allows you to invest time in learning (knowledge reservoir) and take breaks to protect energy (energy reservoir).

Energy Reservoir Gives you the capacity to build relationships, learn deeply, and maintain code quality.

Time Reservoir Creates space for refactoring (system reservoir), mentoring (relationship reservoir), and learning (knowledge reservoir).

Knowledge Reservoir Makes you faster and more effective, creating more time (time reservoir) and reducing stress (energy reservoir).

Relationship Reservoir Provides support during crises, protecting energy and time.

System Reservoir Reduces firefighting, freeing time and energy.

Attention Reservoir Enables deep work, which accelerates all other reservoirs.

The virtuous cycle: Building one reservoir creates capacity to build others. Neglecting one reservoir creates pressure that drains others.

6. How to Build Your Reservoirs: An Engineer's Action Plan

Reservoir Actionable Steps

Financial Automate savings. Build 6–12 months of runway. Live below your means. Treat financial independence as professional infrastructure.

Energy Prioritize sleep. Set boundaries on work hours. Take breaks. Exercise regularly. Treat recovery as non-negotiable.

Time Add buffer to estimates. Operate at 70–80% capacity. Block focus time. Say no to non-essential work.

Knowledge Schedule regular learning time. Read deeply. Build side projects. Teach others. Document what you learn.

Relationship Help others without expectation. Mentor juniors. Give credit generously. Stay in touch with former colleagues.

System Write tests. Add monitoring. Document decisions. Refactor incrementally. Treat technical debt as a liability to be managed.

Attention Turn off notifications. Batch communication. Create focus blocks. Protect deep work time.

7. Why the Law of the Reservoir Matters in the Book's Structure

The Law of the Reservoir sits in Part 1: The Self, the foundational section on internal mastery. Its placement is critical:

· Part 1 is about building yourself before you build your company, your brand, or your legacy.

· The Law of the Reservoir teaches that you cannot build anything sustainable if you are operating from a place of scarcity. You must first build reserves.

· The reservoir is the foundation that enables all other laws. Without a financial reservoir, you cannot take the risks required by The Law of the Failure. Without an energy reservoir, you cannot sustain The Law of Compounding. Without a relationship reservoir, you cannot leverage The Law of Proximity.

Bartlett's deeper argument: Most people fail not because they lack talent, but because they lack reserves. When pressure comes, they break. The person with reserves does not break. They adapt, they pivot, they seize opportunities that others cannot see because they are too busy surviving.

8. Summary: The Law of the Reservoir (Engineer's Perspective)

Element Summary

Definition Build reserves before you need them. Crisis reveals poor preparation.

Core Principle The time to build a reservoir is when resources are abundant, not when you are thirsty.

Types of Reservoirs Financial, energy, time, knowledge, relationship, system, attention.

Scarcity vs. Abundance Scarcity mindset uses everything immediately. Abundance mindset builds buffer.

Engineering Applications Savings for career optionality, energy for sustained focus, time for strategic work, knowledge for complex problems, relationships for support, clean systems for reliability, attention for deep work.

Compounding Reservoirs reinforce each other. Building one creates capacity to build others.

Book Context Part 1 (The Self)—internal mastery requires building reserves before pursuing external success.

Quick Reference: Engineer's Reservoir Checklist

Reservoir Ask Yourself Action

Financial Do I have 6+ months of runway? Automate savings. Build emergency fund.

Energy Am I sleeping 7–9 hours? Exercising? Set boundaries. Prioritize recovery.

Time Is my calendar 80% full, not 100%? Add buffer. Block focus time. Say no.

Knowledge Am I learning regularly, not just when needed? Schedule learning. Build side projects.

Relationship Have I helped someone recently with no expectation? Mentor. Give credit. Stay connected.

System Does my codebase have tests, monitoring, docs? Pay down technical debt. Add observability.

Attention Do I control notifications, or do they control me? Turn off notifications. Protect deep work.