Does It Eliminate Steps or Create Them? The One-Question Test for Practice Technology
Almost everyone in independent practice now believes technology is part of the answer. In the 2026 survey of 360 independent practice leaders, 79% said technology is critical to staying independent. Yet only 24% said they can see the full picture of the revenue they earn. Leaders believe in the tools, but most can’t yet show the payoff in their numbers.
That gap between belief and benefit is the real subject here. Believing technology matters is now the default position. Being able to point at what it changed is not, and the difference usually traces back to decisions made well before anyone signs a contract.
On our recent panel with Medical Economics, the practice leaders didn’t blame the technology itself. They blamed the way it gets chosen and rolled out. And one of them offered a test simple enough to use in the next vendor meeting.
The test
Dr. Jonathan Copeland credited it to one of his partners. Whenever something new comes into the EMR, the partner asks: “Does it eliminate or does it create steps? If you’re asking me to do something more, what are you taking off my plate?” Then come the clinical questions. Does it move a diagnosis upstream? Does it fit evidence-based guidelines? If the answers are no, Dr. Copeland said, “we should seriously reconsider whether we do it.”
It sounds obvious. It is also the step most rollouts skip.
The test works because it inverts the usual order. Most evaluations start with what a tool can do and work backward to whether anyone needs it. This one starts with the person who has to live inside the software all day and asks what the tool is going to cost them in clicks, attention, and time.
Start with a problem, not a tool
Asked how to bring new tools to a team, Dr. Copeland was blunt. “Don’t start with the technology and don’t say, we’ve got to start using AI. Start with a problem you’re trying to solve.” He means a specific problem. Clinically, that could be preventing a hospitalization, catching dementia earlier, keeping a frail senior at home longer, or preventing a fall. Operationally, it could be a billing or AR problem you haven’t solved yet. The question should be specific enough that you’ll know whether the tool answered it.
Joseph Jacot, CEO of Michigan Vascular, described the same shift in his own practice. “Up till now, every bit of technology that’s been introduced, we’ve just taken it in and said, oh, this is something we have to do.” Now his team maps each step of the patient experience, from authorization and eligibility to rooming, quality gaps, and claim review, and asks where technology can actually help at that step. He called it taking a lean process mentality to the technology.
What that looks like in practice is specific. Eligibility and authorization should resolve before anyone picks up a phone, so the front desk already knows whether the patient is covered and what the copay will be. Known quality gaps should be flagged before the patient is roomed, not discovered afterward. Claims should get scrubbed before they go out, with any missing detail sent back to the clinician while the chart is still open. Each of those is a discrete problem with a measurable answer.
Administrative burden isn’t only the physician’s
It’s easy to treat physician administrative burden as the whole story, and that framing leaves most of the practice out.
Jacot sees it from both chairs. As a clinician he feels the weight of clicking through everything the software asks for. As a CEO he watches the front desk doing a version of the same thing, and the billers doing another version again. Everyone in the building is carrying administrative burden, which means a tool that relieves one role while adding steps for two others hasn’t actually helped the practice.
That is worth holding onto when a vendor demo focuses on the physician experience alone. The steps test applies to every seat the software touches.
Fewer boxes, not more
The panel also agreed that simple wins. “It doesn’t have to be real shiny or real fancy,” Dr. Copeland said. “It just has to be really effective and simple.” If a screen already has eight boxes to look at, he doesn’t want a ninth. He wants seven. Physicians are creatures of habit, he pointed out, and an unexpected change in a familiar workflow can become a patient-safety issue.
He put the principle more plainly later. The workflow should serve the provider’s clinical brain, not the other way around. Physicians shouldn’t have to prove or document their medical thinking to satisfy the software. And the payoff for getting this right shows up in people, not just in metrics: he said he has seen physicians less burned out and more excited about practicing when the technology around them gets simpler.
Jacot had a lighter example. His last EHR update changed the color and the font at the same time, and that was too much for everybody at once. His rule: change one thing, improve it, and keep the rest steady.
Adoption is about how a tool is delivered
One more story from Jacot shows why features alone don’t drive adoption. When he first offered his physicians an AI ambient scribe, nobody was interested. Then one of them took his daughter to an orthopedic surgeon, watched the scribe capture the visit and came back asking for it. The tool hadn’t changed. His physician had finally seen it solve a problem he recognized.
Moderator Chris Mazzolini said Medical Economics hears a version of this constantly: AI scribes are among the first tools in years that physicians describe as actually taking something off their plate rather than adding to it. That reaction is the signal worth watching for, because when a tool earns it, adoption stops being a change-management exercise.
There’s a design lesson underneath that story. Dropping a tool into an existing workflow and expecting it to work is, as Veradigm’s Tehsin Syed put it on the panel, a failure of design rather than a failure of training. The workflow has to be redesigned around the tool, which takes a conversation between the practice and the vendor rather than a handoff from one to the other.
Put the test to work
Before your next technology decision, write down the problem in one sentence, list the steps the tool removes and the steps it adds, and decide how you’ll know in 90 days whether it worked. If the list of added steps is longer, you have your answer.
Then ask who else the tool touches. Run the same list for the front desk, the medical assistants, and the billing team, because a tool that moves work from one of them to another will look like a win in the room where it was bought and a loss everywhere else.
Watch the full panel on demand for more on how independent practices are choosing tools that pay off.