flowchart TD
PM["PERFORMANCE<br>MANAGEMENT"] --> GST["Goal-Setting Theory<br>Locke & Latham, 1990<br>────────────<br>Specific, challenging goals<br>with feedback drive<br>higher performance"]
PM --> ET["Expectancy Theory<br>Vroom, 1964<br>────────────<br>Motivation = Expectancy<br>× Instrumentality<br>× Valence"]
PM --> ST["Systems Theory<br>Deming, 1986<br>────────────<br>94% of variation is<br>systemic, not individual"]
PM --> BSC["Balanced Scorecard<br>Kaplan & Norton, 1992<br>────────────<br>Four perspectives:<br>Financial, Customer,<br>Process, Learning"]
PM --> RT["Reinforcement Theory<br>Skinner, 1953<br>────────────<br>Behaviour shaped by<br>consequences; timely<br>rewards sustain performance"]
PM --> SET["Social Exchange<br>Blau, 1964; Rousseau, 1995<br>────────────<br>Reciprocal exchange:<br>fairness drives trust,<br>engagement, commitment"]
style PM fill:#0D1B2A,color:#fff
style GST fill:#028090,color:#fff
style ET fill:#00A896,color:#fff
style ST fill:#015F6B,color:#fff
style BSC fill:#D4A843,color:#fff
style RT fill:#E8683F,color:#fff
style SET fill:#3A4F5E,color:#fff
1 Meaning, Uses and Purpose of Performance Management
After completing this chapter, you will be able to:
- Define performance management and distinguish it from related HR practices.
- Trace the historical evolution of performance management from early merit rating to contemporary continuous feedback models.
- Identify and explain the five primary purposes performance management serves within organisations.
- Apply six foundational theoretical frameworks to understand why and how performance management works.
- Recognise common misconceptions and articulate the characteristics that distinguish effective systems.
1.1 Introduction
Performance management stands as one of the most consequential and most debated processes in contemporary human resource management. It shapes how organisations define success, how managers develop their people, and how employees experience their working lives. Yet despite its centrality, it remains poorly understood in many organisations, often reduced to a once-a-year appraisal ritual that satisfies neither managers nor employees.
1.2 Defining Performance Management
1.2.1 Conceptual Foundations
Scholars have approached performance management from several complementary angles, each adding a dimension that a single definition cannot fully capture.
Performance management is “a systematic process for improving organizational performance by developing the performance of individuals and teams.”
This definition emphasises two features: it is systematic (structured, recurring, not ad hoc) and purposive (its ultimate aim is organisational performance through individual and team development).
Performance management is “an ongoing communication process, undertaken in partnership between an employee and their immediate supervisor, that involves establishing clear expectations and understanding.”
Bacal highlights the relational dimension: PM is not done to employees but with them. This participative orientation is critical to both system design and effectiveness (J. A. Colquitt, 2001; J. Greenberg, 1986).
T. V. Rao (2008) positions PM as a mechanism for achieving organisational excellence through a complete cycle: plan, monitor, develop, rate, and reward. This cyclical conceptualisation has become one of the standard frameworks in both academic and practitioner literature.
S. R. Kandula (2006) argues that PM must link individual performance to the organisation’s mission and strategic objectives. When disconnected from strategy, PM degenerates into a bureaucratic exercise; when tightly coupled with strategy, it becomes a powerful lever for alignment and competitive advantage.
P. Chadha (2003) captures the essential insight in the very title of his work: PM is about performing, not just appraising. Attention must shift from the evaluative event to the continuous process of enabling and sustaining performance in everyday organisational life.
1.2.2 A Working Definition
Synthesising these perspectives, we define performance management as:
A continuous, systematic process through which an organisation aligns individual and team performance with its strategic objectives by establishing clear expectations, providing ongoing feedback, developing employee capability, evaluating results, and recognising contributions, all conducted within a framework of mutual communication and shared accountability.
Four features are essential:
- Continuous: not episodic; its essence lies in day-to-day manager-employee interaction.
- Strategic: connecting individual efforts to organisational purposes.
- Developmental: concerned with building future capability, not just evaluating past performance.
- Mutual: requiring active partnership from both managers and employees.
1.3 Historical Evolution of Performance Management
1.3.1 Early Origins: Merit Rating and Scientific Management
F. W. Taylor (1911)’s time-and-motion studies established that work could be measured and optimised, laying the groundwork for formal evaluation. During World War I, the U.S. military introduced “merit rating” systems to assess officers; these practices migrated into industry during the 1920s and 1930s (K. R. Murphy & J. N. Cleveland, 1995).
Early systems were trait-based, evaluating dependability, initiative, and cooperativeness, but were plagued by halo effects, rater bias, and poor interrater reliability (F. J. Landy & J. L. Farr, 1980).
1.3.2 The Behaviorist Turn: 1950s to 1970s
Researchers moved from trait-based to behaviour-based approaches. Behaviourally Anchored Rating Scales (P. C. Smith & L. M. Kendall, 1963) and Behavioral Observation Scales (G. P. Latham & K. N. Wexley, 1977) grounded evaluation in observable, job-related behaviours.
Simultaneously, P. F. Drucker (1954)’s Management by Objectives (MBO) introduced a results-oriented dimension, shifting focus from how employees behaved to what they achieved. MBO embedded goal-setting into managerial practice decades before E. A. Locke & G. P. Latham (1990) provided its theoretical justification.
1.3.3 The Systems Perspective: 1980s to 1990s
W. E. Deming (1986)’s quality management philosophy challenged individual performance evaluation, arguing it destroyed teamwork and misattributed systemic outcomes to individuals. He estimated that approximately 94 per cent of performance variation is attributable to the system rather than to individual employees.
This catalysed a reconceptualisation of PM as an integrated system. R. S. Kaplan & D. P. Norton (1992)’s Balanced Scorecard reinforced this shift by translating strategic objectives into measurable indicators across four dimensions: financial, customer, internal process, and learning and growth.
1.3.4 Contemporary Practice: 2000s to Present
Research has documented widespread dissatisfaction with annual review systems (P. Cappelli & A. Tavis, 2016; E. D. Pulakos, 2009). Prominent organisations including Adobe, Deloitte, Microsoft, and GE abandoned annual ratings in favour of continuous, forward-looking performance conversations.
Key drivers include the accelerating pace of business, technology enabling real-time feedback, deeper understanding of feedback psychology, and the shift toward coaching-oriented cultures. As H. Aguinis (2013) observes, the most effective PM systems emphasise ongoing dialogue over retrospective evaluation.
1.4 Purposes of Performance Management
Performance management serves multiple, interconnected purposes. J. N. Cleveland et al. (1989) empirically demonstrated that organisations use performance processes for diverse and sometimes conflicting purposes. Synthesising their work with M. Armstrong (2009), H. Aguinis (2013), and S. R. Kandula (2006), five broad categories emerge.
Performance management aligns individual and team effort with organisational objectives by cascading goals from strategy through departments down to individuals. When employees understand how their work contributes to strategic goals, they direct effort toward high-value activities (H. Aguinis, 2013; S. R. Kandula, 2006).
The Balanced Scorecard (R. S. Kaplan & D. P. Norton, 1996) provides the structured methodology for this cascading, ensuring performance is monitored across multiple strategically relevant dimensions.
Evidence: M. A. Huselid (1995) found that strategy-linked PM produced significantly higher productivity, lower turnover, and greater financial performance. A meta-analysis by J. Combs et al. (2006) confirmed the positive relationship between high-performance work systems and organisational outcomes.
Performance management provides the informational basis for compensation, promotions, transfers, reductions in force, and legal documentation (R. Bacal, 1999; J. N. Cleveland et al., 1989).
This administrative use creates a persistent tension: when employees perceive PM as primarily an instrument of control, they become defensive and disengage from its developmental aspects (W. R. Boswell & J. W. Boudreau, 2002).
Key finding: H. H. Meyer et al. (1965) at General Electric demonstrated that combining salary discussions with developmental feedback in one conversation undermined both purposes. Employees focused on defending their rating rather than planning for improvement. Many scholars now recommend separating the two temporally or structurally (M. Armstrong, 2009; P. Chadha, 2003).
The developmental purpose focuses on identifying strengths and improvement areas, providing feedback that facilitates learning, and creating opportunities for skill development and career advancement (H. Aguinis, 2013).
This is perhaps the most valued purpose from the employee’s perspective, as people consistently report wanting feedback that helps them improve and grow (M. London, 2003). It is served through individual development plans, coaching and mentoring, and 360-degree feedback processes (S. R. Kandula, 2006; T. V. Rao, 2008).
PM establishes clear expectations, gives employees information about how their performance is perceived, and creates structured opportunities for dialogue (R. Bacal, 1999; P. Chadha, 2003).
Without clear communication of expectations, employees cannot be held accountable for outcomes they did not know were expected. Without dialogue, PM becomes a one-directional imposition rather than a collaborative process (M. Armstrong, 2009).
Justice perspective: Employees’ procedural justice perceptions are significantly influenced by the quality of communication they receive and the opportunity to voice their perspective (J. A. Colquitt, 2001; J. Greenberg, 1986).
PM enhances engagement, accountability, and commitment through clear criteria, constructive feedback, and fair rewards (E. L. Deci & R. M. Ryan, 2000; W. H. Macey & B. Schneider, 2008).
When employees feel their contributions are recognised, when they have growth opportunities, and when they are treated fairly, they bring greater energy, creativity, and commitment to their work. This purpose cuts across and amplifies all four others.
1.5 Operational Uses of Performance Management Data
Beyond broad purposes, PM data serves specific operational uses across the HR function (H. Aguinis, 2013; R. Bacal, 1999; S. R. Kandula, 2006):
| Use | Description |
|---|---|
| Workforce planning | Identifies capability gaps and surpluses to inform recruitment and redeployment |
| Compensation decisions | Determines merit increases, bonuses, and variable pay |
| Promotion and advancement | Identifies employees ready for increased responsibility |
| Training needs analysis | Diagnoses skill gaps requiring developmental investment |
| Succession planning | Builds leadership pipelines by identifying high-potential talent |
| Legal documentation | Creates defensible records of expectations, evaluations, and improvement efforts |
| Selection validation | Uses performance data as a criterion to validate recruitment methods |
| Organisational development | Aggregates PM data to diagnose systemic issues and inform strategic change |
When the same data simultaneously informs compensation, development plans, and succession pipelines, errors and biases are amplified across multiple decision streams, making data quality a strategic priority.
1.6 Theoretical Foundations
Six foundational theories inform effective performance management design. Together they explain why certain practices work, how to motivate performance, and what happens when systems are poorly designed.
E. A. Locke & G. P. Latham (1990)’s goal-setting theory is among the most empirically validated theories in organisational psychology. Its core propositions, confirmed across hundreds of studies (E. A. Locke & G. P. Latham, 2006):
- Specific goals outperform vague intentions such as “do your best.”
- Difficult goals outperform easy goals, provided commitment and ability are adequate.
- Feedback is essential for sustained goal pursuit.
For PM design: Goals must be specific and measurable, sufficiently challenging, accompanied by regular feedback, and jointly accepted by the employee. For complex tasks, learning goals and strategic support are needed alongside outcome goals (E. A. Locke & G. P. Latham, 2002).
V. H. Vroom (1964)’s expectancy theory holds that motivation is a product of three beliefs:
- Expectancy: effort will lead to performance.
- Instrumentality: performance will lead to outcomes.
- Valence: those outcomes are valued.
For PM design: PM directly influences all three beliefs by clarifying the effort-performance link through goal-setting, establishing the performance-outcome link through reward systems, and identifying meaningful outcomes through career discussions (M. Armstrong, 2009; S. R. Kandula, 2006).
W. E. Deming (1986) argued that approximately 94 per cent of performance variation is attributable to the system, not to individual employees. PM systems that evaluate individuals for outcomes largely determined by processes, management decisions, and organisational design are fundamentally misguided.
For PM design: Effective systems attend to both individual behaviour and the organisational systems that enable or constrain performance (R. Bacal, 1999). Performance problem diagnosis should begin with systemic factors rather than individual deficiency.
R. S. Kaplan & D. P. Norton (1992) and R. S. Kaplan & D. P. Norton (1996)’s Balanced Scorecard addresses overreliance on financial metrics by proposing measurement across four perspectives:
- Financial: revenue, profit, and return on investment.
- Customer: satisfaction, retention, and value creation.
- Internal Process: quality, efficiency, and innovation.
- Learning and Growth: capability, engagement, and knowledge.
For PM design: The Balanced Scorecard template ensures employee goals reflect the full range of strategically important outcomes, balancing lagging indicators (past results) with leading indicators (drivers of future performance).
B. F. Skinner (1953)’s reinforcement theory holds that behaviour followed by positive consequences tends to be repeated. Performance-contingent rewards such as merit pay, bonuses, recognition, and promotions function as positive reinforcers.
Evidence: A. D. Stajkovic & F. Luthans (1997) demonstrated that reinforcement-based interventions produced an average performance improvement of 17 per cent (d = .51). Their subsequent research (A. D. Stajkovic & F. Luthans, 2003) found that money, feedback, and social recognition produced the strongest effect when used in combination. Reinforcement is most effective when it is timely, specific, and clearly linked to the behaviour being reinforced (H. Aguinis, 2013).
P. M. Blau (1964)’s social exchange theory and D. M. Rousseau (1995)’s psychological contract theory conceptualise employment as a reciprocal exchange in which employees contribute effort, skill, and loyalty in return for compensation, development, recognition, and purpose.
For PM design: When PM processes are perceived as fair, transparent, and developmental, they strengthen the psychological contract and foster trust, engagement, and commitment. When perceived as arbitrary or punitive, they erode the contract and produce cynicism and turnover (W. R. Boswell & J. W. Boudreau, 2002; E. W. Morrison & S. L. Robinson, 1997).
1.6.1 Summary of Theoretical Frameworks
1.7 The Role of Feedback: A Critical Nuance
A. N. Kluger & A. DeNisi (1996) conducted a comprehensive meta-analysis of 607 feedback intervention effects and found that while feedback improved performance on average (d = .41), over one-third of feedback interventions actually decreased performance.
Their Feedback Intervention Theory explains this finding: feedback that directs attention to the task and how to improve it tends to enhance performance, while feedback that directs attention to the self such as personal criticism or ego-threatening evaluations tends to diminish it.
Implication for PM design: How feedback is delivered matters as much as whether it is delivered. Systems prioritising specific, task-focused, forward-looking feedback generate positive outcomes; systems emphasising personal evaluation and ranking risk undermining the very performance they seek to improve. This finding strongly supports the shift from annual evaluative reviews toward continuous, coaching-oriented performance conversations, a theme developed in Chapters 9, 12, and 16.
1.8 Conceptual Models of Performance Management
The following models synthesise the key ideas of this chapter from complementary perspectives, offering an integrated mental architecture for understanding how PM operates.
1.8.1 Model 1: Strategic Performance Alignment
flowchart TD
A["Organisational Vision<br>& Mission"] --> B["Business Strategy"]
B --> C["Departmental Goals"]
C --> D["Individual KRAs & KPIs"]
D --> E["Performance Monitoring<br>& Measurement"]
E --> F["Feedback &<br>Development"]
F --> G["Rewards &<br>Recognition"]
G --> H["Organisational Performance<br>Outcomes"]
H -.->|"Strategic Review<br>& Recalibration"| A
style A fill:#0D1B2A,color:#fff
style B fill:#028090,color:#fff
style C fill:#00A896,color:#fff
style D fill:#02C39A,color:#fff
style E fill:#D4A843,color:#fff
style F fill:#E8683F,color:#fff
style G fill:#3A4F5E,color:#fff
style H fill:#0D1B2A,color:#fff
The dotted feedback loop reflects the dynamic nature of strategy: performance data informs strategic recalibration. A direct line of sight runs from organisational vision all the way to individual KRAs and back (H. Aguinis, 2013; R. S. Kaplan & D. P. Norton, 1996).
1.8.2 Model 2: The Performance Management Cycle
flowchart LR
A["Goal Setting<br>& Planning"] --> B["Continuous<br>Monitoring"]
B --> C["Feedback<br>& Coaching"]
C --> D["Formal Performance<br>Review"]
D --> E["Reward & Development<br>Decisions"]
E --> A
style A fill:#028090,color:#fff
style B fill:#00A896,color:#fff
style C fill:#D4A843,color:#fff
style D fill:#E8683F,color:#fff
style E fill:#0D1B2A,color:#fff
Performance management is never finished; it is an ongoing rhythm of planning, supporting, evaluating, and renewing. The circular structure reinforces that the formal review is one stage within a much larger continuous process (M. Armstrong, 2009; T. V. Rao, 2008).
1.8.3 Model 3: Multi-Dimensional Purpose
flowchart TD
PM["PERFORMANCE<br>MANAGEMENT"] --> SP["Strategic Purpose:<br>Aligning individual performance<br>with organisational strategy"]
PM --> AP["Administrative Purpose:<br>Supporting compensation,<br>promotion & HR decisions"]
PM --> DP["Developmental Purpose:<br>Identifying training needs<br>and career growth"]
PM --> CP["Communication Purpose:<br>Clarifying expectations<br>and performance standards"]
PM --> MP["Motivational Purpose:<br>Enhancing engagement,<br>accountability & commitment"]
style PM fill:#0D1B2A,color:#fff
style SP fill:#028090,color:#fff
style AP fill:#00A896,color:#fff
style DP fill:#D4A843,color:#fff
style CP fill:#E8683F,color:#fff
style MP fill:#3A4F5E,color:#fff
An effective system balances all five dimensions. Organisations that over-invest in any single purpose, typically the administrative one, at the expense of others produce systems that measure but do not manage (J. N. Cleveland et al., 1989; E. L. Deci & R. M. Ryan, 2000).
1.8.4 Model 4: Input–Process–Output
flowchart TD
A["INPUTS<br>────────────<br>Organisational Strategy<br>Job Roles & Descriptions<br>Competency Frameworks<br>Resources & Support Systems"]
B["PROCESS<br>────────────<br>Goal Setting & Alignment<br>Continuous Monitoring<br>Feedback & Coaching<br>Formal Evaluation<br>Development Planning"]
C["OUTPUTS<br>────────────<br>Improved Individual Performance<br>Employee Development & Growth<br>Informed Talent Decisions<br>Organisational Effectiveness<br>Enhanced Engagement"]
A --> B --> C
C -.->|"Feedback Loop"| A
style A fill:#028090,color:#fff
style B fill:#0D1B2A,color:#fff
style C fill:#E8683F,color:#fff
The feedback loop reflects W. E. Deming (1986)’s principle of continuous improvement: outputs must feed back to refine the system’s inputs and processes, not merely accumulate as records.
1.8.5 Model 5: Integrative Framework of Prescribed Perspectives
flowchart TD
CENTER["PERFORMANCE<br>MANAGEMENT<br>An Integrated<br>Discipline"] --> BAC["Bacal (1999)<br>────────────<br>Communication &<br>Partnership:<br>PM as ongoing dialogue<br>between manager<br>and employee"]
CENTER --> RAO["Rao (2008)<br>────────────<br>Organisational<br>Excellence:<br>Plan → Monitor →<br>Develop → Rate →<br>Reward cycle"]
CENTER --> ARM["Armstrong (2009)<br>────────────<br>Systematic Process:<br>Developing individual<br>& team performance<br>for organisational<br>improvement"]
CENTER --> CHA["Chadha (2003)<br>────────────<br>Performing, Not<br>Just Appraising:<br>Continuous enablement<br>over episodic<br>evaluation"]
CENTER --> KAN["Kandula (2006)<br>────────────<br>Strategy-Intervention-<br>Driver:<br>Linking individual<br>performance to<br>mission & objectives"]
style CENTER fill:#0D1B2A,color:#fff
style BAC fill:#028090,color:#fff
style RAO fill:#00A896,color:#fff
style ARM fill:#D4A843,color:#fff
style CHA fill:#E8683F,color:#fff
style KAN fill:#3A4F5E,color:#fff
1.9 Case Studies
Infosys implemented a Balanced Scorecard approach that cascaded four organisational strategic themes, namely client value, operational excellence, learning and innovation, and financial performance, into individual performance plans. Each employee’s goals were explicitly linked to one or more scorecard dimensions, creating a direct line of sight from individual effort to organisational strategy.
The company subsequently evolved toward its iCount platform (introduced circa 2016), incorporating continuous feedback, real-time goal adjustments, and development-focused conversations. According to published accounts and industry analyses, the result was a PM system that not only evaluated past performance but actively directed employee behaviour toward strategic priorities while remaining adaptive to changing business conditions (T. V. Rao, 2008; A. Sharma et al., 2016).
Discussion Questions:
- Understand/Apply: How does the Balanced Scorecard approach ensure that individual performance contributes to organisational strategy at Infosys?
- Analyse: What challenges might arise when cascading strategic themes across a large, geographically distributed technology company?
- Evaluate: Why might Infosys have moved from annual reviews to the iCount continuous feedback platform, and what motivational theories support this shift?
Adobe’s abandonment of its annual review system in favour of ongoing “Check-In” conversations is one of the most widely cited PM transformations of the past decade. Frustrated by administrative burden and employee dissatisfaction, Adobe replaced its rating system in 2012 with regular, informal manager-employee conversations focused on three elements: expectations, feedback, and growth and development.
The results were striking: voluntary turnover declined by 30 per cent within the first year, employee engagement improved, and the system freed approximately 80,000 hours of manager time previously consumed by annual reviews (P. Cappelli & A. Tavis, 2016; D. Morris, 2016).
Adobe’s experience demonstrates that the purposes of PM, covering alignment, improvement, development, and engagement, can be achieved more effectively through continuous dialogue than through periodic formal evaluation.
Discussion Questions:
- Understand/Apply: What structural weaknesses in annual appraisal systems motivated Adobe’s transition to continuous check-ins?
- Analyse: How does the Check-In model address the tension between administrative and developmental purposes identified by H. H. Meyer et al. (1965)?
- Evaluate/Create: What capabilities must managers develop to succeed in a continuous feedback model, and how does this relate to A. N. Kluger & A. DeNisi (1996)’s findings on feedback effectiveness?
1.10 Common Misconceptions about Performance Management
The most pervasive misconception conflates performance management with performance appraisal. Appraisal is a component, specifically one evaluative event within a much larger system. Performance management encompasses the full cycle of planning, monitoring, developing, evaluating, and rewarding (M. Armstrong, 2009; T. V. Rao, 2008). This distinction is so consequential that it is the subject of the next chapter.
While HR designs and supports PM systems, the day-to-day practice resides with line managers and their teams. HR provides the architecture; managers provide the execution. When PM is perceived as an HR function alone, it loses operational relevance and becomes a compliance exercise (R. Bacal, 1999; P. Chadha, 2003).
Identifying and addressing underperformance is one function, but far from the primary purpose. PM serves strategic, developmental, communicative, and motivational purposes that extend well beyond substandard performance. Organisations that use it primarily as a discipline tool create a culture of fear that undermines the improvement it seeks to produce (W. E. Deming, 1986; E. D. Pulakos, 2009).
Technology facilitates PM through real-time feedback and analytics. But effectiveness ultimately depends on the quality of human interaction between managers and employees. The most sophisticated platform cannot compensate for managers who lack the skill or willingness to have honest, constructive conversations. Technology is an enabler, not a substitute (H. Aguinis, 2013).
1.11 Summary
- Definition: A continuous, systematic process of aligning individual and team performance with organisational strategy through goal-setting, feedback, development, evaluation, and recognition.
- Historical evolution: From merit rating through behavioural methods and systems thinking, to today’s continuous feedback and OKR-driven models.
- Five purposes: Strategic (alignment), administrative (HR decisions), developmental (capability building), communicative (expectations and dialogue), motivational (engagement and commitment).
- Eight operational uses: Workforce planning, compensation, promotion, training needs, succession, legal documentation, selection validation, and organisational development.
- Six theories: Goal-setting (E. A. Locke & G. P. Latham, 1990), expectancy (V. H. Vroom, 1964), reinforcement (B. F. Skinner, 1953), systems theory (W. E. Deming, 1986), Balanced Scorecard (R. S. Kaplan & D. P. Norton, 1996), social exchange (P. M. Blau, 1964; D. M. Rousseau, 1995).
- Critical nuance: Feedback is not universally beneficial; task-focused, forward-looking delivery is essential (A. N. Kluger & A. DeNisi, 1996).
- Case lessons: Infosys demonstrates strategic alignment through cascaded scorecards; Adobe demonstrates that continuous dialogue delivers PM’s purposes more effectively than annual appraisal.
Performance management, properly understood and skilfully practised, is far more than a bureaucratic necessity. It is a strategic capability that shapes organisational effectiveness and the quality of working life.