Stakeholder Basics
Classification
Engagement Strategies
Stakeholder Scenarios
Real-World Applications
100

Define a stakeholder

A stakeholder is anyone affected by or affecting the project (e.g., clients, internal teams)

100

Define "High Power" in the matrix.
 

They have significant control over project decisions (e.g., CIOs, CTOs).

100

What does "Monitor" mean in the matrix?
 

Observing Low Power, Low Interest stakeholders with minimal effort.

100

Your internal IT team is resistant to change but doesn’t influence client decisions. Where do they fit?

 Low Power, High Interest → Keep Informed

100

Name a key stakeholder for an IT outsourcing project.

Client leadership, end users, internal IT teams, and regulators.

200

What is stakeholder analysis?

Stakeholder analysis is identifying and assessing key people who influence or are affected by the project.

200

Define "High Interest" in the matrix.

They are deeply invested in project success or failure (e.g., end users, business process owners).

200

What does "Keep Informed" mean?
 

Ensuring Low Power, High Interest stakeholders receive updates.

200

A senior executive at a client company isn’t engaged but has budget authority. Where do they fit?
 

 High Power, Low Interest → Keep Satisfied.

200

How can poor stakeholder engagement impact a software implementation?
 

 Leads to failed adoption, budget overruns, and project delays.

300

 Name the two axes of the Influence-Impact Matrix.

Power (Influence) and Interest (Impact).

300

Give an example of a Low Power, High Interest stakeholder.
 

 End users of a newly implemented IT system.

300

What does "Keep Satisfied" mean?

Addressing concerns of High Power, Low Interest stakeholders without overwhelming them.

300

Your project end users are deeply invested but have no decision-making power. Where do they fit?

 Low Power, High Interest → Keep Informed.

300

What’s a common stakeholder conflict in IT projects, and how can it be managed?


 Conflicting priorities—resolve by aligning expectations early, setting clear communication, and prioritizing engagement.

400

Why is stakeholder classification important?

 It helps prioritize engagement efforts, avoiding wasted resources and resistance.

400

Give an example of a High Power, Low Interest stakeholder.
 

A CFO who approves budgets but isn’t involved in project details.

400

What does "Manage Closely" mean?
 

Actively engaging High Power, High Interest stakeholders through frequent interactions.

400

Low Power, High Interest, strategy ?

→ Keep Informed.

400

Give an example of a stakeholder conflict in IT outsourcing.

An outsourced IT team faced resistance from client employees who feared job loss, leading to pushback.

500

What’s the biggest mistake in stakeholder engagement?

Not being able to identify and accordingly involve key decision-makers early, leading to late-stage project blockers.

500

What’s the best strategy for High Power, High Interest stakeholders?

Actively manage and involve them in key decisions.

500

Give an example of a real-world stakeholder engagement mistake and its impact.
 

 A CGI-managed cloud migration faced delays because key client stakeholders weren’t involved early, leading to additional costs.

500

A strategic partner is monitoring progress but hasn't intervened. How should you engage them?
 

 Monitor their involvement and proactively engage when strategic decisions arise.

500

How do you shift a stakeholder from Low Interest to High Interest in a digital transformation project?

Connect project benefits to business goals, provide training, and involve them early.

M
e
n
u