Goals are too broad
Employees receive general responsibilities rather than specific outcomes, measures or priorities they can act on.
PeopleOS · Performance Management
Build a performance rhythm managers can actually run.
PathWeave helps organisations design performance management around clear expectations, regular manager conversations, evidence, calibration, development and follow-through — not just an annual appraisal cycle.
The operating principle
Performance management is a management system, not an HR form.
The system works only when managers can set expectations, observe performance, discuss evidence, make fair decisions and follow through consistently.
HR should design and govern the framework, but managers need to own the conversations. The process should be simple enough to use and strong enough to support pay, development, progression and accountability decisions.
Where systems usually fail
Most performance problems are operating problems, not form-design problems.
Managers wait too long
Feedback is saved for a formal review, so course correction happens after the work or behaviour has already affected the team.
Evidence is inconsistent
Ratings depend on memory, visibility or manager style instead of a common expectation about what evidence matters.
Calibration is missing
Managers use the same rating scale differently, making cross-team decisions feel arbitrary even when intentions are good.
Development is disconnected
Development plans are created after reviews but are not tied to role expectations, next-level capability or manager follow-through.
HR owns the process
Managers complete forms because HR asks them to, rather than seeing performance as part of how they run their teams.
System components
What a practical performance system needs
01
Clear expectations
Role outcomes, goals, standards and behaviours translated into language employees and managers can use.
02
Manager check-ins
A realistic rhythm for feedback, prioritisation, support and course correction rather than one large annual conversation.
03
Evidence
Simple evidence sources that reduce memory bias and make performance discussions more concrete.
04
Calibration
Structured cross-manager review where necessary to improve consistency and reduce rating drift.
05
Development
Specific development priorities connected to the role and next-level capability, with ownership and follow-through.
06
Consequences and recognition
Clear links to recognition, progression, corrective action and other people decisions without turning the system into a scoring exercise.
Manager ownership
Define what HR designs and what managers must do.
HRDesigns the framework, tools, governance, communication and consistency checks.
ManagersSet expectations, observe, coach, document evidence, discuss performance and follow through on actions.
LeadershipSets the standard for accountability and ensures performance decisions reflect business priorities and organisational values.
EmployeesUnderstand expectations, bring evidence, ask for support and own agreed actions and development commitments.
Design sequence
Start with roles and management behaviour before choosing ratings.
1. Clarify rolesDefine the outcomes and responsibilities that performance discussions should actually evaluate.
2. Define expectationsTranslate business priorities into role-relevant goals, standards and behavioural expectations.
3. Set the rhythmChoose a realistic cadence for check-ins, formal reviews and calibration based on the organisation's management capacity.
4. Equip managersProvide simple tools and guidance for feedback, evidence, difficult conversations and development discussions.
5. Connect decisionsClarify how performance information informs recognition, progression, development and corrective action without pretending one score makes every decision.
Different stages need different systems
A 40-person SME should not copy a 4,000-person appraisal process.
Smaller organisations often need fewer forms and more manager discipline: clear expectations, monthly or quarterly conversations and a simple record of actions. As the organisation grows, calibration, role levels, structured development and stronger governance may become necessary.
The same principle applies to startups, technology teams, multi-location organisations and GCCs: the system should reflect role complexity, management maturity and decision needs, not a generic corporate template.
For broad growth-stage HR needs, see HR Consulting for SMEs.
Connected PeopleOS work
Performance systems depend on role clarity and manager capability.
If roles and decision ownership are unclear, start with Organisation Design & Role Clarity.
If the issue is broader than performance alone, HR Transformation connects performance with the wider HR operating system.
For system workflow, records and automation, see HR Operations & HRMS.
Experience
Experience behind the approach
Renu Dhanopia Sharma
Founder · leads PeopleOS
PeopleOS draws on HR leadership, consulting and outsourced HR delivery experience across performance management, organisation structures, policies, recruitment, HR operations and people systems.
About the foundersFocused first step
Review the performance rhythm before redesigning the form.
The HR Health Check can review Performance Management as a standalone area: what managers currently do, where inconsistency appears and what to fix first.
Make performance conversations more useful and more consistent.
Build a system that managers can operate throughout the year.