The commitment to capacity ratio

The number you are afraid to calculate

Most people have no idea what their commitment-to-capacity ratio is. If you asked them to sit down and list every active commitment they hold — every project, every obligation, every promise, every recurring responsibility — and then estimate the weekly hours each one realistically requires, the total would terrify them. That is precisely why they do not do it. The avoidance is not laziness. It is self-protection. As long as the number stays uncalculated, you can maintain the comfortable fiction that everything is manageable if you just work a little harder, sleep a little less, or find the right productivity system. The moment you do the arithmetic, that fiction collapses. And what replaces it is not despair — it is clarity. Uncomfortable, actionable clarity about why things keep falling through the cracks no matter how hard you try.

This lesson introduces the single most diagnostic metric in personal capacity planning: the commitment-to-capacity ratio. It is a fraction. The numerator is the total time your active commitments require. The denominator is your actual measured capacity. The resulting number tells you, with no ambiguity, whether your current situation is sustainable — and if not, by exactly how much.

Defining the ratio

The commitment-to-capacity ratio (C/C ratio) is total commitment load divided by actual capacity. Both sides of the fraction must be measured in the same unit — typically hours per week — and both must be honest.

A ratio of 1.0 means your commitments exactly equal your capacity. Every hour is spoken for. There is no margin for error, surprise, illness, or rest. A ratio above 1.0 means you are overcommitted. Not in the vague, self-deprecating way people say "I have too much on my plate." Overcommitted in the mathematical sense: you have committed to delivering more work than you have hours to produce. Something will not get done. That is not a risk. It is a certainty. No amount of willpower, caffeine, or time management technique changes the arithmetic. If you have committed to 60 hours of work and your measured capacity is 40 hours, 20 hours of commitment will go unmet every single week. The only variable is which 20 hours you sacrifice — and whether you choose deliberately or allow the defaults of urgency, guilt, and squeaky wheels to choose for you.

A ratio below 1.0 means you have margin. You can absorb unexpected demands without cannibalizing existing commitments. You can pursue an opportunity without triggering a cascade of failures elsewhere. The healthy range — the range where systems remain stable, responsive, and sustainable — is 0.70 to 0.85. That means 15 to 30 percent of your capacity is uncommitted at any given time.

This will feel wrong. It will feel wasteful. It will feel like you are leaving potential on the table. That feeling is the exact cognitive distortion this lesson exists to dismantle.

Why the healthy range is not 1.0

Queueing theory — the branch of mathematics that studies how systems process demand — provides the rigorous answer to why operating at full capacity is catastrophic rather than optimal.

John Kingman, a British mathematician, formalized this in the 1960s with what is now called Kingman's formula (or the VUT equation). It describes the relationship between utilization and queue length in any system that processes variable demand. The critical insight is this: as utilization approaches 100%, average wait time does not increase linearly. It increases exponentially. At 50% utilization, queues are short and manageable. At 80%, they are noticeable but tolerable. At 90%, they have roughly doubled compared to 80%. At 95%, they have roughly quadrupled. At 99%, the system is functionally broken — items wait so long in the queue that many of them become irrelevant before they are ever processed.

This is not a metaphor for your life. It is a mathematical description of your life. When you are at 95% capacity utilization, any small perturbation — a sick child, an urgent request from your boss, a pipe that bursts, a friend who needs help — creates a queue that cascades through every other commitment. The tasks you defer today pile up behind the tasks you deferred yesterday. Each one waits longer. Each one requires more context-switching to resume. The system degrades not gracefully but catastrophically, because exponential queue growth means small overloads produce large disruptions.

This is why the sustainable range is 0.70 to 0.85, not 0.95 or 1.0. The 15 to 30 percent buffer is not slack. It is structural integrity. It is the margin that allows the system to absorb variation without collapsing. Remove it, and you are operating a system that works perfectly under ideal conditions and fails violently under real ones. Real conditions include variation. They always include variation.

John Little's proof, published in 1961, adds another dimension. Little's Law states that the average number of items in a system equals the average arrival rate multiplied by the average time each item spends in the system (L = lambda times W). When your commitment load approaches your capacity, lead times — the time between committing to something and actually delivering it — explode. You can feel this in your own experience. When you are at 70% capacity, you promise someone a deliverable and finish it in three days. When you are at 95% capacity, the same deliverable takes three weeks, not because the work itself is harder, but because it sits in a queue behind everything else. The work did not change. The load did.

The cognitive cost: scarcity tunneling

