Stakeholders, Champions and Sponsors

Topics Covered

Mapping the Stakeholders

Who counts as a stakeholder

Why mapping matters

Influence and interest

Roles in the decision

Building the map

Stakeholders on the vendor side

Attitudes toward the deployment

What each stakeholder wants

Hidden stakeholders

Stakeholders who change

Keeping the map private

Using the map weekly

Maps for large organisations

A worked map

Questions that reveal stakeholders

Mapping groups as well as people

Mapping across the lifecycle

Common mapping mistakes

Sharing a clean version

Starting the map on day one

Deployments succeed or fail through people as much as through code. A forward deployed engineer works with sponsors who fund the work, champions who push it forward, users who adopt it and many others who can help or block. This lesson explains how to map these people, work with sponsors, grow champions, handle sceptics and keep relationships healthy over a long deployment.

Who counts as a stakeholder

A stakeholder is anyone who affects the deployment or is affected by it. That includes the sponsor, the users, their managers, data owners, IT and security teams, procurement, legal and sometimes unions or works councils. It also includes people on the vendor side, such as the account executive and product managers. The list is usually longer than it first appears.

Why mapping matters

Without a map, FDEs spend time with whoever is friendly and available, which is rarely the full set of people who matter. A map shows who decides, who influences, who uses and who can block. It reveals gaps, such as a security lead nobody has met, before those gaps turn into surprise objections near launch.

Influence and interest

A simple map places each stakeholder on two axes: influence over the deployment and interest in it. High influence and high interest people, such as the sponsor, need close engagement. High influence but low interest people, such as a chief information officer, need to be kept satisfied with brief updates. Low influence but high interest people, such as users, need to be kept informed and involved.

Roles in the decision

Another useful view is the role each person plays in decisions. Common roles are decision maker, approver, influencer, user and gatekeeper. The decision maker chooses, approvers can veto, influencers shape opinions, users live with the result and gatekeepers control access to people or systems. One person may hold several roles at once.

Building the map

Build the map from discovery interviews, organisation charts and conversations with the account team. Ask each person who else you should talk to and who will have opinions about the result. Note reporting lines, but do not rely on them alone, because informal influence often matters more than titles. A respected senior planner may sway the team more than their manager.

Stakeholders on the vendor side

Map the vendor side too. The account executive owns the commercial relationship, the customer success manager may own long term health, product managers decide what features arrive and support teams handle tickets. Knowing who on your own side needs updates prevents mixed messages to the customer and helps you find help when you need it.

Attitudes toward the deployment

Record each stakeholder attitude: supporter, neutral, sceptic or opponent. Attitudes change over time, so update them as you learn more. A neutral data owner may become a supporter after a good meeting, or a sceptic after a data incident. Tracking attitudes helps you decide where to spend relationship effort each week.

What each stakeholder wants

For each stakeholder, write down what they want from the deployment and what they fear. The sponsor may want a result to report to the board and fear public failure. A planner may want less overtime and fear being replaced. A security lead may want no incidents and fear new data flows. Knowing these wants and fears shapes every conversation.

A stakeholder map shows who decides, who influences, who uses and who can block, and how their attitudes change over time.

Hidden stakeholders

Some stakeholders only appear late: an internal audit team, a regional director in another country or a union representative. Ask early whether anyone must be consulted before a system like this goes live. Asking the question costs little, while discovering a hidden approver a week before launch can delay the deployment by months.

Stakeholders who change

People move roles, leave companies and join new teams. Expect at least one important stakeholder to change during a long deployment. Keep the map current, and when someone new arrives, meet them early and walk them through the deployment. Treat every new stakeholder as someone whose support you must earn, not as someone who inherited it.

Keeping the map private

A stakeholder map contains opinions about people, such as who is sceptical or who holds informal influence. Keep it within the vendor team and write it respectfully, as if the people described might read it one day. Never share it with the customer in raw form. Its purpose is to guide your engagement, not to judge individuals.

Using the map weekly

Review the map each week. Ask which stakeholders you have not spoken to recently, whose attitude has changed and whether any new names have appeared. Plan the coming week of conversations from that review. A few minutes of review keeps relationship work deliberate rather than reactive, and it often prevents surprises.

Maps for large organisations

In very large customers, one map may not be enough. Build a summary map for the overall deployment and detailed maps for each site or business unit. Each regional team may have its own sponsor, champion and sceptics. Treating a global customer as one homogeneous group misses the local dynamics that decide whether each rollout succeeds.

A worked map

Consider a deployment that gives warehouse planners a daily plan. The operations director is the sponsor and decides scope. The head of IT security approves new data flows. The warehouse systems manager is a gatekeeper for data access. A senior planner with fifteen years of experience is an informal influencer. Twenty planners are users, and their shift leads are managers. Procurement approves any extra licences, and the account executive and a product manager sit on the vendor side. Written out like this, the map already shows that security and the systems manager need early meetings, even though neither will use the system.

Questions that reveal stakeholders

A few questions reliably reveal stakeholders during discovery. Who will notice if this system breaks? Who approved the last system like this? Who would be upset if they heard about this project second hand? Whose budget pays for the users time during training? Each question points to people that an organisation chart alone would miss, and the answers often surprise even the sponsor.

Mapping groups as well as people

Some stakeholders are groups rather than individuals: a works council, a regional team or a user community. Map groups with a named contact where possible, and note how the group makes decisions. A works council may need formal consultation weeks in advance, while a user community may respond to a lunchtime demo. Treating groups as if they were single people leads to missed steps.

Mapping across the lifecycle

Stakeholders matter at different moments. Security matters most before launch, procurement at contract changes, users during rollout and the finance team near renewal. Add a note to the map about when each stakeholder becomes critical. This helps plan contact ahead of time, so you build the relationship before you need a decision rather than asking a stranger for approval.

Common mapping mistakes

Common mistakes include mapping only the customer side, treating titles as influence, ignoring people who will lose something from the change and never updating the map after kickoff. Another is mapping only supporters, because they are pleasant to meet. A good map is complete and honest, including the people who are likely to be difficult.

Sharing a clean version

While the full map stays private, a clean version listing names, roles and responsibilities is useful to share with the customer project lead. It confirms who is involved, catches missing people and helps the customer coordinate their own side.

Starting the map on day one

Start the map on the first day, even with only a few names. An early rough map is far more useful than a perfect one built after the important meetings have already happened.

Map who decides, influences, uses and blocks

List every stakeholder on both sides, place them by influence and interest, name their role in decisions and record their attitude, wants and fears. Keep the map private and respectful, review it weekly and ask early about hidden approvers who must be consulted before launch.