Run a Listening Tour Across Sites in a Health System

A health system is not one clinic with several addresses. Each site runs its own referral pattern, staffing mix, and workaround for gaps in supply or scheduling. A key account manager who treats one loud site as the voice of the whole system builds a plan on a sample of one, and that plan falls apart the moment a rural clinic points out it looks nothing like downtown. Listening across sites before you propose coordination is not extra diligence. It is the only way to know what you are actually coordinating.

Why this conversation goes wrong

Sponsors and reps naturally lean on whichever site talks the most or sits closest to headquarters. A downtown academic clinic usually has more staff, more free time, and more opinions to share. Rural or satellite sites often stay quiet, not because their workflow runs fine, but because nobody asked them directly, or because raising a problem to a sales rep does not feel like part of their job. When a manager builds an account plan from the loudest site's feedback alone, one of two things happens. The plan proposes changes that do not fit the quieter sites, or it misses the actual workflow problem that is holding back volume system wide. A sponsor loses confidence fast when a plan clearly ignores their smaller sites, and rebuilding that trust costs far more time than the listening tour would have taken up front.

How to prepare

Ask the system sponsor which sites belong in the tour and why certain ones matter right now. A site that just opened, a site with the most volume, or a site that recently changed leadership all deserve a different level of attention than the rest. Settle on a short, fixed set of questions before you visit anyone, so the answers compare directly across sites instead of drifting into whatever each conversation happens to cover. Four questions cover most of what you need. Where does the work slow down. Who owns that step. What resources or tools do people actually use to get it done. What change would make the day easier for the team doing the work. Tell the sponsor and every site contact up front that this is a listening exercise, not a sales pitch, and that you are not collecting patient information. Agree on a timeline with the sponsor too, so the tour has a clear end date instead of dragging on without ever producing anything.

What to say

The conversation usually opens with the sponsor. In a planning call, the sponsor might say something like this. "Our main clinic talks to you every week. I honestly do not know what the smaller sites are dealing with."

You can respond, "I want to use the same short set of questions at every site, then bring the pattern back to your operations team. That way you are comparing sites on the same basis instead of guessing." The sponsor agrees and gives you three site contacts, one from each location that matters most right now.

At the first site, you ask the local coordinator where work slows down. She says supply requests take three days there, not one, because that site orders through a regional office instead of ordering directly. You did not know that gap existed. Downtown never mentioned it, because downtown does not use the regional office at all.

At the second site, you ask the same four questions and get a completely different answer. The nurse manager says supply timing works fine, but new patient scheduling takes twice as long because two systems do not share information with each other. Same questions, two unrelated problems. That gap is exactly what the tour is supposed to surface.

Once the visits are done, bring what you found back to the sponsor in their own words. "Here is what came up at each site. Across three locations, the pattern is scheduling and supply access, not staffing, and it shows up differently at every location." Let the sponsor decide what to do with that instead of prescribing a fix built on one site's view of the problem.

Mistakes to avoid

1. Do not let the loudest site define the whole account. Give quiet sites the same structured questions and the same amount of your time, even when they have less to say at first.
2. Do not turn a staff comment into a clinical claim. Record the workflow language people use. Leave diagnoses, treatment decisions, and patient details out of your notes entirely.
3. Do not skip the sponsor's input on which sites to include. They know which site is expanding, which one just lost a manager, and which one is about to matter more than it does today.
4. Do not hand the sponsor a pile of raw notes. Organize what you heard into themes with the original language attached, so the sponsor can see both the pattern and the source.
5. Do not promise a fix during the site visit itself. You are gathering information at that stage, not negotiating a resolution. Save the proposal for the sponsor conversation that follows.

How to practice and score it

A key account manager can rehearse this entire sequence before ever calling the sponsor. The sponsor scoping call and a site interview are two different conversations with two different tones. One is a scoping discussion with a decision maker who wants to be updated without doing the legwork. The other is a discovery interview with frontline staff who need to trust that their comments will not come back to bite them. A manager scoring a rep on this should check four things. Did the rep ask the sponsor which sites to include and why. Did the rep use the same four questions at every site instead of improvising a new list each time. Did the rep capture actual language rather than turning it into a summary judgment. Did the rep bring back a comparison across sites instead of one site's opinion dressed up as the whole system's feedback.

DealSpeak's Pharmaceuticals practice conversations at Pharmaceuticals practice conversations include scenarios built around exactly this kind of site variation, so a rep can run the sponsor scoping call and a site interview as separate exercises and get scored on each one. Once the tour wraps and the account plan needs to be pulled together without repeating the unfocused meetings that came before, the approach in Reset an Account Plan for a Health System After Unfocused Meetings picks up right where the tour leaves off. And if the visits turn up requests that risk sitting untouched after everyone moves on, Review Unresolved Requests From a Health System Before They Age covers how to keep those from going quiet.

The result

A listening tour takes more calendar time than one good meeting with your favorite site contact. It also produces a plan the sponsor recognizes as accurate, not a proposal built on the loudest voice in the system. That difference is what turns a coordination pitch into something a sponsor actually adopts instead of politely shelving.