Discover Why Sites Use Different Workflows

A regional director for a health system asks why every clinic in the system cannot just run the same workflow. You are the key account manager sitting across the table, and the honest answer is that clinics rarely start from the same baseline. Different sites carry different staffing levels, different patient portals, and different internal handoffs, even when they all report up to the same administration. If you treat that variation as an obstacle to talk your way around, you miss the operational detail that actually explains why one site struggles and another does not. Handled well, this conversation turns a director's frustration into a real map of how work happens at each site. Handled poorly, it turns into a lecture about standardization that nobody asked for and nobody believes.

Why This Conversation Goes Wrong

This conversation goes wrong when you agree, out loud or through your body language, that variation is the problem. A director says something like why can't every clinic just use the central workflow, and it is tempting to nod and promise a fix on the spot. That promise puts you in a position you cannot defend later, because you have not yet seen the sites you are promising to align. It also signals to site staff, once word gets back to them, that the account manager thinks they are doing it wrong. Site staff dig in when they feel judged. They stop telling you the real reason a workflow looks different, and you lose the one thing you came to the conversation to get, which is the actual operational detail.

The other common failure is treating the director's complaint as the end of the discussion instead of the start of it. One person's frustration is not evidence of what is happening across the system. It usually comes from a handful of visible failures rather than a full picture of every site. If you build a plan around that frustration without checking it against what site leaders actually do day to day, you end up proposing a fix for a problem you do not fully understand yet.

How To Prepare Before You Ask

Before you sit down with a director or a site leader, pull together what you already know about each site in the system. Note which sites you have visited, which ones you know only through secondhand reports, and which sites tend to get named as the outliers. Walk in with a short, specific set of questions rather than a general request to explain their process.

Three questions do most of the work. Ask which task causes the most rework at that site. Ask who owns that task, since the answer often reveals whether a role is centralized, shared across locations, or handled locally by whoever happens to be available. Ask whether the site follows the system's central policy or has adapted it, and if it has, why that adaptation happened. Write the answers down without editing them into a story yet.

Decide in advance that you will not promise a uniform process or claim that one site's result can be copied elsewhere. Sites differ because of real constraints, staffing ratios, patient volume, rural coverage, portal access, and those constraints do not disappear because a director wants consistency. If you have not gathered this picture across a system yet, a structured set of visits before you propose anything gives you a much stronger foundation than a single meeting. Our post on how to Run a Listening Tour Across Sites in a Health System walks through how to sequence those visits so you hear from sites before anyone commits to a fix.

What To Say When A Director Pushes For One Workflow

Picture a discovery session with a service line director for a health system. The director opens with the complaint you hear in most systems.

"Why can't every clinic just use the central workflow," the director asks.

You do not defend the variation, and you do not agree that it is a failure.

"A common workflow across every site may be the right goal, and I want to understand what gets in the way of it today," you say. "Before we decide what should be standardized, can we hear from one site about its staffing and its portal steps."

The director agrees, and a leader from a rural clinic in the system joins the conversation. The clinic leader explains that one coordinator covers scheduling and intake for three locations, and that person built a shortcut into the portal workflow just to keep up with the volume.

"What would have to change for your coordinator to use the central steps without falling behind," you ask.

"Either a second person, or a faster way to close out records between the three sites," the clinic leader says.

You write that down as a specific constraint, not a complaint, and turn back to the director.

"The workflow difference here comes from staffing coverage, not from anyone ignoring the policy," you say.

That statement does two things. It removes blame from the clinic leader in front of the director, and it turns a vague consistency complaint into a specific resource question the director can actually act on.

Mistakes That Undermine The Discovery

A few habits will wreck this conversation even when your intentions are good.

Promising a single workflow before you have visited more than one site turns you into someone who overpromises, and that reputation follows you into every later conversation with that system. Say instead that you are gathering information and that any standardization decision belongs to the system, not to you.

Comparing sites by name while people from different sites sit in the same room puts staff on the defensive and shuts down honest answers. Keep site level detail in your notes and raise it privately with the person responsible for that site, not in front of a group.

Treating any mention of patient volume as an opening to discuss specific patient information crosses a line you do not need to cross. Keep the conversation about process, staffing, and ownership, and leave individual patient details out of it entirely.

Jumping to a proposed fix after hearing from only one site is another common mistake. One site's staffing constraint might be the exception, not the pattern across the system. Hear from at least two or three sites before you suggest anything to the director, and say so plainly if someone asks you to recommend a fix too early.

How To Practice And Score This Conversation

This conversation is hard to get right the first time you try it live, because the pull to agree with a frustrated director is strong. Practice it before you walk into the room.

Ask a colleague to play two site leaders with conflicting descriptions of the same task, one who follows the central policy closely and one who has adapted it for local reasons. Run the discovery conversation twice, once with each site leader, and check whether you ask the same grounding questions both times or drift into leading questions that hint at the answer you expect to hear.

Afterward, check three things. Did you avoid promising a uniform process or claiming that one site's result would work everywhere. Did you accurately summarize the differences you heard, in language the site leaders themselves would agree describes their situation. Did you name the person in the system who actually has authority to decide on any standardization, rather than assuming that authority belongs to you.

DealSpeak lets you rehearse this exact scenario with an AI counterpart that plays the director and the site leaders, and it scores your discovery questions against these same criteria. If you want more scenarios built around this kind of account complexity, the Pharmaceuticals practice conversations page has other situations built for key account managers working across multiple sites in one system.

Once you have the workflow facts from two or three sites, the next problem is usually a plan that has drifted from those facts because too many meetings piled on new priorities without anyone reconciling them. Our post on how to Reset an Account Plan for a Health System After Unfocused Meetings covers how to pull a plan back to what you actually know.

Where This Leaves Your Account Plan

The account plan you build from this conversation should keep two things separate, the workflow facts you observed at each site and the proposals for future coordination that nobody has agreed to yet. Blur those two categories and you will end up defending a promise you never should have made. Keep them separate and you give the director something more useful than consistency, an accurate picture of why the system works the way it does today.