Projects do not become difficult because they involve people. People are the project: they define the problem, carry risk, make trade-offs, operate the result and experience its consequences.
Alignment in a large organisation does not mean universal enthusiasm. It means the relevant people understand the intended outcome, the decision process, their responsibilities and the trade-offs that have been made. A disagreement can remain while the programme moves responsibly. Hidden disagreement tends to return when change becomes costly.
Identify who has a stake
Begin with the groups affected by the decision, not only the names invited to kick-off. These may include:
- the accountable sponsor and budget holder;
- the delivery and operational teams;
- technology, data, security and risk specialists;
- marketing, sales or client-service teams;
- senior leaders with formal decision rights;
- influential partners or colleagues without formal authority;
- suppliers and implementation partners;
- clients, members, customers or other end users;
- people who may be excluded or disadvantaged by the change.
For each, record the outcome they need, contribution, authority, impact, current position and preferred way to engage. Avoid labelling people as “resistant” before understanding the consequence they see.
Formal organisation charts reveal only part of the system. An executive assistant, experienced practitioner or service-desk lead may shape adoption without appearing in governance. Stakeholder analysis should surface influence and knowledge as well as rank.
Agree the purpose before the feature list
State the business, client or operational problem and the outcome the programme is meant to create. Connect it to an agreed organisational priority and show the evidence for the need.
Keep the statement specific enough to guide trade-offs. “Modernise the experience” will support almost any proposal. “Reduce repeated information during client onboarding while maintaining conflict, identity and records controls” provides a decision boundary.
Define success measures, baseline, guardrails and benefit owner. Some measures will remain uncertain during discovery. Record what must be learned rather than filling the gap with an arbitrary target.
Ask key stakeholders separately to describe the purpose. Differences are useful diagnostic evidence. Resolve material contradictions before asking a supplier or delivery team to turn them into scope.
Map journeys and backstage work
Customer and colleague journeys reveal where objectives collide. Follow an important task from beginning to end, including internal handoffs, approvals, data movement, exceptions and support.
Marketing may administer content while technology controls releases. A client team may promise responsiveness while a risk process imposes necessary checks. Neither perspective is inherently wrong. The project must design the service that connects them.
Use a service blueprint or process map to show customer actions, frontstage contact, backstage work, systems, policies and visible evidence. Include the people who do the work. They often know which formal process is bypassed and why.
Do not treat every workaround as bad behaviour. It may expose an unmet need, an inaccessible path or an impractical control. Decide whether to redesign, govern or remove it based on consequence.
Make decision rights visible
Stakeholder engagement cannot substitute for governance. Write down who recommends, who decides, who must be consulted and who must be informed for the programme’s material choices.
Typical decisions include outcome, scope, architecture, risk acceptance, budget, service policy, launch and stop conditions. The right owner varies. A steering committee cannot approve a legal interpretation merely because all members agree; accountable specialists need their proper role.
Set thresholds and escalation routes. Identify the latest safe decision date so a delayed choice has an explicit effect on cost, scope or time.
Publish decisions with rationale, conditions and dissent. This is more durable than saying everybody was “on board” after a meeting in which nobody challenged the sponsor.
Engage people according to purpose
Different groups need different involvement.
Co-design with people whose work or experience is being changed. Consult specialists whose knowledge shapes the decision. Brief wider stakeholders with enough context to understand impact. Give affected people a route to question or correct the plan.
Avoid inviting a broad group to every workshop as a substitute for planning. It consumes time and can make accountability less clear. Equally, a broadcast email is inadequate for somebody expected to adopt a substantially different service.
Choose accessible formats, times and channels. Provide material early, explain unfamiliar language and allow considered written input as well as live discussion. Participation quality matters more than attendance count.
Close the feedback loop. Tell people what was heard, what changed and why some requests were declined. Consultation without a visible response teaches people that participation is theatre.
Name the trade-offs
On meaningful projects, priorities conflict. A faster launch may reduce scope. Stronger control may add effort. A shared platform may limit local variation. Increased personalisation may require data people do not want to provide.
Put these choices into the decision record. Describe who bears the cost and which mitigation is available. Real alignment means people can see the bargain even when it is not their preferred one.
Do not aim for silence. Constructive challenge can reveal a dependency or duty the core team missed. Sponsors should ask for contrary evidence before declaring a position and protect people who raise material concerns.
When consensus is impossible, use the agreed authority. Deferral should be a decision with a consequence and deadline, not an escape from discomfort.
Keep alignment current
The environment changes during delivery. New evidence, staff changes, supplier constraints or client needs can make an earlier agreement obsolete.
Review stakeholders and assumptions at phase boundaries and before irreversible choices. Watch for delayed decisions, low participation, repeated rework, informal workarounds and conflicting messages from leaders. These are signals to investigate, rather than proof that people oppose the programme.
Measure understanding and operating readiness as well as sentiment. Can colleagues explain the purpose, perform the changed task, obtain support and identify the accountable owner? Positive survey responses alone do not establish that the service will work.
At transition, move stakeholder ownership into the enduring service. A project communication plan cannot carry adoption indefinitely.
A practical starting exercise
Ask each key stakeholder three questions separately:
- What outcome must this programme create?
- Which consequence or risk concerns you most?
- Which decision or contribution do you believe you own?
Compare the answers with the charter, journey map and decision rights. The differences show where purpose, authority or impact remains unclear.
Distinction can help structure that analysis in a discovery conversation. The useful output is not artificial unanimity. It is a programme in which the necessary voices are heard, accountable people can decide and everybody affected can understand what happens next.
