Preparing an Executive Review of Open Device Service Issues

An executive review of open device service issues can go one of two ways. You walk in with a clear record of every case, or you walk in with vague status labels and hope nobody asks a hard question. Executives ask hard questions. If you manage a strategic account in medical devices, this review is one of the highest stakes conversations you have, because leadership is deciding whether they trust your account team's account of reality.

Why This Conversation Goes Wrong

Most account teams walk into an executive review with a status column that says in progress next to every open case. That label covers wildly different situations. It might mean the service engineer finished the repair and is waiting for the customer to confirm an install date. It might mean nobody has touched the case in three weeks. When an executive cannot tell the difference, they assume the worst. They start to wonder what else the label is hiding.

The instinct to protect the account often makes this worse. An account manager who feels pressure to show progress will round up. Two open cases become almost resolved. A pending access request becomes just a scheduling detail. None of that is a lie exactly, but it is not the truth either, and executives who sit through enough of these reviews learn to read between the lines. Once they suspect you are managing the message instead of reporting the facts, every future review starts from a position of doubt.

How to Prepare Before the Review

Preparation starts with the service record itself, not with a slide deck. Pull the current status on every open case and confirm it against what the assigned technician or service engineer actually reports, not what was logged three updates ago. For each case, write down four things. The name of the owner accountable for the next action. The work that has already been completed and verified. The action still pending. The date you expect the next update.

Sort the open cases into two groups. The first group is work your team owns and controls. The second group is work that depends on the customer, an access date to a lab or floor, a signature, a scheduling window, information from the site. Say plainly which cases sit in the second group. Do not soften it and do not blame the customer for it. A hospital that needs three weeks to schedule access to a restricted area is not being difficult, it is operating under its own constraints, and your job is to report that constraint accurately, not to make it disappear from the record.

If your organization has never agreed on what a healthy open case count looks like, or nobody set a baseline for what good service performance means for this account, that gap will surface in this exact meeting. Read Running a Value Review When No Baseline Was Set before you walk in, because the same problem, an executive asking a question your team never prepared an answer for, shows up in both conversations.

What to Say When You're Challenged

The chief operating officer looks at the case list and asks, are you hiding unresolved failures from us. This is the moment the whole preparation exercise was for.

You say, no, I am going to walk through the verified case record, case by case. Two cases remain open because service needs an access date from the site, and the assigned team has already documented the request in writing. For every case I will show you the work completed, the customer coordination still pending, and who owns the next step.

The chief operating officer pushes further and asks, why has case fourteen been open for five weeks. You answer, service completed the diagnostic and ordered the replacement part on day three. The part arrived on day twelve. Since then we have been waiting on the customer's biomedical engineering group to confirm an install window, and I followed up on day twenty and day thirty one. The next follow up is scheduled for this Thursday, and if we do not get a date by then, our director of service will call the site director directly.

That answer works because it names the record, the dependency, and the next accountable action, every time. It also gives the executive something to act on. They might decide to call the site themselves, or push the review cadence, or ask a different operations leader to get involved. That is their decision to make once they have real information, not yours to make for them by hiding the case behind a vague label.

Mistakes That Undermine the Review

A few habits will cost you credibility faster than anything else in this meeting.

First, do not use status labels that hide more than they reveal. In progress, pending, under review, these tell an executive nothing about who owns the next step or when it will happen.

Second, do not blame the customer for a delay you have not documented. If you say the customer is slow without dates, names, and a record of your own follow up, it sounds like an excuse, and it probably is one.

Third, do not present a case as closed when a customer dependent step is still open. Executives find out fast when a supposedly resolved case reopens two weeks later, and that discovery costs you more trust than the open case ever would have.

Fourth, do not walk in without a next action for every single case. An open case with no owner and no date is the single fastest way to lose the room, because it tells the executive that nobody is actually driving the work.

Fifth, do not get defensive when someone asks a pointed question. The question is not an attack on you, it is the executive doing their job. Answer it the same way you would answer a friendly question, with the record.

How to Practice and Score This Skill

You cannot build this habit by reading about it once. Pick one open case and practice presenting it out loud in sixty seconds, using only facts you can point to in the service record. Ask your manager, or a peer who plays the executive, to interrupt you mid sentence with a challenge question, the same way a real chief operating officer would. Then check your own answer against three things. Did you name the record you are drawing from. Did you name the dependency accurately, without blame and without vague language. Did you name the next accountable action and a date.

If a case is stalled for reasons tied to a capital purchase still moving through committee rather than a service issue, that is a different conversation with its own pressure points, and Keeping a Capital Evaluation Moving Across a Budget Cycle covers how to keep that one on track.

DealSpeak lets you rehearse the full executive review, including the tough follow up questions, against an AI counterpart built for this exact scenario. Its Medical Devices practice conversations let you run this scenario as many times as you need until the answer comes out clean under pressure, not just when you have had time to prepare a script.

The goal of this review is not to make every case look resolved. It is to give leadership a record they can trust and a clear view of what needs their help. Get that right and the hard questions stop feeling like attacks.