Original sample article. Not approved Tenjin advice or published commentary.
Define the decision you are supporting.
A stakeholder map is most useful when attached to a specific decision or change. Identify the outcome being considered, the constraints around it and the questions that need resolution. Without this focus, mapping can become an exercise in collecting names.
Separate influence from interest.
An organisation may have significant influence but limited immediate interest, or strong interest without a formal role in the decision. Record both. Avoid assuming that a public position describes every concern; note where understanding is based on evidence and where it remains a hypothesis.
Give the map an owner.
For each material relationship, identify an internal owner, the current state of engagement and the next appropriate step. Keep factual notes separate from assumptions. Review privacy, confidentiality and recordkeeping requirements when deciding what information belongs in the working document.
Revisit it at decision points.
Stakeholder priorities can shift when a proposal becomes more concrete. Revisit the map before announcements, approvals and significant changes in scope. Its value lies in informing action, not in remaining a polished diagram.
