Beau

Okay, so I have to share this story. My cousin, right, he decides to build this big, beautiful deck in his backyard. He's a project manager, so he's got the plans, the budget, the timeline, everything is perfect. The crew starts working, and suddenly his next-door neighbor, a sweet old lady he's known for years, comes out absolutely furious.

Jo

Oh no. Let me guess, the new deck was going to block her prize-winning rose bushes from the sun?

Beau

Exactly! He'd completely forgotten to even talk to her about it. He was so focused on his 'project' that he missed a massive stakeholder. It ended up costing him a fortune to redesign part of it. It just goes to show...

Jo

That is the perfect, and painful, analogy for what we're talking about today: stakeholder engagement. Because if that's what can happen on a single project, imagine the scale when you're managing a program.

Beau

Right, because we've talked about how a program is a collection of related projects working toward a big strategic goal. So the list of people involved must just... explode.

Jo

It really does. In a project, you're thinking about your team, your direct manager, maybe the client. In a program, you have to think way broader. You've got the sponsors, sure, but also the steering committee, the heads of different departments—finance, IT, legal—who might be impacted. You've got the end users of whatever the program produces, maybe external regulators, suppliers... even the public.

Beau

That's a terrifyingly long list. How do you even begin to identify all of them? Do you just sit in a room and brainstorm anyone who might possibly care?

Jo

That's pretty much the first step, yeah. But you try to be systematic. You ask questions like: Who is affected by this program? Who has influence or power over it? Who has an interest in its success or failure? You're basically mapping the entire ecosystem of your program.

Beau

Okay, so you have this giant list of people. You can't possibly talk to all of them all the time. That would be a full-time job in itself.

Jo

Exactly. And this is where stakeholder analysis comes in. You don't treat everyone the same. A really common tool is the Power/Interest grid. Imagine a simple four-box square.

Beau

Okay, I'm picturing it.

Jo

On one axis you have power, from low to high. On the other, you have interest, low to high. So you take each stakeholder and place them in one of the four boxes.

Beau

So someone with high power and high interest... that would be your main program sponsor, maybe the CEO?

Jo

Precisely. Those are the people you need to 'Manage Closely'. You're in constant communication with them, involving them in decisions. They need to be your biggest champions.

Beau

What about the opposite? Low power, low interest. Who's that?

Jo

Maybe an employee in a totally unrelated department who will barely notice the program's effects. For them, you just 'Monitor'. You don't need to send them weekly updates, just keep an eye out in case their situation changes.

Beau

And the other two boxes? High power, low interest... and low power, high interest.

Jo

High power, low interest—let's say, the head of the legal department. They don't care about the day-to-day, but they have the power to stop everything if a compliance issue arises. So you 'Keep Satisfied'. You give them the info they need to feel comfortable, but you don't bog them down. Then you have low power, high interest. Think of the end-users of a new software system. They can't stop the program, but they're highly interested because it deeply affects their job. You 'Keep Inform'.

Beau

So it's not just about talking to people, it's about figuring out *how* to talk to them, and how often. That grid makes it much less overwhelming. It's like a communication plan.

Jo

It's the foundation of your stakeholder engagement plan. The plan formalizes this. It lists who the stakeholders are, what their interest and power levels are, what their key needs are, and what the strategy is for engaging them—weekly emails, monthly steering committee meetings, one-on-one check-ins, town halls...

Beau

This feels like it's as much about psychology as it is about management.

Jo

It absolutely is. A huge part of this is managing expectations. You have to be proactive. If you know one of the projects in your program is facing a delay, you don't wait for the high-power, high-interest sponsor to find out from someone else. You go to them first.

Beau

So you tell them the bad news, but you also come with a plan for how you're addressing it. You're controlling the narrative.

Jo

Exactly. It's about building trust. Stakeholders don't expect perfection, but they do expect transparency and competence. If you only ever bring them good news, they'll start to wonder what you're hiding. Bad news delivered well, with a solution, can actually strengthen your relationship with them.

Beau

That's a great point. So, let's say I'm communicating with two different groups. My 'Keep Satisfied' legal team and my 'Keep Informed' end-users. The message about that project delay would be different for both, right?

Jo

Completely different. For Legal, you might send a concise email saying, 'FYI, Project X is delayed by two weeks. No impact on regulatory compliance or contractual obligations.' That's all they need to know. You've satisfied them.

Jo

For the end-users, their training might be pushed back. So their communication needs to be more empathetic. It would be something like, 'We have a new timeline for the system rollout. We know you're eager to get started, and this delay will allow us to fix a critical bug, ensuring a much smoother experience for you. Here are the new dates for training.' You're managing their expectations by framing the delay in terms of a benefit to them.

Beau

It sounds like the real key is to constantly think, 'What does this person need to know, and why do they care?' Instead of just blasting the same information to everyone.

Jo

That's the entire game right there. It's about targeted, purposeful communication. And remember, communication is a two-way street. It's not just about telling them things; it's about creating channels to listen to their concerns and feedback.

Beau

So maybe my cousin should have just asked his neighbor about her garden before he even hired the contractor. A little listening goes a long way.

Jo

He would have saved himself a lot of time and money. And that's really the point. Good stakeholder engagement isn't just 'nice-to-have' administrative work. It's fundamental risk management for the entire program.