Peoplelogic guide
First 90 Days: Assessing Performance Management
A practical plan for new people and HR leaders to learn how performance management works today, whether it produces useful results, and what to change first.
Welcome and how to use this guide
Welcome to your new role, and congratulations. We know you are still settling in, learning names, and getting your feet wet, and that performance management is one of many things competing for your attention right now. This guide gives you a practical way to look at it over your first three months, so you can learn what you have inherited before you decide what to change. Use what helps, skip what does not, and adjust it to your company.
In your first 90 days, find out how performance management works today, whether it produces useful results, and which one or two fixes would matter most. Hold off on redesigning anything until day 60 or later. Most programs have a history, a few vocal critics, and a few quiet defenders, and you will not know which is which until you have listened.
The work runs in three phases:
- Days 1 to 30: learn what exists. Read the documents, meet the people who run and use the process, and write down the official version of how it works.
- Days 31 to 60: test what actually happens. Compare the official process against the data and against what managers and employees describe.
- Days 61 to 90: decide and propose. Rank the problems, pick the first changes, and bring a plan to your leadership team.
The guide is written for a new HR or people leader at a company of any size. Skip questions that do not apply, for example calibration at a company with 40 employees.
Ten areas to assess
For each area, write down what the policy says, what people actually do, and the evidence you have for both.
| Area | What to assess | Questions to answer |
|---|---|---|
| Purpose and philosophy | Why the company has performance management and what leaders expect from it | Is it meant to drive pay decisions, development, accountability, or all three? Do the CEO, executives, and managers give the same answer? |
| Process and calendar | Cycle length, steps, deadlines, tools, and who owns each step | How many touchpoints per year? What is the on-time completion rate? How many hours does a manager spend per direct report per cycle? |
| Goal setting | Method (OKRs, KPIs, SMART goals, none), alignment to company priorities, and how often goals change | Can an employee state their top three goals? Do goals cascade from company priorities? Are they revisited mid-cycle? |
| Ongoing feedback and 1:1s | Frequency and quality of manager conversations outside formal reviews | What share of employees have a 1:1 at least every two weeks? Is there peer or upward feedback? |
| Evaluation and ratings | Rating scale, criteria, written review quality, and bias controls | Do ratings distinguish performance, or do 80 percent of people land in one box? Are rating distributions similar across managers, teams, and demographic groups? |
| Calibration | Whether managers compare ratings across teams before they are final | Who attends, what data do they use, and how often do ratings change? |
| Links to pay, promotion, and talent decisions | How performance results feed merit increases, bonuses, promotions, succession, and exits | Do employees understand the link? Do top performers receive visibly different outcomes? |
| Underperformance handling | Performance improvement plans, coaching, documentation, and exit decisions | How many PIPs ran in the last 12 months and how did they end? How long does a manager wait before acting on a problem? |
| Manager capability | Training, templates, coaching support, and HR business partner involvement | Have managers been trained on giving feedback and writing reviews? Which managers get the strongest results and why? |
| Employee experience, compliance, and systems | Trust in the process, legal risk, documentation, and the tools that hold the data | What do employees say in engagement surveys? Are reviews consistent with legal and documentation standards where you operate? Can the system produce clean reports? |
Days 1 to 30: learn what exists
By day 30 you should be able to describe the official process on one page and name the people who are happy and unhappy with it.
Read and collect
- The current policy, review templates, rating definitions, and the annual calendar
- Manager guides, training decks, and any FAQ sent to employees
- The last two cycles of communications from HR and leadership
- Any past program reviews, vendor proposals, or consultant reports
Hold conversations (30 to 45 minutes each)
- CEO and executive team: what they want from performance management, and what has frustrated them
- Your HR team and HR business partners: where they spend time fixing the process, and which managers cause the most escalations
- Finance and the compensation lead: how ratings affect budgets and merit decisions
- Legal or outside counsel: open disputes, claims, or documentation concerns tied to reviews
- Five to eight managers across different functions and levels, including at least one who is known to be strong and one who is known to struggle
- Five to eight individual contributors, selected with a manager and an employee resource group or similar input so you hear different perspectives
Questions to ask everyone
- Describe how a review cycle works here from start to finish.
- What does the process do well?
- Where does it waste time or create frustration?
- Think of a time it worked well. What happened?
- If you could change one thing, what would it be?
Keep a running log of quotes and examples. At the end of the month, group them into themes and note which ones came up in more than one function.
Days 31 to 60: test what actually happens
By day 60 you should know where the official process and the real process differ, and have numbers to show it.
Analyze the data
- Rating distribution overall, by department, by manager, by level, and by gender, race or ethnicity, age, and tenure where the data allows it
- Completion rates and lateness for goals, self-reviews, manager reviews, and calibration
- Relationship between ratings and promotions, pay increases, bonuses, and voluntary turnover in the last two years
- Whether employees rated highly leave at a different rate than the rest
- Time from first documented concern to PIP to exit for people who were managed out
- Word counts and specificity in a sample of written reviews. Read 20 to 30 yourself, chosen at random, with names removed if you can.
Gather broader input
- A short pulse survey to managers and employees with five to eight questions: clarity of goals, usefulness of feedback, fairness of ratings, time burden, and confidence in the link to pay
- Existing engagement or exit survey comments about reviews and feedback
- Two or three focus groups, with managers in one set and employees in another, so neither group edits itself
- Shadow one calibration session if a cycle is in progress. If not, ask for the notes and attendee list from the last one.
Compare against other practice
- Look at how two or three peer companies of similar size and industry run their cycle. Ask your network or HR peers rather than relying on published case studies, which tend to describe the ideal version.
- Check legal and compliance requirements for each location where you have employees, including documentation retention and any rules about PIPs or protected-class analysis.
At day 60, write a one-page summary of findings with the evidence behind each. Share it with one trusted peer or your manager before it goes further.
Days 61 to 90: decide and propose
By day 90 you should have a ranked list of problems, a short list of changes with owners and dates, and agreement from your leadership team on the first two.
- Rank each assessment area as strong, adequate, or weak, and attach the evidence. Put the weak areas in order by impact on retention, pay fairness, legal risk, and manager time.
- Separate quick fixes from structural changes. Quick fixes include clearer rating definitions, a shorter review form, a reminder schedule, and a calibration agenda. Structural changes include a new rating model, a new tool, or a change to how performance affects pay.
- Choose no more than two changes to make in the next cycle. Three or more at once tend to stall.
- Test each change with a small group of managers before rolling it out. Ask what they would drop as well as what they would add.
- Draft a communication plan for managers and employees that explains what is changing, why, and what stays the same.
- Set success measures before you start: on-time completion, manager time per review, employee survey scores on fairness and clarity, rating spread, and the pay and promotion link for top performers.
- Present the plan to the CEO and executive team. Lead with the evidence, then give the recommendation and what you need from them.
Data and documents to request
Ask for these in week one so they arrive before you need them. Expect some to be missing, and note which ones.
| Item | Source | Why you need it |
|---|---|---|
| Policies, templates, rating scale, calendar | HR | The official version of the process |
| Last two cycles of ratings by employee, manager, and team | HRIS or performance tool | Distribution, consistency, and bias checks |
| Pay, bonus, and promotion outcomes by rating | Compensation or Finance | Whether ratings drive rewards |
| Voluntary and involuntary turnover with ratings | HRIS | Whether the system keeps the right people |
| Completion and lateness reports | Performance tool | Process discipline and manager burden |
| PIP records and outcomes for the past two years | HR and Legal | Consistency and legal exposure |
| Complaints, grievances, and claims tied to reviews | Legal and Employee Relations | Fairness and risk |
| Engagement and exit survey results on feedback and growth | People Analytics | Employee view of the process |
| Training attendance and materials for managers | Learning and Development | Manager readiness |
| Tool contracts, renewal dates, and costs | Procurement or Finance | Constraints on change |
Warning signs to watch for
Any one of these deserves a closer look. Two or three together usually point to a process that needs structural change.
- Ratings cluster in one or two categories, or vary widely by manager with no difference in results
- Managers describe the review as a form to complete for HR, with no effect on their decisions
- Employees cannot say how their rating connects to their pay or promotion
- Reviews are late, copied from last year, or written in the final week before the deadline
- High performers leave at the same rate as everyone else, or at a higher rate
- PIPs are used mainly as a step before termination, and few people finish one and stay
- Calibration happens without data, or senior leaders override results without explanation
- Differences in ratings or pay outcomes between demographic groups that nobody has examined
- The performance tool holds data that nobody can pull into a report
- Leaders ask for a new tool or a new rating scale before anyone has checked whether the current process is followed
- A past redesign was announced and then dropped, and employees remember it
90-day deliverables and scorecard
Produce three things by day 90: a one-page description of how the process works today, a findings summary with evidence, and a plan for the next cycle. Use the scorecard below to record your rating of each area and the proof behind it.
| Area | Rating (strong, adequate, weak) | Evidence | Next step | Owner |
|---|---|---|---|---|
| Purpose and philosophy | ||||
| Process and calendar | ||||
| Goal setting | ||||
| Ongoing feedback and 1:1s | ||||
| Evaluation and ratings | ||||
| Calibration | ||||
| Links to pay, promotion, and talent decisions | ||||
| Underperformance handling | ||||
| Manager capability | ||||
| Employee experience, compliance, and systems |