Engaging stakeholders through the life cycle

A stakeholder engagement plan is a forecast. Engagement itself happens day by day, in meetings, emails, workshops, hallway conversations and the occasional difficult phone call. This lesson follows stakeholders through the project life cycle, from initiation to closure, and covers the work of the manage stakeholder expectations task: keeping expectations realistic, tracking sentiment, dealing with issues and decisions, and handling the resistance that almost every significant change provokes. Change management theory is covered in BUS-130; here the focus is on what a project manager does with stakeholders at each stage.

Engagement changes across the life cycle

Different stakeholders matter most at different times, and the same stakeholder needs different things as the project moves on. Early on, influence is high and the cost of change is low; this is when stakeholders can shape objectives and scope most cheaply. Late in the project, influence is lower and changes are expensive, so the emphasis shifts to acceptance, readiness and adoption.

Managing expectations

Expectations drift. A sponsor who agreed in March that a feature was out of scope may assume by July that it is coming. A user who saw an early prototype may expect the final product to look exactly the same. Managing expectations is mostly about preventing surprises: telling stakeholders early when something is changing, confirming agreements in writing, repeating key messages about scope and dates, and using demos and reviews to keep the shared picture current.

A useful habit is to separate three things in every conversation about a request: what the stakeholder is asking for, what the project has agreed to deliver, and what it would take to close the gap. When a stakeholder asks for something new, the right response is rarely an immediate yes or no. It is to understand the request, explain its effect on scope, schedule, cost and risk, and route it through the agreed change process. That keeps the relationship positive while protecting the baseline.

Tracking engagement and sentiment

Engagement needs monitoring like any other part of the plan. Signs of engagement include attendance at reviews, timeliness of approvals and decisions, the tone and content of feedback, the number and nature of escalations, and informal comments. Some teams keep a simple sentiment score for key stakeholders, updated after each significant interaction, and review trends at the regular engagement review. A falling score is an early warning to act before resistance becomes opposition.

Sentiment scoring is subjective, so be careful not to treat it as data in the scientific sense. It works best when the same people score consistently, when scores are linked to specific observations ("approved the test plan a week early", "cancelled two reviews"), and when the main output is an action, not a chart.

Issues, decisions and the logs that support them

Stakeholder engagement generates issues and decisions. An issue is a current problem that needs resolving, such as a department refusing access to data or a disagreement about acceptance criteria. A decision is a choice that commits the project, such as approving a design or accepting a risk. Recording both matters. An issue log gives each issue an owner and a due date, so stakeholders see that concerns are being handled. A decision log records what was decided, by whom, when and on what basis, which prevents later disputes about whether something was agreed.

Understanding resistance

Resistance is a normal response to change, not a character flaw. People resist for rational reasons (the change really will make their work harder, or the design has a flaw), emotional reasons (fear of losing competence, status or control, or simple fatigue from previous changes) and political reasons (a change shifts budget, authority or headcount). A project manager who treats all resistance as obstruction misses useful information: resisters often see risks the project team has overlooked.

The change curve, adapted from Elisabeth Kubler-Ross's work on grief, describes a common emotional path: shock and denial, then frustration and a dip in morale and performance, then experimentation, acceptance and integration. Its practical lesson is that the dip is predictable. Communication should match where people are: facts and reasons early, listening and support in the dip, and practice, quick wins and recognition during recovery. Prosci's ADKAR model makes a similar point at the individual level: people need awareness of why, desire to take part, knowledge of how, ability to do it and reinforcement to sustain it. Resistance often signals that one of these elements is missing.

Engagement at transition and closure

As a project ends, attention often shifts to the next project, and stakeholder engagement suffers. But this is when acceptance, handover and benefits ownership are settled. Operations staff need training and support; the business owner needs to confirm who will measure benefits after the project team leaves; and stakeholders who contributed deserve thanks. A short closure conversation with key stakeholders, asking what went well and what to improve, produces valuable lessons and leaves relationships in good shape for the next project.

The sponsor relationship

Of all stakeholder relationships, the one with the sponsor deserves the most deliberate attention. The sponsor champions the project, secures funding, resolves issues beyond the project manager's authority and represents the project to executives. A project with a disengaged sponsor is far more likely to fail. Good practice is to agree early how often you will meet and what decisions the sponsor will make, to bring problems early with options rather than surprises, to help the sponsor prepare for executive meetings with concise briefings, and to ask directly for help when you need it. If the sponsor becomes disengaged, find out why: competing priorities, loss of confidence or a change in strategy each need a different response.