In many physician-owned practices, technology quietly becomes a difficult-to-fully-understand area of investment, where even well-run practices struggle to clearly connect spending to outcomes, plus a steady stream of promises of better performance and more efficiencies, which are rarely actually achieved.
Systems become stagnant. Add-ons and integrations proliferate. Contracts renew automatically. Vendors send upgrade recommendations at the last minute, before any rational alternatives can be determined. Leadership reviews the technology budget once a year and has to take the word of their technology teams, whether internal or outsourced, because the complexity of technology makes it difficult to fully see alternatives.
Technology directly shapes clinical throughput, documentation burden, revenue cycle performance, compliance exposure, recruiting strength, and ultimately enterprise value. It affects how physicians experience their day. It determines whether operations run predictably or constantly compensate for friction. It influences whether growth feels controlled or chaotic.
All too often technology seems to take on a life of its own, and is frequently a block or inhibitor instead of the enabler it was promised to be.
When it is treated as a specialized technical silo, instead of being a leadership function (The C-Suite and Physician Leadership), misalignment and disappointment is inevitable.
Stability Is Not the Same as Alignment
One of the most common misunderstandings in healthcare technology is equating “nothing is broken” with “everything is working.”
When IT sets priorities in isolation, even with strong technical competence, the organization optimizes for uptime and the status quo instead of outcomes. Ticket reports say user issues are being resolved. Infrastructure remains stable. Security reports show compliance. Dashboards look healthy. SLAs (Service Level Agreements) are met.
Then why is there so much frustration with tech in healthcare?
Stability at the infrastructure layer does not automatically translate to alignment at the organizational and operational layers.
Physicians begin creating workarounds to move faster through visits. Operations build shadow processes to compensate for inefficiencies between systems. Finance absorbs variability in margins caused by inconsistent workflows or data fragmentation. None of it rises to the level of a system outage, so it rarely feels urgent.
Over time, though, that quiet friction compounds.
Good ticket reports, SLA dashboards and quarterly security reviews do not guarantee organizational success. A system can be stable and still be misaligned with how the practice actually needs to operate, and be causing larger problems that may not be noticeable from the reports coming out of the technology stack.
Leadership Should Decide. IT Should Deliver.
Technology teams are essential. Strong engineers and support teams are critical. Their role is to translate strategy and user needs into systems and solutions, identify risks, options and constraints, and execute with precision.
But their role is not to determine what matters most to the organization.
That responsibility belongs to leadership particularly in physician-owned environments where autonomy, culture, and long-term value are deeply interconnected.
When IT or vendors implicitly set priorities, decisions tend to revolve around tools: products, platforms, security layers, feature sets, technology “stacks”. Those discussions are important, but they are downstream conversations.
The upstream conversation is different:
- What are we optimizing for?
- Where is friction affecting clinical care?
- Where is variability affecting margins?
- Where does technology create drag instead of leverage?
Leadership should decide, IT should deliver.
When those roles blur, technology becomes reactive and tool-driven rather than strategic and outcome-driven. And the organization has to accept whatever technology delivered, with little feeling of involvement, buy-in and collaboration. Technology feels like something that’s done TO them rather than FOR them.
Don’t Call the Vendor. Call Your People.
When something feels off, the reflex is to reach out to the vendor. Sometimes frustration with existing systems means reaching out to a new vendor, before even determining what is the current state. Every vendor out there is hard-wired to showcase how their product is different from whatever you have.
Start internally instead.
Ask physicians where technology slows patient care or adds cognitive burden. Ask operations where duplication, rework, or inconsistent data creates strain. Ask finance where unpredictability appears in revenue cycle performance and margins.
Vendors are built to propose solutions. That is their role. And those solutions many times are focused on feature-sets rather than usefulness, and result in yet another locked-in contract with hidden and unnecessary costs that benefit the vendor, not the practice.
Your people are the ones living with the friction. They are the only ones who can accurately define the problem.
When practices skip this internal clarity step, they often end up layering new tools onto misaligned workflows. The technology stack grows. Complexity increases. The original friction remains. Costs increase. User frustration and resignation becomes the norm.
Technology decisions should begin with organizational alignment, not product demonstrations.
Governance, Not Gadgets
The most resilient physician-owned practices do not treat technology as an operational afterthought. They treat it as a governance issue.
They define clear decision processes.
They involve clinical, operational, and financial stakeholders in prioritization.
They tie technology initiatives to measurable outcomes.
They evaluate vendors and solutions in light of their internal needs and priorities, not on the next BSO (Bright Shiny Object) from vendors.
This is not about slowing decisions down. It is about ensuring decisions are anchored to strategy rather than the latest tech buzz-words or vendor roadmaps.
Technology is now too important to autonomy, profitability, and patient care to sit outside leadership conversations.
It cannot be delegated entirely to engineers. And it cannot be outsourced to vendors who don’t truly have the best intentions.
It belongs at the leadership table.
Because it is too important to leave technology to technology people alone.
