Concepts / Converting Skeptical Stakeholders to Supporters

Converting Skeptical Stakeholders to Supporters

Stakeholders include anyone who can affect or be affected by a project, which usually goes beyond the technical team.

  • Programming

A System That Works but Still Stalls

Imagine a manufacturing plant that decides to replace its paper-based inspection records with a tablet-based system. The engineering team has produced a sound design, and the software works exactly as specified. Even so, the project can stall or fail if the people who will live with the change do not accept it. This is the central problem that stakeholder analysis addresses.

Stakeholder analysis is the discipline of finding those people before the design is locked, understanding what each one stands to gain or lose, and deciding how to bring them along. This article follows one case from the first reading of the political landscape to a changed attitude on the shop floor. Along the way you will trace how two different skeptics moved toward support, and you will identify the concrete actions that moved them.

Who Counts as a Stakeholder

Definition

A stakeholder is anyone who can affect or be affected by a project. This definition is deliberately broad, and it usually reaches well beyond the technical team that builds the change.

Stakeholder analysis begins with a simple inventory question: who has a stake here, and in which direction does their stake point? Some stakeholders hold the power to approve or stop the change. Others have little formal authority but use the new system every shift, so their experience decides whether it succeeds. An analysis that lists only the people with authority misses the people who will determine whether the change works in practice.

Stakeholder Analysis as a Process

The source describes stakeholder analysis as a sequence of steps that happen in a deliberate order. Each step depends on the one before it, and skipping ahead tends to leave gaps.

  1. 1
    Find the people who have a stake in the change, before the design is locked.
  2. 2
    Sort each stakeholder by the role they play relative to the change.
  3. 3
    Understand what each stakeholder stands to gain or lose.
  4. 4
    Decide how to bring each stakeholder along toward the change.

Three Roles and Their Influence

A useful way to sort stakeholders is by the role they play relative to the change. In the case under study there are three distinct roles. The sponsor is the senior leader backing the change, here the vice president. The blocker is the person whose concerns could stop the change from moving forward, here the quality manager, whose professional standing depended on the plant being ready for its AS9100 audit. The line user is the person who works with the system directly, here a senior inspector with twenty-three years at the company.

Tablet inspectionchangereplaces paper recordsSponsorvice presidentBlockerquality managerLine usersenior inspectorprovides directionconcerns could stop itdecides if it is workable daily
How does each role relate to the same tablet inspection change, and why does a map that shows only the sponsor make the project look safer than it is?

The three roles connect to the same change in three different ways. The sponsor provides direction. The blocker holds a veto-like influence over whether the change proceeds. The line user determines whether the change is workable on an ordinary day. A stakeholder map that records only the first relationship would suggest the project is already safe, which is exactly the trap the analysis is meant to avoid.

RoleRelationship to the changeExample in the case
SponsorProvides direction and backs the changeVice president
BlockerConcerns could stop the change from moving forwardQuality manager concerned with AS9100 audit readiness
Line userDetermines whether the change is workable on an ordinary daySenior inspector with twenty-three years at the company

Three roles in the tablet inspection case and how each relates to the change

Tracing the Line User's Turnaround

The first skeptic in the case is the senior inspector. She was not blocking the project in the formal sense. She was openly skeptical that the new tools could handle work that respected her craft. Watch how her stance changes as the project proceeds, and notice what happens at each point.

Openly skepticaldoubts tools can handlecraftRuns first sliceon her own shiftSupporterovertime dropped to fortyminutesweek threedirect evidence in her routine
How does the inspector's stance move from skepticism to support, and at which point does the shift happen?

Her skepticism did not dissolve because someone argued with her. It dissolved in week three, after she ran the first slice on her own shift. Her overtime dropped to forty minutes, which gave her direct evidence about the change in her own working day. The concrete action that moved her was hands-on use of the system in her own routine, and the measurable result she observed was the drop in overtime.

Tracing the Quality Manager's Turnaround

The second skeptic is the quality manager, the blocker. Her concern was specific: the plant's readiness for its AS9100 audit. The source notes that a blocker's concern is often this kind of specific issue, and that early involvement with visible evidence can change her position. The sequence of actions below comes from how she was persuaded.

