GrowGuide

Performance management cycle: plan, review and develop

Plan a performance management cycle with clear goals, regular conversations and a considered review. Discuss evidence, development and recognition fairly.

Elizabeth de BruijnWritten byElizabeth de Bruijn
5 min readPublished

Key takeaways

  • Agree goals, evidence and the support needed before reviewing performance.
  • Use progress conversations to address blockers and changed priorities.
  • Evaluate results alongside the context and support provided.
  • Explain recognition decisions and carry agreed development into the next cycle.

A performance management cycle organises how a manager and employee agree goals, review progress and discuss development. The rhythm should fit the work and the organisation's policies.[1]

This guide uses four stages: planning, progress conversations, a considered evaluation and recognition with the next cycle. Organisations may use different labels or schedules. Explain your own approach before starting.

Sophie de Vries and Amara Okafor reviewing an open notebook at an office table.
Sophie de VriesReviewing a plan together.

1. Plan goals and support together

Explain the organisation's priorities and discuss the employee's contribution. Set goals that are specific, measurable, achievable, relevant and time-bound.

Agree the support and resources needed as well as the result. Include development goals where a new skill is part of the work.

For an illustrative Implementation Manager in a fintech infrastructure team, a development goal could be to prepare a bounded plan for a fictional customer and explain the assumptions in a supervised review. Agree the scope, approved material and review date. A delayed access approval is a dependency to resolve, not evidence by itself of poor employee performance.

  1. 01

    Result and evidence

    Write down what the employee is expected to deliver and what work evidence you will review together. Choose measures relevant to responsibilities the employee can influence.

  2. 02

    Support and dependencies

    Agree the time, information, access and specialist help required. Identify who will resolve a missing dependency.

  3. 03

    Timing and changes

    Set a review date and explain how to update the goal when priorities or resources change. Keep a record of the revised expectation.

2. Review progress while there is time to respond

Amara Okafor standing beside a whiteboard while Sophie de Vries watches from the table.
Sophie de VriesWorking through a topic together.

Arrange conversations at a rhythm that fits the work. Discuss progress, obstacles and any change in priorities.

Coaching leadership can help explore options and agree a next action. Update the goal when the work changes and make the revised expectation clear.

3. Evaluate results, context and support

Review the agreed goals and relevant evidence with the employee. Ask whether the goal was realistic, what they learned and whether the organisation provided the support promised.

Invite the employee's perspective. A formal review should not be the first time they hear about an ongoing concern.

  1. 01

    Compare with the agreed goal

    Use relevant examples from the period and distinguish what was completed from what is still in progress.

  2. 02

    Hear the employee’s account

    Discuss changed priorities, missing resources and the employee’s explanation before drawing conclusions.

  3. 03

    Agree development actions

    Choose the next skill or practice opportunity, who will provide support and when to review it. The learning culture guide covers the conditions needed for that support.

Use peer feedback carefully

Sophie de Vries and Amara Okafor talking in office armchairs with mugs.
Sophie de VriesMaking time for a conversation.

Ask colleagues who have relevant contact with the work for specific observations. Explain the purpose, scope and how the input will be handled.

Different perspectives can help the discussion, but peer feedback can still contain assumptions or bias. Review it alongside other evidence rather than treating every comment as a finding.

4. Discuss recognition and the next cycle

Explain how recognition, development and any reward decisions follow the organisation's policies. Be clear about what is decided and what needs further approval.

Review the process itself with the employee. Carry the learning and agreed support into the next set of goals.

Sources

  1. CIPD. (2026, January 29). Performance management: An introduction. Definition and regular performance discussions; checked 9 October 2026. https://www.cipd.org/en/knowledge/factsheets/performance-factsheet/

Where CapoFine fits

Support agreed development in Grow

Use Grow for the learning part of an agreed development plan: role-specific modules, interactive activities, pathways and progress tracking.

Frequently asked questions

Questions people ask about this topic.

What are the stages of a performance management cycle?

This guide uses planning, progress conversations, a considered evaluation and recognition with the next cycle. Organisations may use different names or combine stages. Explain your organisation’s goals, evidence, review rhythm and decision process.

How often should managers review progress?

Choose a rhythm that fits the work and your organisation’s policies. Schedule conversations while there is time to resolve blockers or adjust goals, and revisit the schedule when responsibilities or priorities change.

How should peer feedback be used in a performance review?

Ask colleagues with relevant contact for specific observations. Explain the purpose and scope, check assumptions and discuss their input alongside other work evidence and the employee’s account.