Many organizations say they run a performance management cycle. What many actually run is a performance review: one conversation, once a year, with a rating at the end. The difference matters. In Gallup’s 2024 research, 56% of U.S. employees said they review their goals with their manager once a year or less. In a separate Gallup survey of Fortune 500 CHROs, only 2% strongly agreed that their performance management system inspires employees to improve.
This guide explains the performance management cycle as it actually works: the five stages, who owns each one, how long a cycle should run, and the points where it breaks. It ends with a starter cycle you can run with a team that has none.
What the performance management cycle is, and what it is not
The performance management cycle is the repeating sequence of planning, tracking, assessing, rewarding, and resetting that links what employees do to what the organization needs. It runs all year. The performance review cycle is only one part of it: the formal assessment that sits in the middle. Treating the review as the whole cycle is the most common design mistake, because everything before it, clear goals and regular feedback, decides whether the review says anything useful.
Think of the performance management process as a loop, not a line. The last stage feeds the first, so each cycle starts from what the previous one taught you. In a small company, one manager may run all five stages personally. In a larger one, HR owns the calendar and the rules, while managers own the conversations, and the cycle only works when both halves are clear.
Five stages, with an owner and a failure point for each
The performance management cycle has five stages. Each has a clear owner, an output worth keeping, and a predictable way of failing.
Stage 1: Plan. The manager and employee agree goals and expectations in writing, with measures. For new hires, the first plan is set during onboarding. Goals can be written as SMART goals or OKRs; what matters is that each has an explicit measure and ladders up to a team priority, so a manager can tell at a glance whether it is on track.
- Owner: the manager, with the employee.
- Output: three to five goals with measurable outcomes, plus one development goal.
- Failure point: goals set once and never reopened, which is how most employees end up reviewing them once a year or less.
Read more: The employee onboarding process, step by step
Stage 2: Monitor. Check-ins and continuous feedback keep the plan honest while the year unfolds, and they stop the review from becoming a surprise.
- Owner: the manager.
- Output: brief notes, adjusted goals, and recorded examples of work.
- Failure point: feedback saved up for the review, which hands the year-end conversation to recency bias.
Stage 3: Assess. This is the formal performance review cycle step: employee self-assessment, manager assessment, and calibration across teams so that ratings mean the same thing in different departments.
- Owner: the manager, with HR facilitating calibration.
- Output: a documented assessment against the goals set in stage one.
- Failure point: ratings given without calibration, so the same performance earns different outcomes depending on the manager.
Stage 4: Reward and develop. Assessment results feed pay, promotion, recognition, development plans, and, where needed, a structured improvement plan.
- Owner: the manager, HR, and whoever owns compensation.
- Output: decisions and a development plan the employee can see.
- Failure point: reviews that finish after pay decisions are locked, so the outcome changes nothing.
Stage 5: Reset. The cycle closes by feeding what it learned into the next one: goals are refreshed and the process itself is reviewed.
- Owner: HR and senior leaders.
- Output: next-cycle goals and a short list of process fixes.
- Failure point: nobody asks managers and employees what was wasted effort, so the same friction repeats.
How long should the performance management cycle run?
Cycle length is a design choice, and each option trades simplicity against responsiveness.
- Annual: simplest to run, but backward-looking, and goals can go stale long before the review.
- Semi-annual: adds a midpoint correction without doubling the workload.
- Quarterly: short check-ins keep priorities current. Gallup found that employees with quarterly progress checks were 90% more likely to be engaged and 2.1 times as likely to see the process as fair and transparent.
- Continuous: feedback happens as work happens, which only works if managers are trained to give it.
The formal review is not disappearing. A 2026 Talent Strategy Group benchmark found that 93.6% of surveyed organizations use one and 56.3% still run it annually, while 47% encourage three or four formal feedback conversations a year. In practice, many organizations pair them: one performance review cycle each year or half-year, with light quarterly check-ins and continuous feedback in between. Whichever rhythm you choose, the performance management cycle should run the same way for everyone in comparable roles, so that results can be compared fairly.
Explore: Employee engagement strategies that actually work
One employee, one year
Consider an illustrative customer success manager at a 300-person company.
In January, she and her manager agree four goals, three tied to retention and one to a development skill, and record them in the system. Each month, their one-to-one includes a few minutes on goal progress, and her manager notes two examples of strong work. In April, July, and October, short quarterly check-ins adjust one goal when a product launch slips.
In December, she writes a self-assessment, and her manager drafts an assessment from the year’s notes rather than from memory. In January, managers across customer success compare ratings in a calibration session and find one team rating more generously than the others, so they align the standard before any review conversation happens. In February, her review holds no surprises. In March, her result informs her increment and a development plan, and the next goals start from what the year taught them.
Notice what the example does not contain: a surprise. Every stage left a record, calibration happened before the conversation rather than after it, and pay followed the assessment instead of racing ahead of it.
Where the performance management cycle breaks
- Managers are not equipped: Frequent conversations do little when managers have not been trained to hold them, and moving from annual to continuous feedback without training often just multiplies awkward conversations.
- The calendar collides: Cycle dates that ignore budget, increment, and hiring calendars leave outcomes with no one to act on them.
- Documentation is thin: Without records through the year, assessments rest on the last few weeks.
- The performance review cycle becomes a form, not a conversation: Completion rate turns into the metric, and the conversation that was the point gets skipped.
Fixing the performance management process usually means fixing one of these, not adding a sixth stage.
Also read: Tackling bias and building trust in performance management
How to tell whether your cycle is working
You can judge whether your performance management cycle is healthy from a handful of signals, none of which is a completion rate on its own.
- Goal freshness: the share of goals updated at least once during the year.
- Check-in coverage: the share of employees with a recorded progress conversation every quarter.
- Calibration spread: how far average ratings differ between comparable teams before and after calibration.
- Decision timing: the days between the close of the performance review cycle and the pay and promotion decisions it is meant to inform, where a negative number means the review came too late.
- Perceived fairness: whether employees see the process as fair, which Gallup links closely to regular progress checks.
A starter cycle for a team that has none
A simple performance management process can start small and grow.
- Week one: agree on three to five goals per person, each with a measure, and one development goal.
- Month one: schedule regular one-to-ones with a standing slot for goal progress, and put a quarterly check-in on the calendar.
- Every quarter: hold a short check-in with around three questions: what progressed, what is blocked, and what support is needed.
- Year-end: collect a self-assessment and a manager assessment against the original goals, then calibrate across comparable teams.
- After the review: connect outcomes to pay, promotion, and development decisions before those calendars lock.
- Close the loop: ask managers and employees what to cut, and start next year’s goals from the answer.
Conclusion
The performance management cycle works when it is treated as a loop of five connected stages rather than one yearly event. Plan with clear goals, keep them alive with check-ins and continuous feedback, assess fairly, connect results to decisions, and let each cycle improve the next. Most failures trace back to one weak stage, not the whole performance management process.
Akrivia HCM’s performance management system supports every stage, from goal setting and continuous feedback to 360-degree feedback, appraisals, and calibration, in the same platform as the rest of the employee record. If you would like to see a cycle running end to end, Explore Akrivia HCM’s performance management capabilities and book your free demo today to see the complete process in action.
FAQs
When should the cycle start?
Start planning before the fiscal year begins so goals and budgets are set together, and finish assessment before pay decisions lock. Starting after the year is underway leaves the early months without clear goals.
Should ratings be numeric or narrative?
Numeric ratings make comparison and calibration easier, while written narrative explains the reasoning, so most cycles use both. Whichever you choose, define each rating level with behavioral examples.
How long should a check-in last?
Twenty to thirty minutes is usually enough when both sides arrive with progress blockers, and support needs written down. Longer meetings often drift into status updates.