Early involvementoffered before the designwas fixedCompliance evidenceinspectable records for theauditDesign shapedher input could stillchange itthenleads to
Which actions happened in what order, and how did each one move the blocker forward?

The evidence that persuaded her was inspectable evidence about compliance, and it was offered early enough that she could shape the design. The early timing mattered as much as the content. Evidence that arrives after the design is locked tells a blocker that her concerns came too late to matter.

Two Paths to Support

The two cases are instructive when placed side by side. Both shifts moved a skeptic toward support, but the path depended on what each stakeholder needed to see. The quality manager needed evidence about compliance that she could inspect, offered early. The inspector needed first-hand experience of the system doing useful work in her own routine.

FeatureQuality manager (blocker)Senior inspector (line user)
Source of skepticismConcern about AS9100 audit readinessDoubt that tools could handle craft work
What persuaded herInspectable evidence about complianceRunning the first slice on her own shift
Timing that matteredEvidence offered early enough to shape the designExperience in week three
Visible resultHer input could still change the designOvertime dropped to forty minutes

Comparing the two skeptics and the actions that moved each one

Predicting a Different Stakeholder

MEDIUM

A generated scenario: a maintenance supervisor is skeptical of a new digital work-order system, and she is a line user who handles the system every shift. Before you decide, consider the source's guidance. What kind of evidence would most likely move her, and at what point in the project should it be offered? Write down your prediction and the reason for it.

Hints
  • Ask whether she is a blocker or a line user, and what each role relates to in the change.
  • The source suggests the inspector moved after using the system herself, while the blocker moved after early, inspectable evidence.
  • Consider whether she needs to check something, or whether she needs to experience the system working in her routine.

Mistakes Beginners Make With Stakeholders

  • Common mistake

    Listing only the people with formal authority

    What it looks like

    A map that includes the vice president but omits the senior inspector who uses the system every shift.

    Why it fails

    The people who use the system daily decide whether the change works in practice, even without formal power to approve it.

    Do this instead

    Ask who has a stake in the change, including people who will use it, and record the direction of each stake.

  • Common mistake

    Treating sponsor support as proof the project is safe

    What it looks like

    Concluding the tablet project is secure because the vice president backs it.

    Why it fails

    A blocker can still hold veto-like influence over whether the change proceeds, and a line user decides whether it is workable.

    Do this instead

    Map each role separately, because the three roles connect to the change in three different ways.

  • Common mistake

    Assuming a skeptic will be won over by argument

    What it looks like

    Repeatedly explaining the benefits to the inspector in meetings.

    Why it fails

    Her skepticism did not dissolve because someone argued with her. It dissolved after she used the system on her own shift.

    Do this instead

    Give the stakeholder something to check or experience, such as inspectable compliance evidence or a working slice in their own routine.

  • Common mistake

    Offering evidence after the design is locked

    What it looks like

    Presenting compliance records to the quality manager once the design is final.

    Why it fails

    The evidence was persuasive partly because it arrived early enough for her to shape the design. Late evidence signals that her concerns came too late to matter.

    Do this instead

    Involve blockers early, while their input can still change the design.

Summary of the Turnaround

  1. 1
    A stakeholder is anyone who can affect or be affected by a project, which usually goes beyond the technical team.
  2. 2
    The sponsor provides direction, the blocker can stop the change, and the line user decides whether it is workable on an ordinary day.
  3. 3
    Blockers such as the quality manager can be moved by inspectable evidence about their specific concern, offered early enough to shape the design.
  4. 4
    Skeptical line users such as the senior inspector can move toward support after experiencing the system working in their own shift.

At a glance

  • A stakeholder is anyone who can affect or be affected by a project, which usually goes beyond the technical team.
  • Stakeholder analysis finds the right people before the design is locked, sorts them by role, and considers what each one stands to gain or lose.
  • The sponsor, blocker, and line user each relate to the same change differently, so each needs its own analysis.
  • A skeptical blocker moved toward support through early, inspectable compliance evidence, and a skeptical line user moved through first-hand experience of the system on her own shift.