The mathematical argument would be sufficient on its own, but the psychological research makes it inescapable. Sendhil Mullainathan, a Harvard economist, and Eldar Shafir, a Princeton psychologist, published Scarcity: Why Having Too Little Means So Much in 2013. Their research program demonstrated that scarcity of any resource — money, time, social connection — produces a specific cognitive distortion they call tunneling. When you are operating under scarcity, your attention narrows to the immediate demand. You become very good at addressing the crisis directly in front of you and very bad at everything else: long-term planning, maintenance, prevention, relationship investment, strategic thinking.

The tunnel is not a choice. It is an automatic cognitive response to operating at or above capacity. Mullainathan and Shafir measured it: scarcity reduces effective cognitive bandwidth by the equivalent of 13 to 14 IQ points. Not because you became less intelligent. Because your processing power is consumed by the ongoing task of managing overcommitment. You are running background processes — worrying about the deadline you are going to miss, calculating which commitment to sacrifice, rehearsing the apology you will have to make — and those background processes steal cycles from your foreground work. You experience this as brain fog, indecision, or the sense that you "can't think straight." What you are actually experiencing is a commitment-to-capacity ratio above 1.0 manifesting as cognitive degradation.

This creates a vicious cycle. Overcommitment produces tunneling. Tunneling degrades your judgment. Degraded judgment causes you to underestimate the time new commitments require (the planning fallacy, documented by Daniel Kahneman and Amos Tversky in 1979, shows that people systematically underestimate task duration by 25 to 50 percent). Underestimated commitments push the ratio higher. The higher ratio intensifies the tunneling. You do not drift into overcommitment. You accelerate into it, because the cognitive machinery that would otherwise help you say no is precisely what overcommitment impairs.

How to calculate your ratio

The calculation itself is simple. The discipline of doing it honestly is not.

Step 1: List every active commitment. Not the ones you wish you had. Not the ones you plan to start. Every commitment currently drawing on your time or attention. Include your job, side projects, recurring obligations, household responsibilities, health practices, learning commitments, social obligations, and the small favors you said yes to that somehow never end. If it occupies any of your hours or any of your mental bandwidth, it goes on the list.

Most people undercount by 30 to 40 percent on their first attempt. They forget the recurring meeting that "only takes an hour" but requires 30 minutes of preparation and 30 minutes of follow-up. They forget the commitment they made three months ago that they have been quietly ignoring but have not officially dropped. They forget the emotional labor commitments — the friend who calls every week to vent, the family member whose finances you manage, the neighbor whose packages you accept — because those do not feel like "real" commitments. They are real commitments. They consume real hours. List them.

Step 2: Estimate weekly hours for each commitment. Be honest, then add 30 percent. The 30 percent adjustment corrects for the planning fallacy. Kahneman and Tversky's research demonstrated that even when people are explicitly warned about the planning fallacy — even when they have been overoptimistic on the last ten tasks — they still underestimate the next one. The bias is not correctable through awareness alone. It requires a mechanical adjustment. Thirty percent is a conservative correction. For commitments involving other people, coordination, or ambiguity, 50 percent is more realistic.

Step 3: Sum the total. This is your commitment load. Write it down. Look at it.

Step 4: Divide by your measured weekly capacity. If you completed Measure your actual capacity (Measure Your Actual Capacity), use that number. If you did not, use 35 hours as a default for knowledge work. This is not the number of hours you are awake or the number of hours you are "at work." It is the number of hours you can sustain productive output in a given week, measured across real weeks that include interruptions, low-energy days, and the ordinary friction of life.

The resulting ratio is your C/C number. Write it down. If it is above 1.0, you are overcommitted by a precise amount, and no organizational technique will fix it. If it is between 0.85 and 1.0, you are operating without margin and one disruption away from overcommitment. If it is between 0.70 and 0.85, you are in the sustainable range. If it is below 0.70, you have significant capacity available — either for new commitments or for the deep, unstructured thinking that rarely survives a loaded schedule.

What to do when the ratio is above 1.0

There are exactly three interventions, and none of them involve working harder.

Cut. Remove a commitment entirely. Cancel the project. Resign from the board. Drop the course. Tell the person you said yes to that the answer has changed. This is the most effective intervention and the one people resist most, because every commitment was accepted for a reason and abandoning it feels like failure. It is not failure. It is arithmetic. You cannot deliver more hours of work than you have hours. Attempting to do so does not produce more output — it produces lower quality across everything and eventual collapse.

Defer. Move a commitment to a future period when you will have capacity. This is not the same as ignoring it. It is an explicit decision: "I will start this in March when the current project ships." Deferral only works if you actually track the deferred item and reassess your ratio when the time comes. Most people defer by procrastinating — they stop working on something without consciously deciding to, and it lingers on the list consuming mental bandwidth without producing output. Conscious deferral removes it from the active list and from your cognitive load.

