Performance Management

Performance management is the part of human resources concerned with defining what good work looks like, measuring it, and using that measurement to improve it.

10 frameworks, from 1910 to today · Human Resources · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Performance management is the part of human resources concerned with defining what good work looks like, measuring it, and using that measurement to improve it. It covers the goals set for individuals and teams, the appraisal that judges how far they were met, the feedback that follows, and the decisions about pay, promotion, and dismissal that hang on the result. What is at stake is double-edged. For the organization, appraisal is how strategy reaches the individual desk and how merit is supposed to be rewarded; for the worker, it is the formal record of whether their effort is seen as valuable1. The history of the field is largely a history of trying to make that judgment both fair and useful—and of recurring doubts about whether a single annual rating can do either job.

Merit rating and the efficiency tradition

Formal appraisal grew out of the early twentieth-century efficiency movement. Scientific management, associated with Frederick Winslow Taylor and his Principles of Scientific Management (1911), broke work into tasks and set standards for each; once a standard existed, someone had to judge whether a worker met it. Early schemes were called merit rating: a supervisor scored subordinates on traits and habits—reliability, initiative, cooperation—usually on simple scales, and the score fed pay and promotion decisions. The U.S. military's rating of officers during the First World War gave the practice a visible model, and large firms adopted it through the 1920s and 1930s.

Merit rating's weakness was that it measured the person's character as the supervisor perceived it, not the work. Traits were vague, scales were undefined, and ratings said as much about the rater as the rated. The psychologist Walter Dill Scott, who had worked on selecting and rating military personnel, helped carry the method into industry, but the core problem—what exactly a "4" on cooperation meant—remained.

The appraisal interview and the rise of feedback

After the Second World War, appraisal shifted from a scorecard to a conversation. The management writer Peter Drucker, in The Practice of Management (1954), argued that managers should set clear objectives with each subordinate and appraise against them rather than against personality. Around the same period, the idea of the appraisal interview—a structured discussion in which supervisor and employee review results and plan improvement—became standard in large American corporations. Douglas McGregor, whose The Human Side of Enterprise (1960) set out Theory X and Theory Y, wrote influentially against using appraisal purely as judgment: if the interview is a courtroom, the employee defends rather than learns. The tension he named—appraisal as evaluation versus appraisal as development—has never been resolved and recurs in every later reform.

Management by Objectives

The decisive mid-century turn was Management by Objectives (MBO), which Drucker introduced in The Practice of Management and which the consultant George Odiorne popularized in the 1960s. MBO's claim was that appraisal should be built from the top down: organizational goals cascade into unit goals, unit goals into individual objectives, and each person is judged on whether the objectives were achieved. The method made performance concrete and tied it to strategy, and it spread widely through the 1960s and 1970s, especially in the United States.

MBO's practical failure was its rigidity. Objectives were often set annually, written down, and then ignored until review; they could be gamed or rendered obsolete by changed circumstances; and the cascade assumed a stable hierarchy. Its legacy, though, is large: the idea that performance should be judged against agreed goals rather than personality traits is now basic to the field.

Behaviorally anchored rating scales

In the 1960s, industrial psychologists tried to fix the vagueness of trait scales with Behaviorally Anchored Rating Scales (BARS). Developed by Patricia Cain Smith and Lorne Kendall at Bowling Green State University and published in 1963, BARS built each rating scale from concrete examples of behavior—critical incidents collected from the people who did the job—anchored at points along the scale. A rating of "high" on handling customer complaints meant a specific described behavior, not an adjective. The method improved reliability and gave feedback something specific to point to, but it was expensive to build and maintain, and it did not solve the problem of rater bias.

The critique from quality management

The sharpest attack on individual appraisal came from W. Edwards Deming, the statistician and quality-management authority whose ideas reshaped Japanese manufacturing after the war and reached American managers through the 1980s. Deming argued that most variation in performance comes from the system—processes, tools, training, management—not from individual effort, and that rating individuals therefore mostly measures noise. In his "14 Points" for management, he called for the abolition of annual merit ratings and management by objectives, holding that they destroy teamwork, encourage short-term gaming, and blame workers for problems management created. Deming's critique was influential in quality-focused organizations and remains the standard argument against forced ranking and individual pay-for-rating.

Forced ranking and its retreat

