Map Executive Sponsors Before a Transformation Discovery Call

A transformation inquiry sounds well sponsored when one executive sends the first message. The business development director still needs to learn who authorizes work, who lives with operating changes, and who owns the facts behind the problem. A sponsor map keeps a discovery call from becoming a presentation for people unable to move a decision forward. More importantly, the map exposes missing voices before a proposal assumes agreement where none exists.

Start by asking what decision is pending. The question needs a real answer. “We want transformation” describes ambition. “Our executive team must decide whether to fund a diagnostic before the annual plan closes” describes a decision. Ask who approves the diagnostic effort, when they meet, and what evidence they expect before agreeing. A decision path often includes a chief executive, finance lead, operating president, board committee, or regional leader. Write names beside roles. Titles alone hide too much.

Then ask who owns the present process. The person with approval authority often lacks direct knowledge of where work stalls. A customer leader knows where promises break. A finance leader knows when spending pressures appear. An operations leader sees handoffs, staffing gaps, and service failures. A technology leader knows system limits and planned changes. Their perspectives need not match. Your job in early discovery involves finding the disagreement and giving the decision group a way to hear each view.

In a fictional call, chief of staff Lena says, “Our CEO wants a transformation partner. Send a proposal this week.” Director Marcus replies, “I will prepare useful questions, and first I need to understand the decision path. Who decides whether to begin, and which leaders own the customer, financial, and operating information?” Lena says the CEO, CFO, and operations president decide together, although the operations president has not seen the request. Marcus says, “Let us hold a short sponsor session with those leaders. We will identify the decision, the evidence they need, and who should join a later diagnosis.”

Draw the first map on a single page. Use one area for decision authority, one for operating knowledge, and one for people affected by a change. Add a fourth area for influence when an executive, advisor, or board member shapes the choice without signing approval. Put each person in every area where their role belongs. A finance executive often approves funding and influences priorities. A service manager often holds operating knowledge and represents an affected team. The multiple placements reveal connections a simple organization chart misses.

Beside each name, write the specific contribution needed. “CFO” tells you little. “CFO brings the funding question and timing assumptions” tells a meeting leader what to request. “Operations president confirms where service work stops” gives a different purpose. “Customer leader describes promises already made” identifies evidence for the decision. If you cannot write a contribution, ask whether the person needs to attend or whether another owner holds the relevant facts.

The map should include blank spaces. A blank space signals a question, not a mistake. If no one owns the customer impact, ask Lena who receives complaints or tracks missed commitments. If no one owns the data behind a cost claim, ask who prepared the figure. If affected frontline staff have no path into the diagnosis, ask the operating leader how their experience will enter the work. Early questions prevent a sponsor group from approving an effort built on untested assumptions.

Different leaders often define success differently. The CEO often seeks a growth path. The operations president often needs reliable delivery before accepting more demand. The CFO often wants a clearer view of cash and staffing commitments. Do not flatten these views into a slogan. Ask each person, “What result would make this effort worth the disruption?” Then ask, “What risk would make you hesitate?” Their answers describe the decision criteria. They also show where a future team needs evidence instead of opinion.

In the fictional sponsor session, Marcus opens with a simple statement. “We are here to define the choice before discussing a solution.” The CEO says the firm needs capacity for a major account. The operations president says service delays have already reached a level staff cannot absorb. The CFO says no investment decision will move without a credible cost range. Marcus writes each concern beside the owner. He asks, “Which fact would help you decide whether a diagnostic is worth funding?” The CEO asks for a view of account demand. The operations president asks for a map of current handoffs. The CFO asks who owns the cost baseline.

Marcus notices an important gap. Nobody in the room owns the account demand data. Lena says the commercial vice president has the forecast but was not invited. Marcus does not invent a number or propose a solution. He asks Lena to request a short input from the commercial vice president and names the exact question: “What committed demand, expected timing, and customer obligations should the sponsor group use when deciding whether to start a diagnostic?” A precise request reduces delay and avoids a broad plea for more information.

Keep the early session short. A forty five minute sponsor meeting has enough room for the pending decision, decision criteria, required evidence, missing owners, and a next meeting owner. Do not fill the time with credentials. A few approved examples establish relevance, yet the meeting exists to qualify the work. If a leader asks for a proposal before the map is complete, explain what remains unknown. “We have not heard from the operations president about service limits, and no one has confirmed the demand source. A proposal now would guess at the work you need.”

After the session, send a factual decision note. State the decision being considered, the leaders who took part, the evidence each leader requested, and the owner of every next action. Do not report agreement where the group only agreed to gather facts. If the CEO favors speed and the operations president favors stabilization, record both views. The note gives the sponsor group a common record and reduces the chance of a different later recollection.

Use the map to set the next discovery boundary. If the sponsor group wants to decide whether a diagnostic is justified, the next step might involve interviews with service leaders and a review of current demand material. If they already agree on the problem but lack a delivery route, the next step might focus on process ownership and dependencies. Say what the early work will answer and what stays outside scope until leaders approve another decision. This protects both sides from a vague engagement.

Practice with a fictional request. Ask a colleague to play Lena and press for a proposal by Friday. Draw four areas on a sheet: approval, operating facts, affected people, and influence. As your colleague speaks, add the CEO, CFO, operations president, and commercial vice president. Leave the demand source blank until Lena names an owner. End the practice by handing Lena a short decision note. On the last line, write: “Lena will ask the commercial vice president to bring the account demand forecast to Tuesday’s sponsor session.”