Why stakeholder mapping is your first 90-day priority
Most advice about starting a new role focuses on quick wins — find something visible, deliver it fast, prove your value. This advice is well-intentioned but often premature. Quick wins chosen without understanding the stakeholder landscape can backfire spectacularly.
Imagine launching an efficiency initiative that threatens a VP's pet project. Or proposing a process change that a long-tenured director already tried and failed at. Or building alignment with the wrong group because you did not understand the real power dynamics.
Stakeholder mapping protects you from these mistakes. By spending your first 30 days understanding who matters, what they care about, and how they relate to each other, you make better decisions about where to invest your energy for the remaining 60 days.
Harvard Business Review research on leadership transitions consistently shows that relationship building in the first 90 days is the strongest predictor of long-term success. Professionals who prioritise stakeholder mapping outperform those who rush to demonstrate competence.
Days 1-30: Map the landscape
The first month is about listening, learning, and mapping. Resist the urge to fix things or share opinions. Your job right now is to understand.
Start with your manager. In your first 1-on-1, ask explicitly: "Who are the key stakeholders I should build relationships with in my first 90 days?" Your manager knows the landscape better than you do and will appreciate that you are thinking strategically about relationships, not just tasks.
Create your initial map. Identify people in four categories: - Decision-makers: People who approve your work, allocate resources, or influence your success. Your manager, skip-level, and any steering committee members. - Collaborators: People you will work with regularly. Cross-functional peers, partner team leads, shared resource owners. - Influencers: People who shape opinions even without formal authority. Long-tenured ICs, respected technical leads, well-connected project managers. - Informants: People who understand the history and context you lack. They know why things are done a certain way, what has been tried before, and where the landmines are.
Schedule introductory meetings. Aim for 2-3 stakeholder meetings per week in month one. Come with questions, not presentations. Ask: "What should I know about how things work here?" and "What would success look like for someone in my role?" and "What has been tried before that did not work?"
Days 31-60: Deepen and prioritise
By day 30, you should have a working map of your stakeholder landscape. Month two is about deepening the relationships that matter most and identifying where you can create value.
Prioritise your stakeholders. Not everyone on your map deserves equal investment. Rank stakeholders by two dimensions: how much influence they have on your success, and how strong your current relationship is. The highest priority are high-influence, low-relationship stakeholders — these are the gaps that need closing.
Move from introductions to substance. Your first meetings were about learning. Now shift to value-creation conversations. Share observations from your onboarding ("I have noticed X — is that consistent with what you see?"), offer to help with their priorities, and start building a reputation as someone who listens, thinks, and contributes.
Identify the informal network. By now you should be able to see the informal power structure — who people really listen to, who has outsized influence despite a modest title, who is the gatekeeper for information or resources. This informal map is often more important than the org chart.
Check your assumptions. Share your stakeholder map with your manager or a trusted peer and ask for feedback. "Am I missing anyone important? Am I reading the dynamics correctly?" This calibration prevents you from investing in the wrong relationships.
Days 61-90: Act on your map
The final month of your first 90 days is where stakeholder mapping converts into career momentum.
Align your quick wins with stakeholder priorities. Now that you understand what different stakeholders care about, you can choose initiatives that create value for the right people. A quick win that your skip-level cares about is worth ten that nobody notices.
Build coalition for your ideas. If you have identified changes you want to make, start socialising them with key stakeholders before any formal proposal. Get feedback, incorporate their input, and build support person by person. By the time you present the idea formally, the decision should feel like a foregone conclusion.
Establish your recurring cadence. By day 90, you should have a regular meeting rhythm with your most important stakeholders. Weekly with your manager, bi-weekly with key collaborators, monthly with senior stakeholders. This cadence becomes the operating system for your stakeholder relationships going forward.
Document your map. Your stakeholder map is a living document. Record what you have learned about each person — their priorities, communication style, concerns, and your relationship status. This documentation becomes invaluable when organisational changes happen, which they always do.
Orvo is designed to support this entire 90-day stakeholder mapping process. Its Network Map visualises your relationships, its meeting prep surfaces context before every conversation, and its relationship tracking ensures nothing falls through the cracks during the most critical phase of a new role.
Common mistakes in first 90 days stakeholder mapping
Even professionals who recognise the importance of stakeholder mapping make predictable errors.
Mapping only your direct contacts. Your stakeholder map should extend at least two levels in every direction — your manager's peers, your collaborators' managers, and the key players in adjacent teams. The people who influence your success are often one or two degrees removed.
Neglecting the informal network. The org chart tells you who reports to whom. It does not tell you who actually makes decisions, who controls information flow, or who has the CEO's ear. Mapping the informal network requires observation and asking good questions.
Front-loading all meetings into week one. Spreading your stakeholder introductions across the full first month gives you time to process what you learn and show up better prepared for each conversation. Two thoughtful meetings per week beat ten rushed meetings in five days.
Failing to log what you learn. The details you learn in stakeholder meetings are perishable. If you do not write down what someone cares about, what they told you about the history of a project, or what their concerns are, you will forget within a week. Capture context immediately after every meeting.
Treating the map as static. Stakeholder maps change as the organisation evolves. New leaders join, priorities shift, teams are reorganised. Review and update your map at least quarterly.
Key Takeaways
- ✓ Stakeholder mapping should be your primary activity in the first 30 days of any new role
- ✓ Map four categories: decision-makers, collaborators, influencers, and informants
- ✓ Days 1-30: listen and map; Days 31-60: deepen and prioritise; Days 61-90: act on your map
- ✓ Prioritise high-influence, low-relationship stakeholders — these are your biggest gaps
- ✓ Document everything you learn and treat your stakeholder map as a living document