Most leaders operate with high self-orientation — focused on proving their worth, asserting their ideas. This is the opposite of what works. This module builds your stakeholder operating system.
Before any relationship strategy can be built, you must map who exists in your stakeholder landscape. This is not a guess. It is a structured inventory — names, not categories.
"The leaders who build lasting influence lower their self-orientation and prioritize deep, methodical listening. They treat relationship-building as a diagnostic exercise. They build relationships before they build agendas. They map before they move."
| Name | Role / Title | Group / Category | Priority Tier | Why They Matter to You |
|---|
Looking at your map — who's missing that you've been avoiding naming? And if you're honest with yourself, why?
Rank your stakeholders by a single criterion: Who has the greatest ability to accelerate or derail your success? Not by title. Not by who you like. By leverage.
"Common mistakes: Overweighting people you like. Underweighting people you find difficult. Ignoring lateral peers. Ranking by org chart instead of by who can actually move or block things."
Name each person, their role, and the specific reason they are in your top tier. Be honest. Vague reasons mean you haven't decided yet.
Who did you rank lower than they should be because the relationship is uncomfortable? Name them, and name the real reason they're not in your top tier.
Trust is not built by being likeable. It is built methodically, across four variables. For each Tier 1 stakeholder, you need an honest read on where you stand.
Looking across your Tier 1 assessments — what's the pattern? Which variable shows up weak most often? What does that tell you about your default operating style?
AOS — Ambitions, Obstacles, Support — is the structured inquiry framework for every Tier 1 conversation in your first 30–60 days. It is not a script. It is a lens for understanding how they see their world.
"Every conversation is both relationship-building AND strategic intelligence gathering. They are not separate activities. When you hear something that contradicts what another stakeholder told you — note it. Do not resolve it yet. Contradictions are data."
Before your next conversation: What are you most tempted to talk about instead of listen to? What's the one assumption you're most likely to go in trying to confirm rather than test?
After completing stakeholder conversations, this stage helps you step back and see the map. What themes are emerging? Where are the contradictions? What does the org say it believes versus what behaviors actually reveal?
"You have been gathering strategic intelligence in every conversation. Now you surface it. Themes tell you what is stable. Contradictions tell you where the real tensions live. The gap between stated and actual priority tells you where to focus."
What topics, concerns, or ambitions came up across multiple conversations, unprompted? What does everyone seem to agree on?
Where did the same question produce meaningfully different answers? What does this person's version reveal that the other person's doesn't?
What does the org say it values versus what behaviors and resource allocation actually reveal? Where is the gap biggest?
Where do you sense tension that no one is naming directly? Which relationships or functions are misaligned in ways that haven't surfaced formally?
Based on everything you've gathered — what is your current working theory of this organization? What is it set up to win at? Where are the fault lines? What do you now believe that you didn't believe when you started?
What are the 3 most important relationship moves you will make in the next 30 days — and what specifically will you do in each one?