Organizational Design · Attention
Measure Execution Load Before You Accept the Next Obligation
Contract value tells you what you will be paid. It does not tell you what it will cost to deliver alongside everything you already said yes to.
Key Takeaways
- Execution load is a different quantity from contract value, composed of concurrency, decision volume, exception rate, dependencies and follow-through. A small obligation can outweigh a large one on every dimension that binds.
- The binding constraint is usually decision capacity, which is concentrated in very few people. Value scales with the work; decision volume scales with the number of distinct commitments and their variability, and only the first appears on a revenue forecast.
- The relationship is not linear. Waiting time rises steeply as utilization approaches capacity, which is why the commitment that breaks an organization is normally indistinguishable in size from the several before it that did not.
Two quantities that get treated as one
The size of an obligation is what you will be paid, and it is measured accurately because someone is paying it. The load is what delivering it costs you in the currency that is actually scarce, alongside everything else that is live. Organizations track the first with precision and estimate the second by feeling, then treat a favorable answer on the first as a reason to accept.
The two diverge most sharply in small and midmarket organizations, where the people who resolve exceptions are also the people who sell, and where a single obligation's decision volume can occupy a founder entirely. It is why a firm can grow revenue and lose the ability to deliver at the same time, and be genuinely surprised by it.
Why the last commitment is the one that breaks it
Queueing theory supplies the shape and it is not intuitive. Kingman's approximation has waiting time rising non-linearly with utilization, gently while there is slack and then very steeply as the system approaches full. The practical consequence is that an increment costing almost nothing at sixty percent utilization costs enormously at ninety, while looking identical on the way in.
This is why the post-mortem question of what was different about the obligation that caused the problem usually has no satisfying answer. Frequently nothing was different. It arrived later.
The measure that misleads
A utilization figure that looks healthy in aggregate can conceal a person at a hundred percent. Little's Law relates work in progress, throughput and cycle time for a system; it says nothing about a system whose capacity is one named individual appearing in every queue. Aggregate capacity is the wrong unit when the constraint has a name.
Five dimensions to score before accepting
Concurrency
What else is live in the same window, and does it peak at the same time? Two obligations that are each comfortable alone can be impossible together if their intense phases coincide, and nothing in either contract mentions the other.
Decision volume
How many judgment calls does this generate per week, and by whom? This is the dimension most often left unmeasured and most often binding, because decision capacity is concentrated in a handful of people who are already spending it elsewhere.
Exception rate
How often does the standard path fail, and what does recovery cost? A five percent exception rate on a high-volume obligation is a full-time role that appears in no budget and was never staffed.
Dependencies
How many parties outside your control can stall this? Each one is a queue you do not manage, and delay compounds through a chain rather than averaging across it.
Follow-through
What does it demand after the deliverable is accepted? Support, reporting, audit, renewal, relationship maintenance. This load persists after the revenue is recognized and is almost never in the decision to accept.
Score each from one to five for the obligation under consideration, then repeat the exercise for everything already live in the same period. The total is not a decision rule and should not be turned into one. Its value is that it makes the conversation about the right quantity, and it exposes the case the revenue figure hides: several small obligations that are individually trivial and collectively binding on the same two people.
The named-individual test
List every live obligation and, beside each, the people who resolve its exceptions. Not the account owner: the person actually called when the standard path fails. If the same two names appear across most rows, the portfolio has a single point of failure that no revenue forecast will show and no additional headcount will immediately relieve, because the constraint is accumulated context rather than hours.
Goldratt's argument holds without modification here: an hour lost at the constraint is an hour lost by the whole system, and an hour saved anywhere else is an illusion. Adding delivery capacity to an organization whose constraint is a founder's decision throughput will make the queue longer, not shorter.
What to do with the answer
Three responses, in order of how often they are correct and inverse order of how often they are chosen. Decline the obligation, which is the answer a full portfolio requires and the hardest one to give when the value looks good. Sequence it, moving the intense phase away from an existing peak, which frequently costs the client nothing and is rarely asked for. Or reduce load elsewhere first, which means naming what stops, and is the one that connects this to every other attention problem an organization has.
Priority Theater takes up what happens when nothing is allowed to stop, and attention margin is the capacity this whole calculation is spending.
The Four A's reading
This is Attention, arriving as a commitment decision rather than a prioritization one. The Four A's ask what must stop so the critical work can move; execution load asks the same question one step earlier, before the commitment that will make the answer urgent. An organization with no measure of load has no basis for declining anything, which means its portfolio is determined by what it was offered rather than by what it can carry.
Authority is the second half, and it decides whether the measurement matters. Someone has to be able to say no to revenue. If that right does not exist, or exists in theory and has never been exercised, a load measurement is a diagnostic with no attached decision.
About the Author
Dan Flynn
Creator of The Four A's of Organizational Readiness™ · Enterprise Transformation Executive · Author, Builders Build
Dan Flynn has spent thirty years inside federal, defense, and commercial organizations: diagnosing the invisible conditions that determine whether capable people produce extraordinary results. He is the creator of The Four A's of Organizational Readiness™ framework, has reached more than 11,000 professionals across corporate, civic, and national security contexts, and took a federal data platform from one release every six months to seventy-two every two weeks by changing organizational conditions: not people.
His book, Builders Build: The Four A’s of Organizational Readiness™, is forthcoming.