477- When Not to Implement Technology w/John Wurl

Phil Howard & John Wurl

477- When Not to Implement Technology w/John Wurl

THE IT LEADERSHIP PODCAST
EPISODE 477

477- When Not to Implement Technology w/John Wurl

20
1 X
20
00:00 | 00:00

Short Clips

Episode Highlights

John Wurl

GUEST BIO

John Wurl started at the lowest level, as a systems engineer on Z80 processors, counting bits and capturing interrupts. What kept him in technology after he moved into IT is how solutions are found and implemented: "It's about the ecosystem that that technology is placed in." That view has gotten him in trouble, because people always go, "but I want this software." His habit is to step back and analyze, and reports are his favorite example: "What is this report going to tell us?"

He makes the case for bringing technology into the upfront conversation, where he sees "almost this militant rejection" of the value technology people can add. His way in is to educate the people deciding on their options, then let them drive the decision. He notes that every change brings a new C title, though "leadership is an organization function." And he explains why "sometimes the best technology solution is not to implement technology": count the dollars and the new problems a solution brings before you commit. When a board pushes for an expensive system, he brings the case back to a financial impact, and the answer usually turns out to be "this, then that."

On AI, he argues it "is misunderstood as a technology problem." He tells how billing issues started when people asked an AI tool outside the EHR for a CPT code, and why he keeps bringing those discussions back to the executive team. His county's AI governance team meets once a month to validate the tools and models staff use. He closes on his agency's mission, serving the underserved through its federally qualified health center (FQHC), and the advice he'd give his younger self: "be curious about things outside of what you're doing, outside of your responsibility."

Network Assessment

Your monthly IT spend should be boring.If it's not, something is wrong.

Network Friction Score
BoringChaotic
Do you have provider/support numbers handy, or is it 1-800-GO-POUND-SAND?

We review circuit consolidation, contracts, security, outage visibility, billing, and future flexibility to reduce chaos without forcing change.

▸Circuit consolidation
▸Contracts & pricing
▸Firewall management
▸Outage alerts
▸Edge security
▸Billing & licensing
Boring results. Reputable savings.
Consolidation that makes sense.
Show Notes

Episode Show Notes

Navigate through key moments in this episode with timestamped highlights, from initial introductions to deep dives into real-world use cases and implementation strategies.

[00:00] Cold open, and a first computer built on a Z80

[02:10] Coordination, processes, and AI as an amplifier

[05:25] Solutions live in an ecosystem

[08:53] What is this report going to tell us?

[11:44] Making it their decision

[15:31] Laying out the options, and repositioning staff with AI

[20:06] A new C title for every change

[21:01] Sometimes the answer is not to implement technology

[22:19] When the system doesn't fit the clinic: this, then that

[29:47] Boards, the financial case and the human at the end

[38:39] Bring in the experts, and take AI to the executive team

[50:56] Serving the underserved, and being curious

KEY TAKEAWAYS

Before you build the report or buy the software, ask what it is going to tell you and whether it fits into a workflow. The operational system may already hold the information.
Count the problems a technology solution creates, in dollars and resources, along with the one it solves. Sometimes the right call is not to implement technology.
Educate the decision makers on each option, then let them drive the decision so the team owns it.
Make the business case in financial terms, mapped to the capabilities that create value for your end users, and offer a "this, then that" path when a big switch isn't the right move yet.
When people resist a change, bring in the experts (John brought in a board member who teaches data analytics) and step back from the discussion.
Take AI decisions up to the executive team: run an AI governance team that validates tools and models, and ask each leader how the AI in their products affects their workflow.
477- When Not to Implement Technology w/John Wurl
logo

You’ve Been Heard

You’ve Been Heard is where IT leaders stop being sidelined and start being amplified. We’re the triple-threat platform: podcast, community and vendor-neutral advisory that elevates your voice, your value, and your influence because when IT leaders rise, so does everything else.

© 2026 You've Been Heard. All rights reserved.