You have a one-pager. You have an executive sponsor on the calendar. The 30 minutes you're about to spend with them will determine whether this initiative gets funded or quietly dies. Most data leaders get this meeting wrong in predictable ways. This is how to get it right.
Send the one-pager 48 hours in advance. Not the morning of. Not in the meeting. Two days before. Executives skim documents in the margins of their day, and the ones who matter will read it before walking in. If you send it five minutes before the meeting, they'll read it during the meeting, which means you'll spend the first ten minutes watching them read instead of talking to them.
Send it without preamble. Three sentences max: "Attaching the one-pager for our Thursday meeting. The decision I'd like to walk away with is whether you're willing to sponsor this. Let me know if anything stands out before we meet." That's the email. No deck attached. No softening.
Decide what you're actually asking for. Most data leaders walk into the sponsor meeting with a vague ask: "support," "buy-in," "alignment." Those are not decisions an executive can make. Walk in with a specific ask: "I'm asking you to be the named executive sponsor of this work. That means you'll review progress quarterly, defend the budget through the planning cycle, and make the call when there's organizational resistance I can't resolve. Are you willing to commit to that?" The specificity is the favor you're doing them.
Don't walk through the one-pager. They've already read it. Walking through it tells them you don't trust them to have read it, and burns the first ten minutes on material they already know. Open by referencing it: "You've seen the one-pager. I want to spend our time on the parts that probably need the most discussion."
Spend most of the meeting on Consequences and Results. The current state and future state quadrants are descriptive. The consequences and results quadrants are where the decision lives.
The Consequences quadrant is where the executive decides whether the cost of inaction is real. If they push back here, "I don't think the margin erosion is that severe" or "we have other initiatives addressing customer retention," that's the conversation worth having, because it tells you whether they actually believe the problem is urgent. If you can't defend the consequences, you don't have sponsor commitment, you have polite acknowledgment.
The Results quadrant is where the executive decides whether they'll be on the hook for outcomes. If they want to negotiate the numbers down, let them. A sponsor who has personally agreed to a slightly smaller number is worth more than a sponsor who nominally agreed to a larger one. The point is to get to a set of numbers they'll defend in a board meeting.
Name the business champion. The executive sponsor cannot be the business champion. Different role, different person. Before you leave the meeting, you need a name. "I think this work needs a business champion, the operating leader whose performance review reflects whether the use case delivers. My read is that this is [X]. Would you be willing to ask them to take this on?" That's the second commitment you're getting in this meeting, and it's almost as important as the first.
Get to specifics on the next 90 days. "If you say yes today, here's what happens next: I'll work with [business champion] to scope the first use case in detail, we'll come back to you in 30 days with a delivery plan, and I'll need you to make the budget commitment in the planning cycle that closes in [date]. Is that timeline workable?" If they hedge here, the commitment isn't real. If they engage with the timeline, you have a sponsor.
"This sounds expensive. What's it going to cost?"
The one-pager doesn't have a price because the price isn't the decision in this meeting. The decision is whether the work is worth doing. The price comes after the use case is scoped. Say: "I'm not asking you to commit to a budget today. I'm asking you to commit to sponsoring the work. The budget conversation comes after we've scoped the first use case, which we'll do in the next 30 days. The order matters."
"Why can't we do this with the data team we already have?"
This is a fair question. The honest answer is usually: "We can do parts of it with the team we have. What we can't do internally is [the specific gap: operating model design, executive-level facilitation, third-party credibility with the business]. I'm not asking for a replacement; I'm asking for a partner on the parts we can't do alone." If you don't have a clear answer to this question, the sponsor will assume you don't have one, and they'll be right.
"I'm supportive, but I'm not sure I'm the right sponsor."
This is a soft no. Don't accept it as a yes. Push: "If not you, then who? The work needs sponsorship at the executive level. If you don't think you're the right person, I'd value your help identifying who is." Sometimes this surfaces the real sponsor; sometimes it surfaces that no executive is willing to own this, which is information you need before investing further.
"Let's do a smaller pilot first."
Pilots are sometimes the right answer and sometimes the way executives kill initiatives without saying no. Test it: "A pilot is fine if we're aligned on what success looks like and what we'd do next. What would the pilot need to show for you to commit to the broader program?" If they can answer that question, the pilot is real. If they can't, you've identified that the sponsor isn't actually committed.
"Send me a deck."
This is the most dangerous response. The executive is asking you to convert a decision-quality artifact into a proposal-quality artifact, which means the decision is being deferred. Push back gently: "I can build a deck if it's useful, but my read is that the one-pager has the substance. What's the specific question the deck would answer that we should discuss now?"
Send a written confirmation within 24 hours. Three lines: "Confirming the sponsorship commitment from yesterday. You agreed to [the specific role], the business champion will be [name], and we'll come back to you in 30 days with a scoped use case and budget. Let me know if I have any of that wrong." This document is the sponsor's commitment, and putting it in writing is what makes it real.
Move immediately on the business champion. A sponsor commitment without a champion is a clock running. The sponsor will lose interest if nothing visible happens in 30 days, and the longest part of the next 30 days is usually getting the business champion engaged. Don't wait. The day after the sponsor meeting, request the meeting with the champion.
If the meeting didn't produce a commitment, don't try again with the same one-pager. A one-pager that didn't land in the sponsor meeting will not land harder the second time. Either the diagnosis was wrong, the framing was wrong, or the sponsor isn't the right sponsor. Take a week to figure out which, then come back with a different artifact, a different framing, or a different sponsor.
This is a meeting design for converting a champion's relationship with their executive into a real sponsor commitment. It is not a sales meeting, and the executive is not a buyer. They are an internal stakeholder being asked to take on a real responsibility, and the meeting works to the extent that you treat it that way.
If you are doing this well, the conversation about XenoDATA, about whether to bring in outside help, about what we cost, does not happen in this meeting. It happens after. Once the sponsor has committed and the business champion is engaged, the question of how to deliver the work is the next conversation. We're worth talking to at that point because the work is worth doing. The work is worth doing because three people are now on the hook for it.
That sequence is the only one that produces engagements that survive past kickoff. Get the sponsor first. Get the champion second. Talk to us third.
Don't have your one-pager yet?
Build it before the meetingOr book a workshop instead → Data Leader Workshop / Executive Workshop
30 minutes · No prep required · No commitment
Not ready to book? Take the Initiative Health Check first →
5 questions · ~2 minutes · No email required
