stakeholder-maplisted

# Stakeholder Map An org chart tells you what people are called. A stakeholder map tells you what they can do to this renewal. They are not the same document and the first one is easy to mistake for the second. The useful question is never "what is their title". It is **"what happens to this account if this person says no, and what happens if they leave".** The failure this exists to prevent: **a beautifully complete contact list on an account nobody can name a decider for.** --- ## What this needs **Shared context.** If an `account-context` document exists, read it first. It says who signs in this business, by role, and whether customer success ever meets them. That answer sets the bar for everything below. Where it is absent, carry on and name the assumption. **Minimum: the names you know and roughly what they do.** Gaps are the output here, not a blocker. **Better with** the last few months of email and meeting history, so "who used to respond and stopped" can be answered rather than guessed. **Best with** the original deal notes, which usually name the economic buyer and almost always name the sceptic that nobody has thought about since. On an inherited account, `account-research` is what finds those notes and establishes which of the names in them are still there. --- ## Step 1: Sort by what they can do, not what they are called Six positions. A person can hold more than one, and the same title maps differently in different companies. | Position | What defin