The 1980s and 1990s saw the spread of forced ranking (also called stack ranking), in which managers must distribute ratings along a fixed curve—typically a set share of top, middle, and bottom performers, with the bottom group managed out. General Electric under Jack Welch became its best-known exemplar, and the practice spread through large American firms. Its advocates claimed it countered lenient ratings and kept a performance culture sharp. Its critics pointed to the evidence that it damaged collaboration, encouraged gaming, and often punished people for system-level problems—Deming's argument in practical form. By the 2010s many prominent firms, including GE itself, abandoned the practice, and the retreat became a symbol of the wider dissatisfaction with annual ratings.

360-degree feedback

A parallel reform attacked the single-supervisor judgment. 360-degree feedback, developed from the 1950s onward in assessment and organizational-development work and widespread by the 1990s, collects ratings from supervisors, peers, subordinates, and sometimes customers and the employee themselves. The claim was that multiple perspectives give a fuller and fairer picture, especially for managers whose work is largely relational. In practice, 360 feedback proved more useful for development than for pay and promotion decisions: ratings from different groups often disagree, and when tied to rewards the feedback becomes political. Many organizations now use it for development only.

Objectives and Key Results

The goal-setting tradition was revived in Silicon Valley. Objectives and Key Results (OKRs), developed at Intel under Andy Grove in the 1970s and brought to Google by John Doerr in the late 1990s, pairs a qualitative objective with a small set of measurable key results, set quarterly and made public within the organization. OKRs deliberately separate goal-setting from compensation, aiming at focus and transparency rather than rating. Their spread through technology firms in the 2010s made them the most visible descendant of MBO, and the most visible attempt to keep goals ambitious by not tying them directly to pay.

Continuous performance management and people analytics

Since the 2010s, two developments have reshaped practice. The first is continuous performance management: replacing the annual review with frequent check-ins, real-time feedback, and regularly updated goals, often supported by software. The drivers were generational expectations, the pace of change in goals, and the accumulated dissatisfaction with annual ratings documented in surveys and by consultancies. The second is people analytics: the application of data science to HR questions, including performance2. Its roots lie in earlier psychometric work on rating reliability and validity, but the modern form uses large datasets and statistical modeling to test whether appraisal scores predict outcomes, whether feedback improves performance, and where bias enters ratings. The evidence has been sobering—research on feedback has found that it can improve performance in some settings and harm it in others—and it has pushed the field toward treating performance management as an empirical question rather than a settled procedure.

Where the field stands

