The First 90 Days: Starting as an Agile PM in a New Organization

The first 90 days in a new Agile PM role are your highest-leverage window for building relationships, understanding the real culture, and establishing the credibility that will determine your long-term effectiveness. A practical guide to starting well.

April 21, 2026

The First 90 Days: Starting as an Agile PM in a New Organization

The Temptation to Prove Yourself Immediately

Every experienced Agile practitioner who walks into a new organization faces the same temptation: to demonstrate their expertise quickly by identifying what's wrong and proposing improvements. The team isn't running retrospectives effectively. The backlog is a mess. The Product Owner doesn't have real prioritization authority. These are real problems — and they're probably visible to everyone in the organization already.

Diagnosing problems and proposing solutions within the first month of a new role is almost always a mistake — not because the diagnoses are wrong, but because you don't yet have the organizational understanding, the relationships, or the credibility to make them land. Solutions without trust create resistance. Expertise without context creates blind spots. The practitioner who arrives and immediately starts changing things typically triggers the same reaction in every organization: "They don't understand how things work here."

Michael Watkins' "The First 90 Days" framework (designed for executives, applicable to any leadership transition) provides the most useful structure for navigating this temptation: earn the right to change things by first demonstrating that you understand the organization deeply and that you can be trusted with the information people share with you.

Days 1–30: Listen, Observe, Map

The first month should be dominated by learning. Not process learning — most experienced Agile practitioners already know how Scrum works. Organizational learning: understanding the specific culture, history, and power dynamics of this particular organization.

Stakeholder Mapping

Build a comprehensive map of who matters — formally and informally. Who has the authority to approve changes? Who has the informal influence to make change succeed or fail regardless of formal authority? Who are the champions of the status quo? Who has been waiting for someone to finally address a persistent problem?

One-on-one conversations are the most valuable tool for this mapping. Come with questions, not proposals: "What's working well about how teams operate today?" "What are the biggest obstacles to delivering value faster?" "What's been tried before, and why did it or didn't it work?" Listen more than you talk.

Understanding the Culture Gap

Every organization has an official culture (what it says about how it works) and an actual culture (how decisions are really made and what behavior is actually rewarded). The gap between these two is the most important thing to understand in your first 30 days.

How are priorities actually set? Observe who is in which meetings, whose opinions shift decisions, and what happens to work that leaders don't personally champion. How is performance actually evaluated? Read the compensation and promotion records, not just the stated criteria. What behavior does leadership model? What leaders do under pressure tells you more about organizational culture than any value statement.

Observe Without Intervening

Attend as many ceremonies as you can — standups, planning sessions, retrospectives, reviews — without leading or significantly shaping them. What patterns emerge in team behavior? Where does the energy go up and where does it go flat? What isn't said that seems like it should be said?

This observational baseline is invaluable when you do start making changes: you'll know with confidence what you're changing, not just what you're reacting to.

Days 30–60: Build Relationships and Identify Leverage Points

The second month shifts from pure observation to selective engagement. You've now earned enough trust with some stakeholders to go deeper, and you have enough organizational understanding to ask better questions.

Identify Your First Quick Win

Quick wins in the first 90 days are not about demonstrating expertise — they're about building credibility and demonstrating that you can be trusted with responsibility. The best quick wins are genuine improvements that matter to stakeholders who have influence, don't require significant resources or organizational change, and deliver visible results within the 90-day window.

Critically: get the quick win with and through others, not by yourself. A change that you make alone demonstrates your capability. A change that you facilitate a team making demonstrates your leadership, which is what actually builds organizational trust.

Map the Informal Networks

Every organization has informal networks that are often more influential than the formal org chart. Communities of practice, former team members who are now in different roles, external coaches who have organizational history, long-tenured individual contributors who have seen everything — these informal networks carry institutional knowledge and social influence that the org chart doesn't capture.

Building relationships within these networks, with genuine curiosity rather than political calculation, gives you access to organizational context that you simply cannot get from formal channels.

Days 60–90: Begin Shaping, Not Fixing

By day 60, you should have enough understanding and enough credibility to begin actively shaping some aspects of how Agile is practiced in your area of responsibility. The framing matters: not "I've identified what's wrong and here's how to fix it," but "based on what I've learned, here are some hypotheses I'd like to test — what do you think?"

This framing accomplishes two things. It signals genuine learning orientation rather than predetermined judgment. And it recruits colleagues as co-owners of any changes, rather than subjects of them.

The 90-day window ends with you knowing the organization well enough to develop a coherent 12-month plan — one grounded in organizational reality rather than theoretical best practice. That plan is the foundation of everything you'll accomplish in the role.