FIELD NOTE |
February 4, 2026
The Organization Is Borrowing Capacity From Its People
An organization can look remarkably capable when capable people are quietly absorbing the difference between what it promised and what it actually built.
I once resigned from a company I loved because I could no longer reconcile what the organization wanted to accomplish with what it was asking people to absorb in order to accomplish it.
At the time, I was regularly working twelve-hour-plus days. My team was under-resourced even as the work around us continued to expand. I was moving between licensing and auditing, customer negotiations, new-product introductions, technical support, change management, data, and operations.
We supported a growing go-to-market organization while the infrastructure underneath it was not growing at the same rate.
The interesting thing is that the work was still getting done.
That was part of the problem.
From the outside, an organization can look extraordinarily capable when what it actually has is extraordinarily capable people compensating for the organization.
For a long time, I thought being able to hold that much complexity was evidence that I was particularly good at my job.
In some ways, it was.
But I eventually understood that my ability to compensate for the system was also preventing the organization from fully experiencing the cost of the system.
Every time I caught something before it broke, translated between teams, stayed late, built the missing bridge, or figured out how to execute a decision that had not accounted for execution, the organization received an outcome it had not actually built the capacity to produce.
My competence was hiding the organization's constraint.
When compensation looks like capability
Organizations tend to evaluate capacity through what gets accomplished.
Did we launch the product? Close the deal? Complete the audit? Deliver the report? Support the customer?
If the answer is yes, the operating model appears to be working.
But output and capability are not the same thing.
A team can produce enormous output while spending much of its energy compensating for the conditions under which that output is produced.
Someone manually reconciles data before every forecast. A manager attends meetings because decisions stall without them. An operator maintains a private spreadsheet because the official system cannot represent what the work requires. Someone remembers which customer has an unusual contractual obligation because that information never made it into the systems everyone else relies on.
The work happens.
But the organization hasn't necessarily developed the capability to do that work reliably. It has developed a dependency on people who can make up the difference.
And the better those people are at compensating, the harder the dependency can be to see.
I've written before about the experience of noticing things other people don't seem to notice. I wasn't simply being asked to carry more. I was also someone who found it difficult to leave a problem alone once I understood it.
If I could see the missing connection, I wanted to make it. If I understood why a process wasn't working, I wanted to repair it. If two teams were operating from incompatible assumptions, I wanted to reconcile them.
There is real value in that kind of attention.
There is also a cost.
Systems are remarkably good at discovering who will absorb ambiguity.
The person who notices the missing handoff gets the handoff. The person who can translate gets more translation. The person who can carry several functions at once becomes evidence that several functions don't need to be staffed.
Eventually, competence becomes a subsidy.
That doesn't mean the person carrying the work has no agency in the arrangement. I had choices, even when they were difficult ones. I also had a sense of responsibility that made some of those choices harder to exercise.
But the organization had choices too.
It controlled priorities, staffing, resources, and much of the authority required to change the conditions producing the work.
Those responsibilities aren't interchangeable.
The competency cost
There's another dimension to this that I think deserves attention, particularly for women in leadership.
Competence can become a career constraint.
Researchers Linda Babcock, Maria Recalde, Lise Vesterlund, and their colleagues have studied what they call non-promotable tasks: work that benefits an organization but does relatively little to advance the career of the person performing it.
Their research found that women were disproportionately asked to take on this work and were more likely to volunteer for it.
The research helps explain something I've been thinking about for years.
What happens when the person who is particularly good at making an organization function becomes so valuable in that capacity that the organization has little incentive to let them do anything else?
The person who anticipates problems becomes responsible for preventing them. The person who can manage difficult relationships becomes responsible for maintaining them. The person who can coordinate across functions becomes the unofficial owner of everything that falls between them.
And because the work is important, it keeps coming.
The organization may recognize and appreciate these contributions without treating them as evidence of strategic leadership.
Then, when advancement is discussed, the conversation turns to whether the person has demonstrated enough strategic thinking, executive presence, or readiness for a broader role.
There's a contradiction here.
The organization can consume someone's capacity to do strategic work and then evaluate them on how much strategic work they managed to demonstrate.
The person may have spent years keeping the organization operating, resolving structural problems, developing people, and making decisions across functions.
But if that work is categorized as execution, their contribution can be interpreted as evidence that they're an excellent operator rather than someone capable of designing and leading the system.
I think that's worth questioning.
Sometimes the strategic work is already happening. It's simply being recognized as operational competence because of the position the person occupies or the kind of work they've become known for doing.
And sometimes the operational demands really have prevented the person from developing or demonstrating other capabilities.
Those are different problems. Both deserve attention.
This isn't exclusively a women's experience, and not all operational work is non-promotable. But the research suggests that the distribution of work and the criteria used to reward it are not necessarily neutral.
I wonder how often women are expected to demonstrate leadership by making everyone else's leadership possible.
Keeping people aligned. Remembering what was agreed. Anticipating reactions. Smoothing over conflict. Making sure nobody is surprised. Finding a way to deliver even when the resources aren't there.
At what point does being indispensable translate into authority?
And at what point does it simply mean more people know who to call?
Being trusted isn't necessarily the same as being supported.
Being indispensable isn't the same as having power.
And being exceptionally good at maintaining a system doesn't mean that maintaining it is the highest-value contribution you could make.
What the work is actually costing
Organizations are generally good at naming visible work.
Launch the product. Close the deal. Ship the feature. Publish the report. Resolve the ticket.
We're less precise about the work required to make those outcomes possible across boundaries.
Someone translates what Product means into language Sales can use. Someone notices Finance and Customer Success are using different definitions. Someone carries context from one meeting into another because the systems don't. Someone repairs a relationship after a difficult handoff. Someone recognizes that a decision made in one part of the organization has created a problem somewhere else.
Some of that work is unavoidable.
Coordination isn't the absence of execution. It's part of what allows multiple people to execute in a shared direction.
But when we don't account for it, we don't eliminate its cost.
We distribute that cost to whoever is willing or able to absorb it.
I will map systems, draw diagrams, pull reports, and join keys all day—but unless we learn to execute in a shared motion, we will overburden our most valuable resources: our people and our teams.
Not every manual intervention is a problem. Not every exception needs to be automated. Not every boundary needs to disappear.
Human beings are valuable precisely because we can notice, interpret, adapt, and respond to things a formal system wasn't designed to anticipate.
I don't want to eliminate that flexibility.
I want to understand what we're using it for.
There's a difference between relying on human adaptability to learn what a system needs and relying on it indefinitely as a substitute for building what the system needs.
The first can make an organization stronger.
The second can make the organization increasingly dependent on people continuing to absorb costs it hasn't acknowledged.
Early-stage companies often depend on extraordinary human flexibility for good reasons. Roles are fluid. Information changes quickly. People cross boundaries because the boundaries themselves are still emerging.
That can be appropriate for the stage of the organization.
But temporary conditions have a way of becoming permanent assumptions.
We move fast can mean planning is someone else's problem.
Everyone pitches in can mean ownership remains permanently ambiguous.
High agency can mean people are expected to solve around structural constraints without the authority to change them.
What began as flexibility becomes dependency.
And because the organization is still producing results, there may be little immediate pressure to reconsider the arrangement.
This is one reason I pay attention when an organization describes itself as lean.
Lean relative to what?
Its headcount? Its revenue? Its operating expenses? The amount of work being accomplished?
Or the total human effort required to produce and sustain those outcomes?
Those aren't necessarily the same measurement.
A company can have low operating expenses because it has designed an efficient system.
It can also have low operating expenses because people are supplying the missing infrastructure through their own time, attention, relationships, and judgment.
Both may look efficient on a financial statement.
They are not the same operating model.
When the borrowing stops
People are remarkable shock absorbers.
We remember what the system forgets. We translate between functions whose language no longer matches. We recognize exceptions. We maintain relationships that keep brittle processes moving. We find ways around obstacles because customers still need answers and the work still needs to happen.
But that capacity is finite.
Eventually, someone leaves. Someone stops volunteering the extra hour. Someone reaches a limit. Someone encounters another responsibility that requires the capacity they've been giving away.
Or they remain, but no longer have the room to notice what is changing, question an assumption, develop someone else, or think beyond the next urgent problem.
The organization may experience the consequences as a sudden failure.
But the constraint wasn't necessarily new.
What changed was the availability of the person who had been compensating for it.
And the cost isn't limited to burnout or turnover.
It's also the work that never happens.
The system improvement nobody has time to design. The person who doesn't get developed because their manager is permanently resolving exceptions. The opportunity nobody investigates because the team is already operating at its limit.
The organization can be so busy delivering what it has already committed to that it loses the capacity to become something different.
That is particularly difficult to see because the evidence of the problem is often an absence.
Something wasn't explored. A relationship wasn't developed. A risk wasn't recognized early enough. An idea never became an experiment.
None of those necessarily appears on a dashboard.
And I think this is where the distinction between output and capability becomes most important.
Output tells us what the organization accomplished.
Capability tells us something about what it can continue to accomplish, under what conditions, at what cost, and with what room left to respond to something unexpected.
A system that requires extraordinary effort to produce ordinary results may be delivering, but it isn't necessarily healthy.
A system that depends on a handful of people to remember, reconcile, interpret, and intervene may be effective today without being durable.
And a system that consumes all the capacity of its most capable people may be sacrificing its ability to improve in exchange for its ability to keep going.
I don't think the answer is to stop expecting people to stretch, help each other, or take responsibility beyond the narrowest interpretation of their roles.
Those are things I value.
But I want that effort to contribute to something the organization can retain.
When someone repeatedly solves the same problem, what have we learned about why the problem keeps occurring?
When a person becomes indispensable, what have we learned about the capabilities the organization hasn't developed?
When a team delivers through extraordinary effort, what would it take for the next delivery to require less of that effort?
When someone spends most of their time making everyone else's work possible, how are we recognizing and rewarding that contribution?
And when someone says they can't keep carrying what they're carrying, do we treat that as information about the system—or as a problem with the person?
I left a company I loved because I couldn't reconcile the work we wanted to do with what it was taking to do it.
I don't think the work was unimportant. I don't think the people were incapable. And I don't think every difficult period means an organization is poorly designed.
Sometimes extraordinary effort is warranted.
But extraordinary effort shouldn't become invisible simply because the people providing it are capable of sustaining it for a while.
An organization can keep delivering while quietly accumulating a debt to the people making delivery possible.
Sometimes that debt appears as turnover or exhaustion. Sometimes as opportunities that never get pursued. Sometimes as capable people who no longer have room to think.
And sometimes it remains invisible because the people carrying it are still succeeding.
The work getting done is not proof that the organization has built the capacity to do it.