The Team Is Fully Staffed. So Why Is No One Available?
Thanks for reading! Subscribe for free to receive new posts.
Discussion
Be the first to share your thoughts on this article.
Often missing from the capacity picture
Three questions every leader should ask
Need a clear picture of capacity before the next commitment?
Ono Logic helps healthcare and public-sector organizations make workforce obligations visible, identify where capacity debt has accumulated, and build operating models that leaders can actually see and manage.
At Hawaiʻi Pacific Health, an internal improvement effort began with an unusually blunt invitation: Tell us which parts of the electronic health record make you wonder, "Why do I have to do this?"
The program, called "Getting Rid of Stupid Stuff," asked clinicians to identify documentation requirements and routine tasks that should be eliminated, changed, or better explained. The improvements ultimately saved an estimated 1,700 nursing hours each month across the health system.
That number matters because it exposed work that had been hiding in plain sight. No single field, alert, or documentation requirement appeared large enough to create a staffing crisis. Each task was simply part of the job. Multiplied across hundreds of employees and thousands of encounters, however, those small obligations consumed the equivalent of a substantial workforce.
That is how many capacity problems begin. Not with an obvious shortage. Not with one impossible assignment. They develop through recurring requests, redundant controls, informal coordination, unresolved exceptions, and small additions that no longer look optional once they become routine.
A team can therefore appear fully staffed while having almost no capacity left.
Organizations tend to measure the work that is easiest to name. Job descriptions list responsibilities. Project plans list assignments. Time sheets record hours. Organizational charts identify reporting relationships.
Those tools are necessary. They are also incomplete.
They rarely capture the time required to prepare a decision before a meeting, reconcile competing information afterward, follow an approval across departments, review a vendor's work, respond to an urgent leadership request, or repair something that arrived incomplete.
They rarely account for the manager who checks a document before it reaches an executive, the analyst everyone calls because the formal system cannot answer the question, or the employee who remembers why a process was designed the way it was five years ago.
This is the work between the work. It includes coordination, interpretation, review, escalation, documentation, exception handling, and rework. In regulated organizations, much of it cannot simply be dismissed as bureaucracy. It may be what makes a decision traceable, a payment defensible, a service safe, or a program compliant.
The problem is not that this work exists. The problem is that organizations frequently plan as though it consumes no capacity.
In capacity reviews, I have repeatedly seen teams that appeared adequately staffed until recurring coordination, reporting, review, and exception work was assigned a realistic effort value. The staffing number had not changed. What changed was the organization's ability to see what its people were already carrying.
When formal capacity runs out, work does not disappear. It moves.
A dependable employee takes one more assignment. A manager agrees to another weekly report. A subject-matter expert becomes the unofficial reviewer for work produced across several teams. A project launches while the old process continues "temporarily," sometimes for years.
The organization continues to function, so the arrangement can look successful. But when a process depends on a small number of people repeatedly absorbing work that was never formally assigned or measured, the organization is not demonstrating capacity. It is receiving a private subsidy from its most dependable employees.
This is often described as commitment or resilience. Sometimes it is. It is also a fragile operating model.
The people who absorb hidden work become harder to replace, more difficult to promote, and increasingly likely to become bottlenecks. Their knowledge remains trapped in personal routines rather than transferred into processes the organization can sustain.
Eventually, being indispensable becomes another word for being overloaded.
I use the term capacity debt to describe what accumulates when an organization adds obligations without retiring, redesigning, or properly resourcing existing work.
Like financial debt, capacity debt allows an organization to move forward today by borrowing from tomorrow. A new initiative begins without ending an older one. A temporary report becomes permanent. A new technology is introduced while legacy controls remain in place. A program expands without accounting for the approvals, coordination, and evidence required to support the additional work.
For a while, the cost remains hidden. Then the interest comes due.
Decisions take longer. Routine work begins to slip. Quality reviews are compressed. Employees work outside normal hours. Project teams compete with operations for the same people. Leaders become frustrated that work is moving slowly, while staff struggle to explain why there is no room left.
Healthcare offers a visible example. A 2026 National Academy of Medicine commentary described the "1.2-FTE problem," in which a clinician employed for one full-time role effectively performs an additional, largely invisible administrative shift. The precise burden varies by role and organization. The operating pattern does not: the formal assignment reflects one amount of work, while the actual system requires more.
Urgency can conceal that difference for a while. It cannot eliminate it.
When leaders discover a capacity problem, they often reach quickly for a solution: hire more people, reorganize the department, purchase new software, automate the workflow, or require better prioritization.
Any of those responses may be appropriate. None can be evaluated honestly without first measuring the work.
Atrius Health demonstrated the value of that sequence when it addressed the volume of messages reaching primary-care physicians through the electronic health record. The organization first examined the types and quantities of messages physicians were receiving. It then applied a combination of elimination, automation, delegation, and collaboration. By 2022, Atrius had reduced total daily inbox volume for primary-care clinicians by approximately 25 percent. The result was not produced by telling physicians to work faster. Atrius made the work visible, separated necessary activity from low-value activity, and redesigned responsibility around the work that remained.
The Department of Defense offers the same lesson from a different direction. A 2024 Government Accountability Office review found that the department did not know how many contractor personnel supported its financial-management workforce or what functions they collectively performed. That missing visibility created a major obstacle to assessing workforce needs and capability gaps.
Automation without a baseline may move work rather than remove it. Additional staffing may reinforce a broken process. Reorganization may change reporting lines without changing the obligations consuming people's time.
The first question should not be, "What solution should we buy?" It should be, "What is actually happening?"
Capacity questions are part of a broader readiness conversation: start with a 20-minute readiness conversation about what is being implemented and where execution is getting difficult.
Capacity planning is sometimes treated as an exercise in proving that employees are busy. That is the wrong objective.
A useful capacity review should determine how much dependable operating room remains and what conditions are consuming it. It should make trade-offs visible while leaders still have choices.
Headcount can answer how many positions are filled. It cannot, by itself, show how much dependable operating room remains. That requires understanding the work employees perform, the obligations surrounding it, and the burden created by the systems meant to support it.
Before approving the next initiative, adding another report, or promising another deadline, ask: When this new priority begins, what will stop, move, or wait?
When the answer is "nothing," leadership has not eliminated the trade-off. It has transferred the trade-off to the workforce and made it harder to see.
A fully staffed organization is not necessarily an organization with capacity. Sometimes it is simply an organization whose people have become very good at carrying the difference.