Today the main approaches coexist rather than replace one another. Goal-based systems descended from MBO and OKRs remain the backbone of most formal schemes; 360 feedback survives mainly as a development tool; continuous check-ins have displaced the annual review in many large firms; and people analytics supplies the evidence used to argue about all of them. The unresolved questions are old ones in new dress: whether appraisal should judge or develop, whether individual ratings can be fair when performance is largely systemic (Deming's point), and whether frequent measurement improves work or merely documents it. The field's history is a long record of reforms that solved the previous method's problem and created the next one.

References

  1. Business performance management (Application), Wikipedia
  2. Analytics (People analytics), Wikipedia

The frameworks of Performance Management

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1910-1950

    Merit Rating

    How should a supervisor score a worker's traits?

    Fly to its tower in Nousfarer

  2. 1950-1980

    Appraisal Interview and Developmental Appraisal

    How should supervisor and employee discuss performance?

    Fly to its tower in Nousfarer

  3. 1954-1990

    Management by Objectives

    How should goals cascade into individual objectives?

    About Management by Objectives
    Management by Objectives (MBO) is the framework that first made performance management a deliberate, results-oriented process rather than a subjective review of personal traits. Developed in the 1950s, MBO answered a practical question: how can organizations ensure that every employee's daily work contributes directly to the organization's larger aims? Its core insight was to replace vague, personality-based evaluations with jointly set, measurable objectives that create a clear line of sight from individual effort to organizational success.
    In a first course on MBO within performance management, the curriculum follows a logical progression through ten key concepts. The sequence begins with Goal Setting, the foundational practice of defining what an employee will achieve. This leads directly to SMART Objectives—the canonical checklist ensuring goals are Specific, Measurable, Achievable, Relevant, and Time-bound. The next concept is Joint Goal Setting, where managers and subordinates collaborate to agree on objectives, a process that distinguishes MBO from purely top-down directive approaches. From this collaboration emerge Performance Standards, the clear criteria against which work will be judged. These standards are then documented during Objective Setting, a formal step that creates a written record of commitments. The entire cycle is structured as an Annual Performance Cycle, beginning with objective setting and ending with a Performance Review. During the year, the Manager-Subordinate Dialogue provides ongoing discussion about progress, not just a single end-of-year conversation. The actual evaluation uses Results-Oriented Evaluation, which measures outcomes against the agreed objectives rather than personal traits or behaviors. This evaluation happens at the Performance Appraisal meeting, where the employee's achievements are formally compared to the set goals. The final curriculum concept is the Management by Objectives Process itself, which ties all these elements together: managers cascade high-level organizational goals downward through successive levels (a process known as Top-Down Cascading), ensuring that every individual objective supports the next level up. For instance, a regional sales manager might set a goal to increase market share by 5%, which then informs each sales representative's individual target for new accounts.
    The intellectual history of MBO is rooted in its time, roughly 1954 to 1980, a period when performance management shifted from informal, trait-based appraisals to systematic, goal-driven systems. Key precursors include the Scientific Management movement, which emphasized efficiency and measurable output, and the Human Relations Movement, which highlighted the importance of worker motivation and participation. Management consultant and author Peter Drucker (1909–2005) is the canonical originator of MBO, introducing the term and concept in his 1954 book The Practice of Management. Drucker drew on earlier management thought but gave it a distinctive new focus: the integration of individual and organizational goals through a collaborative process. His formulation was further developed by George Odiorne (1920–1992), particularly in his 1965 book Management by Objectives: A System of Managerial Leadership, which provided a more detailed operational model. The behavioral theorist Douglas McGregor (1906–1964) also reinforced MBO's participatory aspect through his Theory X and Theory Y distinction, arguing that MBO aligned with Theory Y's assumption that workers are capable of self-direction and self-control when given clear objectives. During its peak, MBO became standard practice in many large corporations and government agencies, including the U.S. Department of Defense under Robert McNamara in the 1960s.
    MBO's relationship to later frameworks is one of supplementation, not simple replacement. The dominant successor was 360-Degree Feedback (emerging around 1980), which added multi-source behavioral input to complement MBO's results-only focus. Later frameworks like the Balanced Scorecard (1992) and Performance Prism (2000) expanded performance management to include multiple stakeholder perspectives, while Agile Performance Management (2010) replaced the annual cycle with continuous, iterative conversations. MBO's core logic—goal setting, alignment, and periodic review—remains an active legacy, especially in organizations that run annual objective-setting systems such as OKRs (Objectives and Key Results).
    The 12 concepts its tower teaches
    • Annual Performance Cycle
    • Goal Setting
    • Joint Goal Setting
    • Management by Objectives Process
    • Manager-Subordinate Dialogue
    • Objective Setting
    • Performance Appraisal
    • Performance Review
    • Performance Standards
    • Results-Oriented Evaluation
    • SMART Objectives
    • Top-Down Cascading

    Fly to its tower in Nousfarer

  4. 1963-1990

    Behaviorally Anchored Rating Scales

    How can rating scales be tied to observed behavior?

    Fly to its tower in Nousfarer

  5. 1980-Present
  6. 1980-2015

    Vitality curve

    Should ratings be forced into a fixed curve?

    Fly to its tower in Nousfarer

  7. 1990-Present

    360-Degree Feedback

    Whose perspectives should judge a person's performance?

    Fly to its tower in Nousfarer

  8. 1999-Present

    Objectives and Key Results

    How should ambitious goals be set and tracked?

    Fly to its tower in Nousfarer

  9. 2010-Present

    People Analytics

    What does data show about ratings and feedback?

    Fly to its tower in Nousfarer

  10. 2012-Present

    Continuous Performance Management

    How can feedback and goals be kept continuous?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Merit RatingAppraisal Interview and Developmental…Management by ObjectivesBehaviorally Anchored Rating ScalesQuality Management Critique of Indivi…Vitality curve360-Degree FeedbackObjectives and Key ResultsPeople AnalyticsContinuous Performance Management

Beyond the field

Where Performance Management's ideas came from in other fields, and what they led to there: the strongest 12 of 29 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Performance Management is a planet in Nousfarer

Its city has a tower for each of these 10 frameworks. Land, walk in, and climb one concept at a time.

Land on Performance Management

Related fields

Fields its ideas are linked to

More in Human Resources

See where Performance Management sits on the Map of Human Knowledge