Reduce Meeting Fatigue When Several Teams Need to Participate

Meeting fatigue is often less about your product and more about your company's internal traffic. When a hospital liaison sits through three overlapping calls with your organization in one week, they are not confused about what you sell, they are worn down by how disorganized your side looks. As a key account manager, you often absorb the blame for a scheduling problem you did not create. The fix is not a single meeting that tries to answer everything. The fix is one agenda, built from real questions, owned by the right people, and kept inside a time limit you actually respect.

Why this conversation goes wrong

Meeting fatigue presents itself as a scheduling complaint, but it is almost always a coordination failure inside your own company. Medical affairs books a call, market access books another, and operations wants fifteen minutes to confirm a delivery detail nobody flagged as urgent. Each team has a legitimate reason to talk to the hospital, but nobody on your side checks whether the liaison already answered that question last month. Over time, the liaison stops seeing your company as a partner and starts seeing it as a set of departments that do not talk to each other. That impression outlasts any single answer you gave well on a call.

The trap for a key account manager is agreeing too quickly that everything belongs in one room. That sounds helpful in the moment, but medical and commercial topics do not always belong together, and blending them can make a liaison uneasy about who is actually running the conversation and why. The opposite trap is defending your teams instead of fixing the process. If you tell the liaison that every meeting was necessary, you confirm their suspicion that nothing will change.

How to prepare before you propose one agenda

Before you call the liaison, find out exactly which internal teams have already met with this account and what each one still needs. Talk to your medical, access, and operations counterparts directly and ask each one the same plain question, what decision are you trying to support, and what do you need from the hospital to make that decision. If a team cannot answer that question clearly, their topic probably does not belong on the agenda yet, no matter how much they want a slot.

Write a short list that separates access questions, scientific questions, and operational matters, and put a name next to each one on your side. This list is the real work, and it should happen before you ever propose a meeting time. Send that list to the liaison ahead of the call so they can tell you what to drop, what to add, and what deserves a separate conversation entirely. A liaison who sees this kind of preparation stops treating you as another name on a crowded calendar and starts treating you as the person who filters requests before they reach them.

Decide how long the meeting needs to be and hold that number. Thirty minutes with three clear items beats ninety minutes with a vague purpose and five people waiting for their turn to talk. If a topic needs real depth, it deserves its own call with the right specialist, not five minutes squeezed into a shared session where nobody gets a full answer. A similar sequencing problem shows up when a new site comes on board, and Plan a New Clinic Site's Program Onboarding walks through how to order early conversations so no single team crowds out the others.

What to say

The liaison opens with the frustration you expected. "Why can't your company organize itself. I had your medical team on the phone Tuesday, and now operations wants another hour on Thursday for something that sounds like the same topic."

You answer without defending the past. "That is fair, and I will fix it. I am going to contact each team today, find out exactly what they still need from you, and come back with one agenda that has a time limit on every item. You will see the whole thing before you agree to anything."

The liaison pushes for specifics. "How long will this take, and who actually shows up on the call." You say, "I need two days to confirm the list with my teams. The meeting itself will run thirty minutes, and I will only bring someone into the room if their question has not already been answered somewhere else."

The liaison agrees to the terms. "Thirty minutes, one agenda, no repeat questions. Send it to me by Friday and I will review it before we get on the call."

Mistakes to avoid

1. Promising that one meeting will replace every future conversation. Some topics require a private discussion between your medical team and the liaison's clinical staff, and forcing that into a commercial meeting can compromise the separation those roles are supposed to maintain.
2. Building the agenda from what your internal teams want to say rather than what the liaison needs to decide. An item that exists only because a team wants time in front of the account does not belong on the list, and the liaison will notice when a topic has no clear purpose.
3. Skipping the written agenda and hoping the meeting will sort itself out once everyone is on the call. Without a document sent in advance, the liaison arrives unsure what to expect, and the conversation drifts into whatever the loudest person on your side wants to cover.
4. Setting a time limit and then ignoring it once the meeting starts. If you commit to thirty minutes, stop at thirty minutes, even if that means scheduling a short second call for whatever did not fit.
5. Letting an internal team override the agenda after the liaison already reviewed it. If access or operations adds a new item the morning of the call, tell them it waits for the next session, not the current one.

How to practice and score this conversation

A manager can coach a key account manager on this exact scenario by having them run through the call before it happens, not after a real meeting goes badly. Rehearsing the opening response, the one where the liaison challenges your company's organization, matters more than rehearsing the agenda itself, because that first response decides whether the liaison trusts the rest of the plan.

Score the practice run on three specific things. Check whether the account manager named a concrete number of teams and questions rather than promising vague coordination. Check whether they committed to a real deadline for sending the agenda instead of leaving it open ended. Check whether they resisted adding a topic to the agenda just because the liaison mentioned it in passing, without first confirming it maps to a decision the liaison is actually trying to make.

You can run this scenario, along with other account conversations specific to this industry, in DealSpeak, where an AI counterpart plays the liaison and reacts to whatever agenda you propose in real time. The Pharmaceuticals practice conversations library includes this scenario next to related ones, including Map Governance Before Discussing a Pilot for a Health Systemwhich covers a similar coordination problem earlier in a relationship, before a pilot is even on the table. Practicing the call before the real one lets you find the weak spots in your agenda while the stakes are still low.

Close

Meeting fatigue is a signal that your internal teams are not talking to each other, not a sign that the liaison is impatient or difficult. Fix the coordination problem and the fatigue disappears on its own. One agenda, clear owners, a real time limit, and a complaint turns into a reason the liaison trusts you more than before.