Every team goes through the same journey. Bruce Tuckman named it in 1965: Forming, Storming, Norming, Performing. Most people learn about this model and nod along. Fewer actively use it to guide their own behavior at each stage.

This guide is for the person who wants to do more than just survive the forming period — who wants to understand where the team is, what's needed right now, and how to contribute to getting everyone to performing faster.

High performance isn't a destination you arrive at. It's a state you maintain: minimum waste, minimum rework, and every person operating at their potential. The milestones below are a map for getting there — and for staying there once you do.

Minimum waste No spinning on the wrong problem. Energy goes where it moves things forward.
Minimum rework Quality is built in, not bolted on. You understand what "done well" means before you start.
Full potential Each person doing the work only they can do — not just filling a role.

End of Day One

Your first impression is also your first data collection

Forming
  • Name the people who matter most to your work. Not the full org chart — the three to five people whose clarity, feedback, or decisions will shape yours. Get them on your radar now.
  • Ask one good question in every intro meeting. Not "what does your team do?" — something like "what's the hardest part of working across this team right now?" You learn more and you're already modeling the kind of thinking high-performing teams need.
  • Find out how the team communicates. Async or sync? Slack-heavy or meeting-heavy? Where do decisions get made — in the meeting, or in a doc before the meeting? Fitting into the existing rhythm reduces friction from day one.
  • Write down your first impressions. What's the energy? What's unspoken? What do people seem proud of versus tired of? These observations are most honest before you're fully inside the system.
Waste check The biggest waste on Day 1 is performing confidence you don't have. Ask, observe, and absorb. You're not expected to contribute yet — you're expected to orient.

End of Week One

Map the terrain before you move on it

Forming
  • Understand the team's actual goals — not just the stated ones. What does success look like this quarter? What does the team get measured on? What would make the team lead's job easier?
  • Learn the quality bar. What does "done" mean here? What gets sent back? What's considered a shortcut versus a reasonable tradeoff? Knowing this upfront eliminates the most common source of rework.
  • Identify the team's pain points. What slows work down? What's been broken for months that nobody has fixed? This is where you'll have the most leverage once you've earned the credibility to act.
  • Have one real conversation — not just an intro. Pick one person and go deeper. Ask about their work, what they're proud of, what frustrates them. Relationships that carry trust are built one real conversation at a time.
Waste check Resist the pull to jump into execution before you've understood the system. A week of deliberate observation saves months of working in the wrong direction.

End of Month One

Start contributing — and start noticing friction

Forming → Storming
  • Deliver something real. Not perfect — real. A contribution that the team can see, use, and give you feedback on. This is how trust is built faster than any relationship-building exercise.
  • Clarify your lane explicitly. Have a direct conversation with your manager: what does success look like for me in the next 90 days? What's in my scope, and what should I route elsewhere? Ambiguity here is the primary source of rework.
  • Notice where the team is storming. Disagreements about process, roles, or priorities will start to surface. This is healthy — storming isn't failure, it's the team figuring out how to work together. Don't avoid the friction; understand it.
  • Name one thing you'd change — to yourself, not to the team. Capture your fresh-eyes observations before you become too embedded to see them clearly. You'll need this list later when you have the credibility to act on it.
  • Give feedback before it's asked for. Not in a disruptive way — in a constructive one. Noting what's working and what isn't, in the right setting, signals that you're invested in the team's performance, not just your own.
Rework check Most rework at this stage comes from undefined expectations. Get explicit agreements in writing — on scope, on quality, on how decisions get made — and you'll spend far less time redoing work that was never clearly defined.

End of Month Six

Move from contributor to trusted teammate

Storming → Norming
  • Know the team's working norms — and contribute to refining them. How does the team make decisions? Resolve conflict? Communicate when something's going wrong? If these aren't documented, you're well-positioned to help create that shared understanding.
  • Identify your superpower on this team. Not your job title — what do you bring that's genuinely hard to replicate? High-performing teams have members who know exactly what they're uniquely good at and lean into it deliberately.
  • Make someone else's work easier. Notice a gap, a bottleneck, or something a colleague is struggling with that you can remove. The shift from "doing your job" to "making the team better" is where norming becomes performing.
  • Revisit your fresh-eyes list from month one. Which of those observations still feel true? Which have context you didn't have then? Are there things you can now act on — or articulate as proposals — that would move the team forward?
  • Build a feedback loop with your manager. Not just performance reviews — a regular, honest conversation about what you're doing well, where you're growing, and what the team needs from you next. Feedback is the fuel for closing the gap between current and potential.
Potential check Norming is where people often plateau — they get comfortable with how things work and stop pushing. The highest performers use this stage to go deeper, not just wider. Find the hard problems and choose one.

First Annual Review

Measure yourself against the right bar

Norming → Performing
  • Evaluate impact, not effort. The question isn't "how hard did I work?" — it's "what got better because I was here?" Be specific. A good review grounds itself in outcomes the team or organization can point to.
  • Name what you'd do differently. Every year holds decisions you'd make differently with hindsight. Naming them in a review isn't weakness — it's the signal that you're operating at a level of self-awareness that actually produces growth.
  • Articulate where you want to go. Not vaguely ("I want to grow into leadership") — specifically. What kind of problems do you want to be solving in year two? What skills do you want to build? What role do you want to play on this team?
  • Ask for honest feedback — and mean it. Specifically ask: what would make me more effective here? What am I not seeing about myself or my work? The people who get better fast are the ones who actively surface the uncomfortable truths.
Performance check A team performing at full capacity is full of people who know themselves well — their strengths, their growth edges, and what they're building toward. Your annual review is an investment in that self-knowledge.

Three Years In

You're not just performing — you're raising the bar

Performing
  • Be the person who helps the next joiner hit the ground running. Institutional knowledge, team norms, the unwritten rules that took you months to learn — make it easier for the next person. The team's performing state is only as durable as its ability to onboard new energy.
  • Challenge the norms that have become sacred. Some processes were right for the team two years ago and need updating now. The person with the tenure and the trust is often the only one who can name that without it being heard as an attack.
  • Invest in someone else's growth deliberately. Sponsorship, mentorship, removing blockers, advocating for someone's idea in a room they're not in — high-performing teams generate other high performers.
  • Ask whether this is still where your best work lives. Not because you should leave — but because staying with intention is different from staying out of inertia. At three years, you have enough context to make that call clearly.
Potential check A team stays at performing when its senior members actively work to keep it there — by modeling the culture, developing others, and refusing to let comfort slide into complacency. That's the job at three years.

The Tuckman model is often taught as something that happens to teams. This guide is built on a different premise: you can actively shape which stage your team is in and how fast it moves through them — by showing up with clarity, asking the right questions, naming the friction instead of avoiding it, and caring enough about the team's performance to invest in it before it's required of you.

That's what hitting the ground running actually means. Not moving fast on day one. Moving in the right direction — for yourself, and for the people around you.

🐱
Written with CAT
Claude Agent for Tania · Anthropic AI

This piece was researched and shaped in genuine partnership with Claude, Anthropic’s AI. Tania names this collaboration intentionally — because meaningful AI partnership is worth acknowledging, not hiding.

← Back to all resources