In 2023, more than 80% of UK organisations said at least some employees received a formal appraisal or review, yet only 48% of employees had even a basic level of performance management. Just 28% experienced systematic performance management, including objectives, reviews and feedback, according to CIPD research on people management and productivity. The problem isn't a lack of interest in performance. It's the failure to turn good intentions into a reliable workflow.
A modern performance management process should connect business priorities, individual objectives, regular conversations, evidence, development and decisions. It should work for hybrid teams, support consistent management practice and leave a clear record when ratings, progression, reward or corrective action need to be explained.
Table of Contents
- What the Performance Management Process Really Means in 2026
- The Five Core Stages of the Performance Management Process
- From Annual Review to Continuous Performance Management
- KPIs and Metrics That Prove the Process Is Working
- Common Pitfalls and Why Most Programmes Underperform
- How HRManagement365 Supports Each Stage on Microsoft Power Platform
- UK and EU Compliance, Data Protection and Getting Started
What the Performance Management Process Really Means in 2026
The performance management process is the end-to-end operating cycle for managing contribution and capability. It starts when an organisation translates strategic priorities into team and individual expectations, then continues through progress monitoring, feedback, development, formal assessment and action on results.
That definition matters because an annual appraisal is only one event inside the cycle. A form completed at year-end can't compensate for unclear objectives, undocumented conversations or development actions that were never revisited. The process must help managers and employees understand what success means, assess progress against evidence and adjust direction when business conditions change.
A UK process with a persistent execution gap
The UK has clear historical roots in formal appraisal systems that spread from the US during the 1920s and 1930s. The term “performance management” first appeared in the 1970s and became a recognised process in the latter half of the 1980s. CIPD survey work in 1991 found widespread confusion about what the term meant, which reflected the move from simple appraisal forms towards a broader management process. These historical details are documented in Performance Management in Action.
The field has matured, but implementation remains uneven. In the same CIPD evidence, 95% of respondents identified driving organisational performance as a key objective, while only 45% said their programme achieved that objective. That gap points towards workflow design, manager capacity and evidence quality rather than employee hostility to feedback.
Practical rule: If a manager can't see the current objective, record a conversation and identify the next action without leaving the HR system, the process is too dependent on memory.
For HR directors, the practical blueprint is straightforward. Define the stages, make each stage produce a tangible record, give managers lightweight tools in their normal Microsoft working environment and use reporting to identify missing activity. Organisations reviewing the wider employee lifecycle may also benefit from this blog post on hiring, because performance management starts with role clarity and realistic expectations established during recruitment.
The Five Core Stages of the Performance Management Process
A strong process has five connected stages. Each one should create an artefact that the next stage can use. If a conversation produces no objective, note, decision or action, it may have been useful, but it hasn't become dependable organisational evidence.
Goal setting creates direction
The first output is a set of SMART objectives and key results. Managers should connect individual goals to team priorities and corporate objectives, while recording measures, ownership, timeframes, dependencies and any assumptions.
Avoid storing goals solely in Word documents, email or local spreadsheets. Structured records allow HR to report on alignment, identify duplicated objectives and see where priorities have changed. A Dataverse-based model can also support goal weights, status, evidence and approval history.
Continuous check-ins create a current record
A check-in is a working conversation, not a miniature annual review. The output should include the meeting date, agenda, progress summary, obstacles, support required and agreed actions.
Teams can provide the familiar meeting environment, while an HR application can capture the relevant notes against the employee record. The design decision is important. Managers need enough structure to create useful evidence, but not so much administration that they avoid recording the conversation.
Continuous feedback captures contribution in context
Feedback should come from the people who observe the work. That can include manager coaching, peer recognition, upward feedback and, where appropriate, structured 360-degree input.
The record needs context. A short note should identify the behaviour or outcome, explain its impact and state whether follow-up is required. This creates a more balanced evidence base than relying on a manager's memory at year-end.
Formal reviews produce a defensible assessment
The formal review consolidates objectives, evidence, feedback, the employee's perspective and the manager's assessment. Its outputs normally include a rating or assessment, summary narrative, development priorities and a sign-off trail.
HRManagement365 can be configured to route reviews through manager, skip-level and committee approvals where that governance model is required. Organisations comparing different approaches can use this resource to compare performance management frameworks, then select the controls that fit their culture and regulatory context.
Development plans turn findings into action
A development plan should answer three questions. What capability needs to improve or grow? Which activity will build it? How will the manager and employee know that progress has occurred?
The resulting record might link to learning, mentoring, a stretch assignment, a competency gap or a future role. It should return to the next check-in rather than disappear after the review. The five stages work only when development is treated as an operating commitment, not a closing paragraph in an appraisal form.
From Annual Review to Continuous Performance Management
The annual model concentrates too much meaning into one meeting. Feedback arrives late, evidence is reconstructed from memory and an employee may hear concerns for the first time when a rating is already being discussed. That creates unnecessary tension for both parties.
A continuous model distributes the work across the year. Managers clarify expectations early, discuss progress while there is still time to respond, record evidence close to the event and revisit development actions before priorities move again.
Hybrid work makes this shift operationally necessary. Managers can't depend on incidental office observation to understand contribution, collaboration or obstacles. They need deliberate points of contact, clear records and consistent expectations across UK and EU locations.
Continuous doesn't mean constant
Continuous performance management isn't a demand for endless meetings. It is a control loop:
- Set a direction.
- Observe progress and capture evidence.
- Discuss obstacles and provide feedback.
- Adjust objectives or support.
- Review outcomes and agree development.
- Feed decisions back into the next cycle.
The control loop should be proportionate. A project-based role may need objectives reviewed when deliverables change, while a regulated operational role may require more formal evidence and approval. The process should adapt without losing version history.
HRManagement365 can support organisations that want to replace an isolated annual event with connected objectives, conversations and review records. Its practical value depends on configuration, manager adoption and governance, not on switching on another form. For a manager-focused view of the operational change, see performance reviews for managers.
UK guidance for formal performance discussions supports a continuous control-loop approach, recommending a minimum of three formal discussions each year, objective setting, a mid-year review and an end-of-year review, alongside informal check-ins, as described in Parliamentary performance management advice. The point isn't to create a rigid calendar. It is to ensure that evidence, support and corrective action don't wait until the final conversation.
KPIs and Metrics That Prove the Process Is Working
A Power BI dashboard should show whether the process is operating, not merely how many forms have been submitted. HR directors need measures that expose quality, timeliness, participation and follow-through.
Four useful KPI categories
Objective quality tests whether employees have meaningful direction. Useful measures include the proportion of objectives with a defined outcome, the level of alignment to team priorities, the distribution of objective weights and the number of goals changed without an explanation. A high completion rate can still mask poor quality if managers copy generic objectives across a team.
Review cadence shows whether conversations happen when promised. Track employees with current goals, completed check-ins, overdue reviews and the time since the last recorded one-to-one. A dashboard should distinguish an overdue conversation from a conversation that occurred but wasn't recorded.
Feedback frequency measures whether evidence is broad enough to support a fair assessment. Consider the reach of 360-degree feedback, peer recognition activity, manager response time and the balance between positive coaching and corrective feedback. These measures need careful interpretation because low volume may reflect poor adoption, limited opportunity to observe work or an unsuitable process design.
Development execution tests whether the organisation acts on identified needs. Track active plans, completed actions, learning activity and internal movement, but don't treat course attendance as proof of capability. Managers should record the applied behaviour, project outcome or demonstrated skill that shows whether development helped.
Performance Management KPIs by Category
| KPI Category | Example Metric | Realistic Target | Data Source |
|---|---|---|---|
| Objective quality | Objectives with measurable outcomes and owner | Set an internal baseline, then improve quality through review | Dataverse goal records |
| Review cadence | Employees with a current goal and recent check-in | Agree a service level that managers can sustain | Power Automate and review records |
| Feedback frequency | Employees receiving documented feedback from more than one source | Set a role-sensitive participation target | Feedback entity and Teams activity |
| Development execution | Development actions completed by the agreed date | Use plan type and role to set different expectations | Development records and learning integration |
Don't publish targets until the underlying definitions are stable. A “completed check-in” should mean more than a calendar appointment. A “current goal” should include an owner, status and review date.
reporting in HR becomes a design issue rather than a dashboard exercise. HR teams should model the data in Dataverse first, then expose trusted measures through Power BI. The same discipline applies to workforce planning, including specialist recruitment decisions such as identifying the best place to hire SDRs. Different decisions need different measures, and copied metrics rarely provide useful context.
Common Pitfalls and Why Most Programmes Underperform
Most performance management programmes don't fail because managers dislike meaningful conversations. They fail because the organisation gives managers an administrative process that is fragmented, slow and difficult to evidence.
UK research reported in HR Magazine performance framework material found that only 36% of companies considered their performance management process effective. The same evidence identified several operational barriers: 45% said managers didn't see the value, 53% said managers didn't have time to do it well, 32% said too much time was spent filling in forms, and 69% said there was too little time collecting colleague feedback.
The workflow failures behind the symptoms
Objectives buried in Word documents become invisible. Evidence stored in personal inboxes becomes inaccessible when a manager changes role. Calibration committees relying on memory create inconsistency, while development plans often vanish once the review has been signed off.
Spreadsheets and email can support a small pilot, but they become weak systems of record as the organisation adds locations, managers, approval layers and data protection requirements. They make version control difficult and encourage each business unit to invent its own interpretation of the process.
A Dataverse-backed design addresses the root problem by giving goals, notes, feedback, approvals and development actions defined records with permissions and history. That doesn't remove judgement. It makes the judgement easier to inspect and challenge.
Design test: If HR can't identify who changed an objective, why it changed, who approved a rating and what support followed, the process isn't auditable enough for consequential decisions.
The answer isn't to add more mandatory fields. It is to remove duplicate entry, surface the workflow in Teams, pre-fill information where possible and give managers prompts that match the conversation they need to have. Manager enablement means training, clear guidance and tools that reduce friction. Culture improves when the system makes the desired behaviour practical.
How HRManagement365 Supports Each Stage on Microsoft Power Platform
HRManagement365.com is a UK and EU HR solution powered by Hubdrive and Microsoft technology. It extends Hubdrive and Microsoft with implementation expertise, integrations, customisations, workflows and HR applications. The solution is built in Power Platform, Dynamics 365 and Dataverse, with the option to develop customer-specific functionality where standard configuration doesn't cover the process.
The platform boundary should be clear. Microsoft Power Platform supplies the foundation for apps, automation, data and reporting. Teams provides a familiar collaboration surface, while Power BI turns governed data into management insight. HRManagement365 adds the HR process design, configuration and custom development needed to make those components work together.
Stage-by-stage implementation
Goal setting can use Dataverse tables for objectives, key results, owners, weights, dates and status. HRManagement365 can add a custom goal-cascade model and SMART scoring where an organisation needs structured alignment beyond standard records.
Check-ins can be supported through Power Automate reminders, Teams meeting templates and Power Apps forms. A customised workflow can save agendas, notes and actions to the employee record, subject to the organisation's permissions and retention design.
Feedback may require a custom Praise and Feedback entity surfaced through Teams. That structure can capture the source, context, visibility and follow-up requirement instead of leaving important evidence in chat history or email.
Formal reviews can run through Power Apps-driven forms with role-based approvals, evidence attachments, sign-off and moderation controls. The exact routing should reflect the organisation's governance model, especially where ratings influence progression or reward.
Development planning can link agreed actions to learning providers, competencies or internal opportunities. Power BI can then show plan status, overdue actions and capability themes, provided the semantic model remains governed and current.
HRManagement365 can also provide implementation and consultancy, custom approval processes, integrations, employee lifecycle automation, reporting and Power BI services, plus connections with Dynamics 365 Business Central and Finance & Operations. The relevant performance capabilities are described through HRManagement365 talent and performance management.
Trade-offs to make explicit
A Microsoft-centric design brings licensing costs per user, change management effort and an ongoing obligation to maintain the Power BI semantic model. Customisation also creates ownership responsibility. Document the data model, flows, security roles and support model before production deployment.
UK and EU Compliance, Data Protection and Getting Started
Performance records need a governance model before they need a dashboard. UK GDPR and EU GDPR share core principles, but organisations must still assess the relevant national employment, works council, retention, consultation and employee-monitoring requirements in each EU member state. A UK parent and an EU subsidiary shouldn't assume that one policy automatically satisfies every local obligation.
The lawful basis for processing performance data will depend on the purpose and context. Organisations commonly assess legitimate interest or contract performance, but HR and privacy teams should document the reasoning, minimise access and separate formal records from informal material. Ratings, disciplinary outcomes and agreed development decisions may belong in controlled HR records. Informal Teams feedback may need different access, retention and visibility rules.
Cross-border access matters where UK and EU entities share a Dataverse environment. Confirm the controller and processor roles, transfer arrangements, access locations, security model, retention schedule and employee information provided through the privacy notice. Don't copy every Teams conversation into the employee record. Capture only the evidence required for the defined HR purpose.
Broader lifecycle compliance
The same structured data model can carry records beyond performance. The UK Home Office states that employers must complete a right to work check before employment and repeat it shortly before a time-limited permission expires, as set out in the employer's right to work guidance.
Employers must obtain original documents or use the online share code route where applicable, check documents in the person's presence, retain copies that can't later be altered and keep those copies during employment and for two years after the employee stops working. The employer must also record the check date and repeat the check when permission is time-limited, according to the UK right to work code of practice. A Dataverse workflow can support evidence capture, expiry tracking and reminders, but HR still owns the compliance decision.
A controlled rollout
Use a limited rollout rather than attempting every HR process at once.
- Weeks one to two: Model goals, review templates, permissions and retention rules in Dataverse.
- Weeks three to four: Pilot check-ins with one business unit and Teams integration.
- Weeks five to eight: Enable managers, validate Power BI measures and resolve data-quality issues.
- Weeks nine to twelve: Extend formal reviews and connect development plans.
A faster rollout increases compliance exposure, so keep the pilot scope controlled. Test access, evidence capture, reporting definitions and local UK or EU requirements before expanding the process.
Speak to an HRManagement365 specialist to assess your current performance management workflow and design a Microsoft-based process with structured objectives, evidence capture, approvals, Power BI reporting and development actions. Discover how HRManagement365, powered by Hubdrive and Microsoft, can help improve and automate your HR processes across the UK and EU, then visit HR Management 365 or phone +44 1522 508096 today. Send us a message through the HRManagement365 contact page.
