THANK YOU FOR SUBSCRIBING
A featured contribution from Leadership Perspectives: a curated forum reserved for leaders nominated by our subscribers and vetted by our Healthcare Tech Outlook Advisory Board.



It is 6:45 p.m. A physician has finished seeing patients but is still at the keyboard, finishing notes. Home and family are waiting. A technology leader might see an opportunity for AI to improve efficiency. The physician may see something else: another demand on a long day. I understand both perspectives, but AI can only help if we understand the physician's day first. Over the years, I have learned that healthcare transformation begins with people, not platforms.
Start where the work happens.
I've worked in large health systems and now at Mahaska Health, a rural Iowa Critical Access Hospital. Across those settings, some of my most valuable conversations have happened away from a conference room, standing beside the people doing the work. In Lean methodology, we call this the gemba. I think of it more simply: show up, listen and see the day through someone else's eyes. You see workarounds that never make it into a project plan and the resourcefulness of people caring for patients.
Ambient clinical documentation is a beneficial example. AI can help draft a note, but the note itself is not the goal. What matters is whether a physician can look a patient in the eye, stay present in the conversation and leave work with fewer unfinished notes. Physicians need a real voice in how these tools fit their day and to say when they fall short. We earn adoption by building with people, not by asking them to accept what we have already decided.
Build trust before the pilot.
Trust is built in the small moments, especially when someone raises a concern and sees that we take it seriously. AI also calls for sound data, privacy and cybersecurity protections, human oversight and clear accountability. They matter because clinicians must trust that our tools support safe, compassionate care. Leaders must be clear about AI's capabilities and who is responsible for decisions.
“Technology enables transformation. People make it happen.”
At Mahaska Health, our AI work focuses on three areas that touch people's daily experiences: physicians, patients and revenue cycle. We are using ambient documentation to ease the work surrounding a patient visit, exploring tools that help care teams spot gaps in care and applying analytics to understand payer denials. Each conversation begins with a question: What is making your work harder than it needs to be, and what would “better” look like for you?
Solve for people, measure the impact.
I believe we should define success in terms people recognize before we put numbers on a dashboard. For a care coordinator, it might be finding important information without searching through pages of records. For a patient, it might mean fewer gaps between visits and a team that knows their story. Operational and financial measures should show whether those experiences improved.
Take the revenue cycle. Every denial may mean another claim to research and correct. Helping that person avoid unnecessary rework is a worthwhile starting point. We can then measure time spent per denial, rework volume and preventable denial rates. Better reimbursement supports community care but should follow from improving the work.
That means listening first, setting a baseline, and coming back to ask whether life at work actually improved. Some ideas will fall short. When they do, we owe our teams an honest conversation, a willingness to adjust and sometimes the courage to stop. Trust grows when feedback changes the course.
From insight to action
I keep coming back to that physician at 6:45 p.m. The last patient has gone home, but the workday has not ended. Enthusiasm for a tool will not give that time back. We have to listen, design a better way together and learn whether it helped. Behind every workflow is a person trying to do good work for someone else.
As leaders, we set the tone. When a nurse, physician, or team member tells us something is not working, our first response should be curiosity, not defensiveness. Thank them, learn and make it safe to speak up again. That is how a pilot becomes a partnership and how lasting change takes root.
I do not believe the organizations that benefit most from AI will necessarily be the ones that move fastest or spend the most. They will be the ones willing to listen, build trust and keep learning alongside their people. My challenge to leaders: spend time where care happens and let people's needs guide what you build. Don't measure leadership success only by the technology you deploy. Measure it by the difference you make for the people who use it and the patients they serve. Technology enables transformation. People make it happen.