You cannot influence everyone with the same message. A junior developer cares about whether your tool makes their daily workflow easier. A VP of Engineering cares about cost, risk, and whether the initiative will distract teams from shipping product. A security architect cares about compliance and blast radius. Treating these audiences identically is one of the most common reasons good technical ideas fail to gain traction.
Stakeholders are anyone who is affected by your initiative, has an opinion about it, or has the power to advance or block it. Identifying them systematically before you start communicating is essential.
The Power/Interest Grid
A practical tool for stakeholder analysis is the Power/Interest Grid — a 2×2 matrix that plots stakeholders by two dimensions:
- Power: Their ability to block or advance your initiative (budget control, veto authority, team influence).
- Interest: How directly and significantly your initiative affects their work or goals.
Quadrant 1 — Manage Closely (High Power, High Interest):
These are your most critical stakeholders. They can block your initiative and they care deeply about the details. Engage them personally and frequently. Involve them in design decisions. Their buy-in is not optional — it is a prerequisite for success. Example: the lead architect of your company's highest-revenue service.
Quadrant 2 — Keep Satisfied (High Power, Low Interest):
These stakeholders can stop you but do not want to be involved in the details. Give them concise executive summaries focused on risk, cost, and business outcomes. Never send them a 40-slide technical deep-dive. Example: the CFO who controls the infrastructure budget.
Quadrant 3 — Keep Informed (Low Power, High Interest):
These are often your end users — the application developers who will live with your platform every day. They cannot formally block you, but they can become your loudest advocates or your most vocal detractors. Communicate through newsletters, town halls, Slack channels, and beta programs. Make them feel heard. Example: individual developers on product teams.
Quadrant 4 — Monitor (Low Power, Low Interest):
Do not invest heavy energy here, but check in periodically. Stakeholders can move quadrants — a team that was low-interest becomes high-interest the moment your migration touches their service.
Stakeholder Mapping in Practice
Before any major initiative, spend 30 minutes writing down every person or group who will be affected. Place them on the grid. Then ask: "Who is missing?" It is common to forget adjacent teams (security, legal, finance) who have quiet veto power. Discovering a blocker in week eight of a twelve-week project is far more expensive than discovering them in week one.