Stakeholder Management in Salesforce Programmes: The Hard Truths

The Stakeholder Problem Nobody Talks About

Salesforce programme post-mortems are full of technical explanations: the data migration was harder than expected, the integration took longer, the requirements changed mid-sprint. These are real — but they are rarely the root cause. The root cause is almost always that the right people were not sufficiently engaged at the right time, and when the programme hit a difficult moment, there was nobody with the authority and will to unblock it.

Stakeholder management in Salesforce programmes has three components that are often conflated. Stakeholder identification — knowing who has influence over the programme, even if they are not formally on the governance structure. Stakeholder engagement — the ongoing work of keeping the right people informed, consulted, and invested. Stakeholder alignment — the deliberate effort to resolve conflicts between stakeholders before those conflicts derail delivery.

Most programmes do a reasonable job of identification. They struggle with engagement — particularly as the programme progresses past initial excitement into the messy middle. They almost universally underinvest in alignment — treating stakeholder conflicts as communication problems when they are actually interest conflicts that require negotiation.

The Four Stakeholder Archetypes

In practice, stakeholders in Salesforce programmes fall into four archetypes. Understanding which archetype you are dealing with determines how you engage.

The Champion has a personal stake in the programme's success — often because their team's effectiveness is directly tied to the outcome. Champions will advocate internally, unlock budget, and escalate blockers on your behalf. They are your most valuable stakeholders. Invest time in keeping them informed, successful, and visible. Their credibility rises and falls with the programme's performance.

The Reluctant Participant has been told to engage but does not see personal benefit in the programme. They will attend meetings, provide cursory approvals, and disengage when anything competes for their time. The mistake is treating them as engaged because they are present. Reluctant participants need to be given a stake — a visible win, a problem the programme will solve for them specifically, or a consequence of non-engagement that is made explicit.

The Active Resistor is working against the programme — sometimes overtly, more often through delay, objection, or selective withholding of information. Active resistance usually has a reason: the programme threatens their team's scope, their budget, their headcount, or their personal relationships with displaced vendors. The response is not escalation (which makes them more resistant) but understanding and, where possible, addressing the underlying concern.

The Passive Bystander is neither for nor against the programme. They have influence but are not exercising it. In a healthy programme, bystanders are fine. In a programme under political pressure, bystanders who could have defended the programme do not — and their silence is interpreted as withdrawal of support. Engage bystanders with specific, low-effort asks: a brief endorsement at an all-hands, a review of an output, a quote for a communication. Small investment, meaningful insurance.

The Five Resistance Patterns

Stakeholder resistance is not monolithic. The response that works for one pattern will backfire on another.

Scope resistance — "This is bigger/more complex than we agreed." Often legitimate. The response is either to demonstrate that the scope is correct and was understood, or to acknowledge scope creep honestly and re-baseline. Defending original scope when it has genuinely changed destroys credibility.

Prioritisation resistance — "We have bigger priorities right now." A signal that the programme has lost competitive position in the stakeholder's agenda. The response is to make the cost of delay explicit: what business outcome is deferred by every month of delay? Vague urgency does not work — specific financial or operational impact does.

Process resistance — "We don't want to change how we work." The most common and most underestimated form of resistance. Technology is rarely the obstacle; process change is. Involve the resistant teams in process design early. Process change imposed on people will be quietly circumvented; process change co-designed will be adopted.

Trust resistance — "We don't believe the programme will deliver." Often the residue of a previous failed technology programme. The response is demonstration, not assertion. Deliver something small and visible early. Show working software to real users. Trust is rebuilt through evidence, not promises.

Political resistance — "This programme benefits Department A at Department B's expense." The hardest to address directly because it cannot be acknowledged openly. The response is to design benefits that are visible for all affected departments, involve resistant teams in decision-making, and use the sponsor's authority to set expectations about acceptable political behaviour.

Sponsor Engagement: What It Actually Requires

Programme sponsors in Salesforce programmes are often senior enough to provide political cover but busy enough to be perpetually unavailable. The delivery team's job is to make sponsorship as easy and effective as possible — not to depend on sponsors to be proactively engaged.

The sponsor engagement model that works: a one-page programme dashboard delivered weekly (never more than one page — if you need more, you are reporting, not communicating), a 30-minute monthly conversation (not a status meeting — a decisions meeting: here are the three decisions we need you to make or endorse this month), and a pre-agreed escalation protocol (you define the categories of decision that require sponsor involvement; the sponsor pre-commits to a response time).

Sponsor disengagement is a programme risk, not a communication failure. When a sponsor starts cancelling the monthly meeting, delegating to a junior representative, or taking longer than pre-agreed to respond to escalations, document it as a risk. Have the conversation directly: "I need to understand your availability over the next quarter — here are the decisions I'll need you involved in." This is not confrontational; it is professional risk management.

Early Warning Signals and the Stakeholder Health Score

Programmes rarely collapse suddenly. They degrade over time, and the degradation is visible in stakeholder behaviour if you know what to look for.

Maintain a simple stakeholder health score — not a sophisticated RAG model, just a weekly assessment of four signals for each key stakeholder: attendance at programme governance, responsiveness to requests, tone in communications (escalating or settled), and action follow-through. When two or more signals are amber for the same stakeholder for two or more weeks, intervene directly.

The intervention should be a private conversation, not a formal escalation. "I've noticed you've been less available over the past few weeks. I want to understand if there's something about the programme direction I should know." This conversation surfaces concerns before they become programme-threatening problems. Most stakeholders who are disengaging are doing so because of a specific concern that they haven't raised formally. Give them a safe channel to raise it.