Stakeholder Management Is Mostly Asking Better Questions
Stakeholder Management Is Mostly Asking Better Questions
Stakeholder management sounds like a soft, vague skill until a project depends on it. Then it becomes very concrete: different people want different things, they don't always say so directly, and your job is to find the real need under the stated request before you commit a team to building the wrong thing.
The first version of a request is rarely the real one
"We need this feature" is usually the end of someone's thinking, handed to you as the start of yours. The useful move is to ask what decision it helps them make, or what happens if it doesn't get built. Often the answer reshapes the request entirely, and occasionally it dissolves it, which saves everyone a sprint.
Most of the value in stakeholder management lives in that gap between what someone asked for and what they actually needed.
Align on priorities before you align on details
When stakeholders disagree, it's tempting to negotiate the details. But the disagreement is almost always about priority, not specifics. Get everyone to agree on what matters most first, and the details tend to fall into place. Skip that step, and you'll re-argue the same point in every meeting.
My role is to make those priorities explicit and shared, so the team isn't quietly building to three different versions of "important."
Keep everyone honest, gently
Good stakeholder management isn't about saying yes to everyone or being the person who blocks things. It's about keeping the conversation honest, surfacing trade-offs early, naming constraints plainly, and making sure the people affected by a decision are in the room when it's made.
Do that consistently and trust builds on its own. After that, coordination gets a lot easier.
Harish skipped presentations and built real AI products.
Harish Varajith C was part of the April 2026 cohort at Curious PM, alongside 18 other talented participants.