“In capital-planning conversations, every request sounds urgent . . . but many capital requests are not about need, they are about want,” says Marc Schlessinger, Staritas’s Principal Consultant & Investigator.
A department has a patient care issue. A physician is frustrated with aging equipment. A competitor just installed the latest technology. The language is compelling, the stakes feel high, and the default response becomes, “We need this.”
When organizations fail to separate need from want, the result is predictable: constrained budgets, reactive decisions, and investments that do not move the organization forward.
Why This Happens
Many capital procurement processes are designed to collect requests, not to evaluate them. Departments build their cases and advocate for their priorities. The strongest narratives rise to the top.
What is often missing is a consistent way to answer a harder question:
Is this request solving a verified organizational risk or advancing a defined strategic goal?
Without that filter, three dynamics tend to dominate:
- The most vocal stakeholders receive priority
- New technology looks more valuable than it is
- Real risk competes with preference
What a True “Need” Looks Like
A need is tied to one of a small number of measurable realities:
- A patient or staff safety risk
- A regulatory or compliance exposure
- A documented failure rate or end-of-life asset
- A capacity constraint that limits access or revenue
- A strategic service line that cannot move forward without the investment
In contrast, a want is usually driven by:
- Physician preference
- Standardization that is not clinically or operationally required
- “Keeping up” with competitors
- A general perception that equipment is old, even if it remains functional
Both may be valid considerations. However, only one should drive capital-planning priority.
What This Looks Like in Practice
Consider two scenarios that illustrate how easily age, perception, and preference can blur the line between need and want:
A True Need
An operating room table with a failing hydraulic system was only midcycle based on age. On an inventory report, it appeared to have years of useful life remaining and would not have ranked as a near-term priority. In practice, it was shifting during active procedures, and repeated repairs had failed to correct the problem. The risk was immediate and clinical—not theoretical.
What looked like a low-priority asset on paper became a top priority the moment safety and reliability were factored in. Age suggested waiting. Risk made the decision clear.
A Common Want
In another case, a CT scanner was flagged for replacement because it was approaching its expected lifespan and newer technology was available. At first glance, the request felt reasonable. No organization wants to fall behind technologically. But when utilization, service history, and current performance were reviewed, there was no documented capacity constraint, no quality issue, and no strategic program dependent on an upgrade. The equipment was still meeting clinical demand.
The urgency came from perception, not risk. What seemed like a need was ultimately a preference for newer technology rather than a requirement to support patient care or organizational performance.
The lesson in both cases is the same: the request does not define the priority. Verified risk, utilization, and strategic impact do. When those elements are applied consistently, some midlife assets move to the top of the plan, while others that “feel due” fall off entirely.
The Hidden Cost of Getting This Wrong
“When need and want are treated as equal, real risk gets delayed, capital becomes reactive, and strategic alignment disappears,” says Schlesinger.
Over time, this erodes confidence in the entire process. Leaders stop seeing capital planning as a strategic function and start seeing it as an annual negotiation.
A Better Way to Structure the Conversation
Organizations that effectively separate need from want tend to approach capital planning differently. They typically do three things:
- Define risk in objective terms
- Require a clear link to strategy
- Create visibility across the entire asset inventory
When these elements are in place, capital decisions shift from advocacy to alignment. The conversation becomes: What does the organization need most right now? rather than Who made the most compelling case?
A Simple Test for Your Next Capital Cycle
Before your next capital cycle, consider three questions:
- Do we have a shared definition of need?
- Can we perceive risk as enterprise wide?
- Does every funded request advance a strategic objective?
If the answer to any of these questions is “no,” it may be a sign that your organization is still working to clearly distinguish need from want.
Organizations seeking a more objective, defensible approach often begin with an independent view of their inventory, risk exposure, and replacement timing. Staritas works with health systems to build 10-year capital replacement plans that align clinical risk, utilization, and strategy—ensuring capital decisions are driven by need—not urgency.
Learn more about how we can help you prioritize the assets that protect patient care, preserve throughput, and support long-term strategy.
