Stakeholder Management

It is built for people whose work depends on others agreeing, deciding or helping: analysts and engineers on IT projects, consultants and onsite or offshore coordinators in IT services, project coordinators and PMO associates, and anyone who has to keep a manager, a client and two other teams aligned at the same time. No formal training is assumed. The course is about the people around a piece of work: who they are, what they need and how to keep them engaged. Schedules, budgets and earned value belong to Project Management, and the everyday skills of writing clear emails and running meetings are in Communication and Interpersonal Skills.

The course uses the standard tools: stakeholder identification and analysis, the power-interest grid, the salience model (power, legitimacy and urgency), the stakeholder register, the engagement assessment matrix (unaware, resistant, neutral, supportive, leading), RACI, communication plans and RAG status reporting. Grids and RACI charts are drawn as tables, and the running example is the expense-claims app rollout. Software tools and exam content are left out.

Every lesson is a few short reading cards built around a worked example, such as a power-interest grid, a stakeholder register, a RACI chart or a status report, with a diagram where one helps and audio narration you can listen to instead of reading. A short multiple-choice quiz follows, with an explanation for every answer, and you can ask the AI guide about any card or question. The questions put you in a situation and ask for the call: which quadrant a stakeholder belongs in, who should be Accountable for a task, whether a project is amber or red, or whether to escalate now or wait. The final section compares look-alike choices, such as the grid or the salience model, inform or consult, and influence or escalate, and then works through cases such as a payroll system migration, conflicting asks from sales and finance, and an onsite–offshore client escalation.

Stakeholder trouble usually starts with a few familiar slips, and each of these has its own lesson:

• Listening only to the loudest stakeholders and missing the end users
• Assuming you know what a stakeholder wants instead of asking about the interest behind the request
• Putting more than one Accountable person on a task, or consulting everyone on everything
• Agreeing scope in a meeting and never confirming it in writing
• Watermelon reporting: green on the outside, red on the inside
• Escalating too late, or escalating without options and the impact of each
• Saying no without a reason or an alternative

Udemy and Coursera mostly teach stakeholder management through video lectures, usually as part of a wider project management programme. LinkedIn Learning offers short video courses by working professionals. This course does a different job: short narrated lessons followed by scenario questions that make you place a stakeholder, fix a RACI chart, choose an engagement strategy or decide when to escalate. Video suits hearing an experienced manager's stories, and this format builds the judgement to make those calls quickly on your own work. It has no live role-play, so try each technique with a real stakeholder at work or college.

Use a real piece of work, such as a project at your job, a client account or a college event, as your running case. When a lesson covers identification, list everyone it touches; when it covers the power-interest grid or the salience model, place them; when it covers the register and the engagement matrix, note where each person is today and where you need them to be. Draw a RACI chart for your next three tasks and check it for the mistakes the course names. Answer each quiz question before reading its explanation, because recalling the reasoning yourself is what makes it stick. Then write one honest status report with progress, risks and asks, and send it.