The New Manager's Team Performance Assessment Playbook: How to Evaluate Your Inherited Team in 90 Days
You just took over a team.
You've heard a mix of things about the people on it. Your predecessor left behind performance reviews that read like diplomatic exercises. You know you need to form your own view , but you also know that acting on first impressions is how new managers destroy trust in month one.
This playbook gives you a structured recipe for assessing your inherited team's performance accurately, fairly, and without burning the credibility you'll need to lead them.
It's not a "be nice and get to know people" plan. It's a data collection and calibration system , one that produces a defensible view of each person's actual performance level by day 90.
Why Most New Managers Get This Wrong
Problem 1: They trust the narrative too much. Every team you inherit comes with stories. "Alex is the one to watch." "Jordan is checked out." "Sam has been here 11 years and knows everything." Some of these narratives are accurate. Many are outdated. Some were shaped by politics you don't know about yet.
Problem 2: They act on impressions too fast. The first employee who impresses you in week one is not necessarily your top performer. They might be your best self-promoter. The quieter person who delivers consistently on unglamorous work might be 3x more important to the team's success.
Problem 3: They don't establish their own standards. They inherit performance norms from the previous manager and evaluate against them. But if the previous manager had low standards, you're calibrating against a broken baseline.
Problem 4: They confuse liking someone with performance. High-performing teams are not built on who the manager enjoys working with. Early relationship warmth and performance are frequently uncorrelated.
The Recipe at a Glance
Outcome: A calibrated, documented view of each team member's performance level by day 90 , good enough to inform your first performance review cycle and defensible to your own manager.
90-Day Structure:
- Days 1–30: Listen, observe, collect data. No performance judgments.
- Days 31–60: Form hypotheses, test them, cross-reference.
- Days 61–90: Calibrate and document your view. Make one move.
What you'll produce: A performance matrix for your team with a current state assessment and a development priority for each person.
Days 1–30: Listen, Observe, Collect Data
Rule 1: No Performance Conclusions in Month One
You will be tempted to form views. Write them in a private doc as hypotheses, not conclusions. The cost of acting on a wrong first impression is high; the cost of waiting 30 days to be sure is low.
Your Data Collection Plan
Conversations (structured, not casual): Schedule a 45-minute 1:1 with each team member in week one. Ask the same questions of everyone:
- "What are you working on right now that you're most proud of?"
- "What's the biggest thing getting in the way of you doing your best work?"
- "What do you think the team does well that I should protect? What should change?"
- "What do you wish your last manager had done differently?"
Don't share your impressions. Just listen. The quality of their answers tells you a lot , but more importantly, their stories point you toward the work they think matters.
Output observation: In the first 30 days, pay attention to the work, not the people. Who produces things on time without being chased? Whose work requires the most rounds of revision? Whose output do other people cite or build on?
Network observation: Watch who other people go to. Who gets pulled into problems that aren't theirs to solve? Who do junior team members ask for help? Who does your team go to outside the immediate group? This informal network is your first look at who's actually creating organizational value beyond their job description.
If you're using Confirm and have access to ONA data, this network picture is available immediately rather than requiring weeks of observation. That data will surface the patterns in days instead of months.
Formal record review: Pull the last two performance review cycles for each person. Read for patterns, not scores. What themes repeat across years? What changed? Were ratings calibrated (consistent with your external sense of the person's level) or inflated? Note where the narrative feels incomplete.
Days 31–60: Form Hypotheses, Test Them
By week five, you should have tentative hypotheses about each person. You're now stress-testing them.
The Hypothesis Testing Framework
For each person, write three sentences:
- "I think their current performance level is ___ [high/solid/developing/concerning] because ___"
- "My main uncertainty is ___"
- "The next thing I'm watching for is ___"
Then test each hypothesis deliberately.
Testing "high performer" hypotheses: Give them a stretch assignment , something meaningful, slightly beyond their current scope, with a real deadline. High performers use it to show range. Solid performers deliver the baseline. The response tells you which you have.
Testing "concerning performer" hypotheses: Have a direct conversation: "I've noticed [specific behavior]. I want to check my read. What's going on there from your side?" You're looking for self-awareness and accountability. A concerning performer who sees the gap and engages with it is recoverable. One who deflects consistently is a different situation.
Cross-reference with peers: By week six, you know the team well enough to ask peer-level questions. In your next round of 1:1s, add: "Who on this team do you find most useful to work with and why?" Don't prompt with names. Let people nominate. This is informal ONA , it surfaces who has peer-recognized contribution.
The "Surprise List"
By day 45, make two lists:
- Surprised Up: People performing at a higher level than the narrative suggested
- Surprised Down: People performing at a lower level than the narrative suggested
The people on these lists are your most important calibration opportunities. "Surprised Up" people may be undersupported or underpaid , investigate. "Surprised Down" people may have deteriorated since the last review, or may have been managed differently , understand before acting.
Days 61–90: Calibrate, Document, and Make One Move
The Performance Matrix
By day 75, build a simple performance matrix. For each person:
Current performance level: High / Solid / Developing / Concerning
Trajectory: Improving / Stable / Declining
Potential: Based on stretch response and network influence, what's your sense of their ceiling?
Your action: Investment priority / maintain / develop / watch closely
This isn't a formal document. It's your working map. But it should be specific enough to share with your own manager if asked: "Here's where I see the team."
The Documentation Standard
Everything in your assessment should be traceable to observable evidence. Not:
"Jordan seems disengaged."
But:
"Jordan missed two out of the last four project check-ins without a reschedule, and in our 1:1 in week four, when I asked about the new client project, they couldn't recall the deadline we'd set the week before."
Specific behavioral evidence is what makes your assessment defensible and fair. It also means that when you share feedback, you're giving the employee something concrete to respond to.
If you're using Confirm, log your observations directly in the continuous feedback module tied to each employee. By the time your first formal review cycle runs, you'll have 90 days of documented observations to draw from.
Making One Move in Month Three
By day 90, you should make one visible move that signals your standards.
This isn't about drama. It's about credibility. Your team is watching to understand what performance actually means under your leadership.
Options (pick the one that's most warranted):
- Recognize a hidden performer publicly. Acknowledge in a team setting or to your own manager someone who has been consistently excellent but under-recognized. This signals you're paying attention.
- Begin a direct development conversation with someone whose performance is slipping. Don't wait for the next review cycle. Act on what you've learned.
- Redefine an expectation that was vague. If your assessment revealed that team members have different understandings of what "done" means for key deliverables, clarify it. Explicitly.
The move matters less than the fact that you made one based on 90 days of observation , not inherited narrative.
Common Pitfalls
"I want to be approachable, so I'm avoiding hard conversations." Approachability and directness aren't in conflict. The person you'll be least approachable to by month six is the one you avoided hard conversations with in months one through three. They'll feel blindsided.
"I inherited a team with legacy performance problems and I don't want to deal with that yet." The longer you wait to address a known performance problem, the more you own it. By month six, your team members wonder why you haven't said anything. By month twelve, they assume you don't care or can't.
"I'm relying on my predecessor's reviews too heavily." Use them as one data point. Not the primary frame. You're there to build your own view.
Using Confirm for a New Manager Assessment
The 90-day playbook works without any specific tool. It works faster and more accurately with Confirm because:
-
ONA data compresses observation time. What takes you 30 days to notice about informal network patterns, ONA can show you in week one. You'll know who the team actually goes to for help before you've had your third team meeting.
-
Continuous feedback log. Rather than reconstructing your 90-day observations at review time, they live in Confirm tied to each person. This is especially important if you're a new manager who will be writing your first performance reviews for people you've only known for three months.
-
Historical context. You can see how each person's performance and network position have moved over time , not just what your predecessor wrote, but the underlying data.
See how Confirm helps new managers ramp faster →
The Output at Day 90
By the end of this playbook, you should have:
- A performance assessment for each person that's based on 90 days of observation, not inherited narrative
- Specific behavioral evidence for every conclusion you've drawn
- At least one person who's been recognized who wasn't before
- At least one person who now knows you see something that needs to improve
- A foundation for your first formal performance review cycle that makes you look like you've been there for a year
The first 90 days are when new managers either earn their team's respect or lose it. This playbook is how you earn it , not by being the nicest person in the room, but by being the most observant and most fair.
