The stakeholder map and influence without authority

A stakeholder is anyone the project affects or depends on, inside the team or not. A stakeholder map puts them on one page by two questions: how much can this person affect the launch? and how much does the result matter to them? The answers decide how much effort each relationship gets.

• High on both: work closely. Leo, the sponsor: frequent contact, decisions in writing.
• Strong influence, little daily interest: keep satisfied. Hanna can stop the money, but physics isn't her daily concern, so she gets the short monthly check with no surprises.
• Affected, little influence: keep informed. The support coordinators will answer every physics question from families in February; brief them before families start asking.

Watch for groups where no single person matters much but together they can stop everything: Klasna's tutor candidates. Involve them early and ask about their constraints.

The most dangerous stakeholder is the one who isn't on the map, because nobody plans around them. They are often outside the project and never in a meeting, but they control something the plan quietly depends on.

At Klasna, four of the six candidates who passed the demo lesson teach at schools. They can't promise February slots until their schools publish the second-term timetable in early January. The brief assumes about 15 learners per tutor, and that figure, and with it the target of 120 learners, depends on a timetable nobody on the map controls.

You can't talk to the schools, but you can plan around them. To find such stakeholders, follow each key assumption back to whoever controls it: who decides when tutors are free, who approves payments, who publishes what you need. A missing stakeholder is usually a hidden risk.

Finding an unmapped stakeholder is half the job; the other half is turning what you found into something you can act on. "It may work out" is an assumption, and an unwritten assumption fails silently.

At Klasna, Danylo expects the school-teaching tutors to be free in the evenings and at weekends, which is also when families want lessons. Plausible, but the 15-learners-per-tutor figure rests on it. So write it down with a check and a date: ask the candidates now which hours are safe whatever the timetable, and get confirmed weekly slots from each tutor by 10 January.

The date matters. Confirmation by 10 January still leaves time to recruit more tutors or adjust the target if the slots fall short; finding out in February doesn't. Treating the hope as settled, or waiting passively for the timetables, both leave the risk where nobody sees it.

Much of a lead's work depends on people who don't report to them. Roman from tutor operations introduces tutors to the work, and he has said no: January is his peak, when spring English and math tutors start, so no separate physics onboarding before February.

Asking Leo to order him works once and costs you Roman for the rest of the project. Influence without authority follows a different sequence:

1. Understand what the other side needs: Roman needs a calm January.
2. Look for overlap between his plan and yours: his English onboarding sessions run every week anyway.
3. Make one small, specific request with dates: physics tutors join the second-week session.
4. Offer something in return: Vira covers the subject part herself, so his team does less.
5. Confirm it in writing and keep your side.

Skip step 1 and you ask for the one thing he can't give.

The test of a request to someone you can't direct is simple: can they say yes in one line? That takes four parts.

• Show you understand their constraint: "I know January is your peak."
• One small, specific request with a date: physics tutors join the second-week English session, not "help somehow".
• An offer: Vira runs the subject part, so it adds little for his team.
• A clear ask: a yes or a better idea by Friday.

Three common versions fail. Name-dropping the sponsor ("as discussed with Leo") reads like a threat, even when meant as context. A vague plea leaves the other person to do your thinking. And repeating the request they already refused, only smaller-sounding, tells them you didn't listen.

Finally, confirm the agreement in writing and keep your side of it, so the next request starts from trust.

A colleague's no is the start of the work, not a reason to call the sponsor. Asking Leo to step in every time someone refuses wins the point and loses the person: next time Roman will say yes to your face and do the minimum.

Escalation has a proper place: a real conflict between two parts of the company, after an honest attempt to find a request that fits both. Then the sponsor decides, because only he can weigh Roman's January peak against the physics opening.

So the order is: understand, propose, offer, and only then, if the answer is still no, escalate. Influence is built over the whole project; every early escalation spends some of it.

When an honest attempt fails, a conflict between two parts of the company belongs to the sponsor. How you escalate decides whether you still have a colleague afterwards.

• Tell the other person first. "I'll ask Leo to decide between your January and our opening." Nobody likes to hear about it second-hand.
• Show both sides' costs. Roman's peak is a real business need, not an obstacle. Leo can weigh the trade-off only if both costs are on the table.
• Accept the decision either way, and say so.

Then update the map. A stakeholder's place isn't fixed: Roman moves from "keep informed" to "work closely" until onboarding is done, because right now he can make or break the launch.

Going to the sponsor quietly, or presenting only your side, may win this round. It also teaches Roman that agreements with you happen behind his back.

A stakeholder map is a snapshot, not a contract. People's influence on the launch and their interest in it change as the work moves through its stages, so the map is worth a quick look at each stage and whenever someone surprises you.

At Klasna, Roman barely mattered in October; during onboarding he can make or break the launch, so he moves to "work closely" until it's done, then back. The support coordinators sit in "keep informed" now, but as February approaches they will answer every family question, and a short briefing before opening becomes urgent. The tutors' schools appeared on the map only when Vira mentioned the timetables.

The cost of a stale map is the same as of a missing stakeholder: someone you could have prepared turns into a surprise.

How it fits together: the map tells you who matters and how much effort each person gets; influence without authority wins help from those you can't direct. The next lesson gives them all one rhythm: a weekly written status that says where the project really is, without a meeting.