The First 90 Days of a New Team: 9 Signals Every Leader Should Track.

Your new team is finally in place.

Roles assigned. Backfills in place. Deadlines set. Everyone is “excited.”

This is the moment where many leaders step back.

But this is exactly when your quiet leadership matters most.

Below are the key things to watch for when a new team starts. So you don’t end up back in firefighting mode six months from now.


1. Can they say, in one sentence, why they exist?

Early on, ask a few team members, one-on-one:

“What is this team here to do, and why does it matter to the business?”

Listen for:

• Clear, simple answers that sound similar

• A link to real business outcomes (revenue, risk, cost, customer impact)

• Confidence, not guessing

Red flags:

• You hear three different “goals” from three people

• They talk only about tasks, not outcomes

• They can’t explain how their work helps the company win

If they’re unclear, that’s a leadership miss, not a team miss.

Your move:

• Restate the goal in simple language

• Explain how their work fits into the bigger picture

• Repeat it in every early meeting until they can say it back to you


2. Do they know what “success” looks like this month and this quarter?

A new team does not need a 40-page plan. But they do need a clear finish line.

Look for:

• 3–5 clear goals for the next 30–90 days

• Each goal tied to a simple metric (shipped, live, reduced, increased)

• Teamwork means being accountable. We hit goals together.

Ask them:

“If we meet again in 90 days, what will we have finished that proves this team is working?”

If they can’t answer, they will drift.

Your move:

• Help them define a short list of outcomes

• Make sure each outcome has an owner and a date

• Review these outcomes in your check-ins, not just activities


3. Are roles and decisions clear, or is everyone stepping on each other?

New teams often struggle with:

• Who decides what

• Who talks to which stakeholders

• Who owns which part of the work

You will see this show up as:

• Slow decisions

• Rework and confusion

• “I thought they were doing that” conversations

For product teams, in particular, watch for:

• A Product Owner who clearly owns business, financial trade-offs and scope decisions

• A Scrum Master who owns clearing blockers and improving flow

• Team members who know their main focus area, but are willing to stretch and learn

Your move:

• Ask: “Who decides X?” for the top 3–5 recurring decisions

• Make sure there is one clear owner, not a committee

• Support title changes early if you are creating new roles — like Cortez, burn the ships and commit


4. Are they talking openly, or going quiet and polite?

In the first weeks, teams will “play nice.” That’s normal.

But if it lasts too long, it’s a warning sign.

Healthy teams:

• Share concerns early

• Disagree with respect

• Raise risks before they explode

Unhealthy teams:

• Avoid hard topics

• Nods in meetings, grumbling after

• “Everything is fine” until the week before a big date

Remember: teams go through Forming, Storming, Norming, Performing. If you never see Storming, they might be hiding real problems.

Your move:

• In early meetings, ask: “What’s one thing that worries you about how this team will work?”

• Reward people for raising issues, not for staying quiet

• Make it clear that respectful conflict is expected and safe


5. Are they learning from failure, or hiding it?

New teams will stumble.

Your question is not, “Did they fail?” It is, “What did they do next?”

Watch for:

• Small experiments lead to small failures. Then, we learn clearly and quickly from them.

• Team members openly talking about what didn’t work

• Quick changes based on data, not blame

Red flags:

• People fear sharing bad news

• Blame games between roles or locations

• Repeating the same mistake more than twice

An easy picture:

A toddler learns to walk by falling. They fall, adjust, try again. They don’t write a report about falling. They just keep learning.

Your team is the same.

Your move:

• Say explicitly: “It’s okay to fail, but we must learn fast.”

• When something goes wrong, ask: “What did we learn?” before “Who did this?”

• Protect the team when they share bad news early — give them air cover


6. Do the numbers tell a story you can trust?

You don’t need to manage their work day-to-day. You need to connect to their radio frequency. Not yours.

Look at:

• Sprint and product backlogs

• Burndown charts

• Sprint reviews or regular demos