Delegate. Transfer a commitment to someone else. This requires that you actually release control of the outcome, not that you assign the task and then hover over the execution. Delegation that generates as much oversight work as the original task is not delegation. It is duplication.

Notice what is not on this list: "try harder," "wake up earlier," "be more efficient," "find a better system." These are the responses of someone who has not calculated their ratio. Once you see the number, these responses are revealed for what they are — attempts to expand the denominator through sheer force of will. Your capacity is not infinitely elastic. Capacity is finite even if ambition is infinite established that. Measure your actual capacity measured it. Capacity varies day to day showed it varies day to day. The denominator is what it is. The only lever you have is the numerator.

WIP limits: the operational principle

David Anderson, in his work codifying Kanban for knowledge work, introduced a concept from manufacturing that maps directly onto the C/C ratio: work-in-progress (WIP) limits. A WIP limit is an explicit, non-negotiable cap on the number of items that can be in progress simultaneously. In a factory, exceeding the WIP limit means the floor is cluttered with half-finished inventory, workers are context-switching between too many tasks, and nothing moves to completion at a reasonable pace. On a personal Kanban board, exceeding the WIP limit means the same thing: too many open loops, too much context-switching, and nothing getting finished.

The C/C ratio is your personal WIP limit expressed as a continuous metric rather than a count. A ratio of 0.80 means you have room for one more significant commitment. A ratio of 1.20 means you need to pull one commitment off the board before you add anything new. The discipline is identical to the factory floor: stop starting, start finishing. Every commitment you add without removing one pushes the ratio up. Every commitment you complete or cut without replacing it brings the ratio down. The goal is not zero commitments. The goal is a ratio that leaves enough margin for the system to function under real-world conditions.

Taiichi Ohno, the architect of the Toyota Production System, captured this in a phrase that should be taped to every desk of every overcommitted knowledge worker: "The more inventory, the less likely you will have what you need." Replace "inventory" with "commitments" and the statement is equally true. The more commitments you hold simultaneously, the less likely any individual commitment receives the time, attention, and quality it requires.

The Third Brain

An AI system with access to your commitment inventory becomes a ratio calculator that operates in real time. Here is the practical architecture.

Maintain a structured list of your commitments in a format your AI can parse — a simple table with columns for commitment name, estimated weekly hours (including the 30 percent planning fallacy buffer), start date, and expected end date. When someone asks you to take on something new, before you respond, describe the request to your AI and ask: "If I accept this at an estimated X hours per week, what does my ratio become?" The AI performs the addition and returns the new ratio. If the answer is above 0.85, it flags the request as a capacity risk and asks which existing commitment you would reduce or remove to accommodate it.

Over time, the AI accumulates historical data: how long commitments actually took versus your estimates, which types of commitments you systematically underestimate, which ones you consistently defer without completing (a signal that they should be cut, not deferred). It can refine the planning fallacy adjustment per commitment type — maybe your writing estimates are accurate but your coordination estimates are off by 60 percent. It can alert you when your ratio has been above 0.85 for three consecutive weeks, which is the point at which queueing theory predicts queue growth begins to compound. It can model what your ratio will look like in four weeks given your current commitment end dates, so you can plan your acceptance of new work against future capacity rather than just present capacity.

The commitment tracker does not need to be elaborate. A shared document, a dedicated note, or even a pinned message thread is sufficient — as long as it is the single source of truth and you consult it before saying yes to anything. The AI layer transforms it from a static list into a dynamic model of your capacity utilization.

The bridge to load balancing

Your ratio is a snapshot — it tells you the relationship between commitments and capacity at this moment. But commitments are not evenly distributed across time. You might have a ratio of 0.80 averaged across the month but 1.30 in the first week and 0.50 in the last. The average hides the peaks, and it is the peaks that break systems.

Load balancing across time addresses this directly. Load balancing is the practice of distributing commitments across time so that your ratio stays within the sustainable range at every point, not just on average. You will learn to map your commitments onto a timeline, identify the weeks where multiple deadlines converge, and restructure the schedule to eliminate the spikes that push you into exponential queue territory. The C/C ratio gives you the diagnostic. Load balancing gives you the prescription.

But the ratio comes first. You cannot balance a load you have not measured, and you cannot measure a load you have not listed. Start there. List everything. Add the hours. Do the division. Look at the number. Whatever it says, it is telling you the truth about why your system behaves the way it does.