Every Technology Yes Is a Capacity No
Noelle Brackett, Founder & CEO, Smith Mountain Advisors
I’ve sat through hundreds of technology approval meetings. I can tell you almost exactly what got scrutinized: the capital cost, the subscription cost, the implementation cost, sometimes the staffing plan for the project team. The dollars had to survive real questioning, and they usually deserved it.
What I rarely saw examined with the same rigor was the other thing we were about to spend.
Every technology yes spends two currencies. The first is money, and most organizations govern it carefully — budgets, business cases, capital committees, variance reports. The second is capacity: training hours, clinician attention, workflow redesign, analyst time, go-live support, governance bandwidth, and the organization’s finite reserve of trust that the next change will be worth it.
The money gets a business case. The capacity often gets assumed.
The second price
Here’s what makes the second price different from the first. Money can be reallocated, borrowed, or replenished through the next budget cycle. Capacity is more difficult to replace. You cannot give a clinician back the hour spent in training, or recover the quarter in which an operational improvement sat unfinished.
The same clinicians who must absorb this implementation are the ones still absorbing the last one. The same analysts supporting the new platform are the ones who were supposed to finish the optimization backlog. The same governance calendar that reviews the next proposal is the one that never got back to measuring the previous one.
And when capacity is overspent, nothing fails loudly. There’s no overdraft notice. Everything just slows. Adoption plateaus. Training gets compressed. The workflow redesign that the business case quietly depended on gets deferred. The investment goes live — and underperforms in ways nobody connects back to the five other things that were competing for the same attention.
Every yes is a no. The question is whether you chose it.
When an organization says yes to something, it is also saying no — or at least not yet — to something else. That isn’t a figure of speech. It’s arithmetic. The training calendar has a fixed number of hours. The clinical departments can tolerate a finite amount of workflow change in a quarter. The analysts, the educators, the operational leaders who make technology actually work are not an expandable resource, however the roadmap is drawn.
So, the no or not yet is real. It just rarely gets decided.
The yes is explicit — a committee, a signature, a kickoff meeting. The no is implicit: a workflow fix deferred again, an optimization effort that aged another quarter, an adoption push that got half the support it needed, a capable team that quietly stopped believing the roadmap. The trade happened. It simply happened without an owner, without a record, and without anyone comparing what was gained to what was given up.
I’ve written before that if nothing was displaced, nothing was prioritized. This is the same principle seen from the other side: something is always displaced. Prioritization just determines whether you picked it.
Why the ledger matters more now
For much of the last two decades or so, organizations planned around an eventual steady state after the EHR implementation — a period after go-live when teams could recover, optimize, and absorb what had changed. Whether that period consistently materialized is another question. Today, planning around it is increasingly unrealistic.
Capability now arrives continuously — from the platform, from AI vendors, from tools that never pass through a traditional implementation at all. The ledger of yes’s and unchosen no’s doesn’t settle at go-live anymore. It compounds.
That changes the stakes of the trade-off. When yes was an occasional event, an unexamined no was an occasional cost. When yes is continuous, the unexamined no’s accumulate into something structural: a permanent gap between what the organization has committed to and what it can actually absorb — paid for in underperforming investments and exhausted people.
Making the trade visible
This doesn’t require a new committee. It requires a few disciplines most organizations already know how to practice — just not, usually, for capacity.
Denominate decisions in capacity, not only dollars. A business case that states the capital cost but not the training hours, the workflow changes, the support burden, and whose attention it will consume is half a business case. If a technology investment promises $10 million in benefits, but the organization cannot absorb the workflow changes required to realize them, that value is at risk before implementation begins. Ask for the other half.
Require every yes to name its no. Before approval: what are we deferring, slowing, or stopping to make room for this? Written down, specifically. If the honest answer is “nothing,” either the organization has idle capacity — worth confirming — or the no is being made invisibly, which means someone else is going to pay it.
Give the no an owner too. If a yes defers the ambulatory workflow fix by two quarters, the leader who owns that workflow should be in the room when the trade is made — not discovering it later. The displaced item doesn’t disappear from the organization. It shouldn’t disappear from the record.
Revisit the trade. The discipline that completes the loop: was the yes worth what it displaced? Sometimes the answer is no — and the decision that returns the capacity is “stop,” perhaps governance’s least practiced and most undervalued verb.
This may slow an individual approval. But it can accelerate delivery across the portfolio, because the initiatives that move forward have a better chance of receiving the capacity required to succeed.
The question I’d leave you with
Pull up your organization’s last three significant technology approvals.
For each one, ask two questions. What did it cost in capacity — whose hours, whose attention, whose change tolerance? And what did we agree to slow down or stop to pay for it?
If no one can answer, the trades were still made. They were just made by default — by momentum, by whoever escalated loudest, by the calendar.
The organizations that perform best in the next decade of healthcare technology won’t necessarily be the ones that said yes the most. They’ll be the ones that understood what each yes cost and deliberately directed their scarce capacity toward the outcomes that mattered most.
Every yes is a trade-off. The only question is who’s making it.