• Daily Stand-ups, especially when trending off course.

You’re not checking to control them. You’re checking for clarity and honesty.

Ask yourself:

• Are we seeing real, working results, not just status slides?

• Is work getting to “Done,” or stuck at “almost done” forever?

• Do trends match what they are telling you in meetings?

When the data shows they’re behind, the most powerful question you can ask is:

“How can I help?”

Your move:

• Attend sprint reviews

• Look for Done work — things that are ready to ship, not half-built

• Use data to start good questions, not to threaten


7. Are they being protected, or pulled apart by other priorities?

New teams often fail not because they are bad. They fail because they can’t focus and never get the chance.

Common problem:

• Key people are on 3 different projects

• Their calendar is full of other meetings

• Leadership constantly “borrows” them for urgent side work

Result:

• Slow progress

• Low morale

• The story that “this team model doesn’t work here”

In one client, we found a delivery team that had only 30–50 hours a week together out of a possible 120. They were expected to perform like a full-time team. They never had a chance.

Your move:

• Check how much real, shared time the team has each week

• Push back on random work that steals their focus

• Provide a dedicated Scrum Master to guard their time and clear blockers

• Listen and act when blockers are escalated.


8. Do they feel like “resources” or valued people?

Your language shapes your culture.

If leaders call them “resources,” they begin to feel like parts. If leaders treat them as talented, trusted people, they step up.

Watch for:

• How managers talk about the team: “people” or “resources”?

• Whether wins are celebrated and called out by name

• Whether they see a future in this role, or feel temporary and disposable

Your move:

• Use people’s names when you talk about the work

• Talk openly about career paths and promotion ladders

• Build individual development plans (IDP’s) so they know their career and learning options


9. Is leadership aligned above them, or sending mixed signals?

New teams can be doing everything right and still fail.

Why?

Because leaders above them are not aligned.

You will notice:

• One leader pushes speed, another pushes risk avoidance

• One tells them to cut scope, another tells them “nothing can move”

• The team gets whiplash from changing direction

In many cases, early team success exposes this misalignment. That’s not a sign the team is broken. It’s a signal leadership needs to get in the same room.

Your move:

• Meet with your peers and agree on clear priorities for the team

• Decide together what can flex: scope, budget, date

• Communicate one joined-up message back to the team


10. Are you leading by example, or just by email?

Your behavior sets the ceiling.

Teams notice when:

• You show up to reviews and actually listen

• You ask for recommendations instead of giving orders

• You model the same focus, honesty, and learning you expect from them

They also notice when:

• You say “fail fast” but punish any mistake

• You ask for “ownership” but override every decision

• You talk about “people first” but treat them like numbers

Your move:

• Join a few early team planning sessions or stand-ups, even briefly

• Ask: “What do you recommend?” before sharing your view

• Show them, with your actions, the culture you want them to build

• Apply the new culture to your own team.


A simple checklist for your next new team

When a new team starts, ask yourself, over the first 90 days:

1. Can they all clearly state the team’s purpose and why it matters?

2. Do they have 3–5 clear, measurable goals for this quarter?

3. Are roles and decisions well understood?

4. Are they having honest conversations, including some healthy conflict?

5. Are they learning openly from small failures?

6. Do their backlogs, charts, and reviews tell a clear, honest story?

7. Do they have enough shared time and the right tools to truly work as a team?

8. Do they feel valued as people, not just “resources”?

9. Are leaders above them aligned and sending one clear message?

10. Am I modeling the behavior I want from them?

You don’t need to manage everything. You DO need to watch these signals.

Starting a new team is to start a new business entity. Expect revenue, expenses and accountability just like you would from any other business unit. You want teams who will pay for themselves (and more!)

The future of your company won’t be built by your slide decks. It will be built by small, highly aligned, highly autonomous teams who know why they exist, are trusted to deliver, and are allowed to learn their way to greatness.

Your job is to give them that chance — and protect it.