Map Governance Before Discussing a Pilot for a Health System

An innovation director at a health system often walks into these meetings with real enthusiasm and no map of how the organization actually approves anything. That enthusiasm can feel like traction, but it is not the same as sponsorship, clinical approval, or privacy clearance. As a key account manager, your job in this conversation is to find out who owns each approval and get the right people talking, without ever suggesting that this meeting settles the timeline.

Why This Conversation Goes Wrong

Innovation directors are often measured on how many promising ideas they bring forward, not on how many pilots actually launch. That incentive pushes them to move fast in conversation, even when the organization behind them moves slowly. When you sit across from someone this eager, the easy path is to match their energy and start talking about start dates. That is the mistake.

A health system pilot usually depends on three separate decisions that rarely sit with one person. Clinical governance reviews whether the pilot affects patient care or workflow. Privacy and security review whether data handling meets the system's requirements. A budget sponsor has to agree to fund or resource the work, even if it is small. If you do not know who holds each of these decisions, you cannot promise a date, and you should say so plainly rather than let vague optimism stand in for a plan.

The risk is not that you say something dishonest. It is that you let a hopeful conversation harden into an expectation. If the director walks out of the meeting believing you have agreed on a timeline, and later hears from three separate committees that nothing has been approved, your credibility takes the hit, not theirs.

How to Prepare Before the Meeting

Before you sit down with the director, find out what you can about how this health system typically approves new programs. Ask your internal team if anyone has worked with this account before, and look for any prior pilots, however small, that show which departments got involved and in what order. If nothing is documented, plan to build the map live, in the meeting.

Prepare a short set of questions you intend to ask no matter how the conversation opens. You want to learn the following.

1. What problem the director wants this pilot to solve, in specific terms.
2. Which committee or role reviews clinical impact, and how often it meets.
3. Who owns privacy and security review, and whether that review runs on a separate track from clinical review.
4. Where budget or resourcing would come from, and whether anyone has agreed to sponsor it yet.

These questions are not a test of the director. They are how the system defines its own gates for you, and how you show that you take the internal process seriously instead of treating it as an obstacle to route around.

Also decide in advance what you are and are not authorized to offer. If your company requires a formal discovery process before any pilot discussion moves forward, know the shape of that process so you can describe it accurately instead of guessing in the room.

What to Say in the Room

The director opens with the version of this conversation you should expect. "This could really help our unit. Can we start next month."

Resist the pull to answer the timing question directly. Instead, redirect to the approval path. "Before we talk about timing, I want to understand what your system needs to approve something like this. Who owns clinical review, who owns privacy review, and where would budget sponsorship come from."

The director admits the picture is incomplete. "Clinical and privacy review are separate processes here, and honestly, no one has agreed to sponsor this yet."

That is useful information, not a setback. Respond by proposing a concrete next step that matches what you just learned. "That is helpful to know. Rather than set a date now, I would like to set up a short discovery session with whoever owns clinical review and whoever owns privacy review, so we understand what each one needs from a pilot like this. Once we know that, we can talk about a realistic sequence."

If the director pushes back and asks for a date anyway, hold the line without sounding rigid. "I do not want to give you a date that falls apart the moment one of these reviews raises a question. A short discovery conversation now will get us to a real date faster than guessing today would."

Notice what this exchange does not include. It never promises a start date. It never treats the director's enthusiasm as equivalent to organizational approval. And it never leaves the director without a next step. You are trading a false timeline for a real one, which is a better trade for both sides.

Mistakes That Undermine the Deal

The most common mistake is agreeing to a soft date just to keep the conversation warm. A soft date has a way of becoming a hard commitment in someone else's notes, and you will spend weeks later walking it back.

A second mistake is treating the director as the only stakeholder who matters because they are the one in the room. Enthusiasm from one champion does not substitute for sponsorship from someone who controls budget or a committee that controls clinical risk. Build the full map even when only one person is talking to you.

A third mistake is asking about governance in a way that sounds like a stall tactic. If your questions come across as bureaucratic hurdles you are throwing up, the director will disengage. Frame every question as something that helps the pilot succeed once it starts, not something that blocks it from starting.

A fourth mistake shows up when you let a health system push for informal terms before any formal process exists. The same discipline, get the real decision path on the table before agreeing to anything, applies just as much when a procurement team tries to move ahead of a formal request for proposal. See how that situation plays out in Handle a Procurement Request Before an RFP Is Issued.

How to Practice and Score This Conversation

Run this scenario with a manager or a peer playing the innovation director, and have them push hard for a date, since that is what will happen in the field. Afterward, do not grade yourself on whether the conversation felt smooth. Grade it on whether you actually surfaced a name or a role for each of the three gates, clinical, privacy, and budget, and whether you proposed a specific next step instead of a vague promise to follow up later.

A manager reviewing the practice session should also check whether you drew the sequence out loud, in what order these reviews typically happen and which ones can run at the same time. A map with unnamed owners is not finished. Keep pushing in practice until every gate has a name attached, or an honest acknowledgment that no name exists yet.

This same discipline, ask questions until the real owners are visible, applies to other pressure moments with this account. If a program complaint comes in later and someone wants a quick answer before the facts are gathered, the same instinct to slow down and map reality first will serve you, as described in Run a Review Based on Facts After a Program Service Complaint. You can rehearse both scenarios, along with others specific to this industry, through Pharmaceuticals practice conversationswhere DealSpeak scores how well you handle the pressure to commit before you have the facts.

A pilot that starts on a real date, backed by a named sponsor and a clear review path, is worth more than one that starts fast and stalls in committee three weeks later. Map the governance first, and let the timeline follow from what you find.