4  Agile HR versus Traditional HR

ImportantLearning Objectives

You will be able to:

  1. Describe the assumptions underlying the traditional HR operating model and explain why they made sense in the environment that produced them.
  2. Compare agile and traditional HR across planning, structure, performance management, communication, and decision-making.
  3. Evaluate which HR activities genuinely benefit from agile ways of working and which remain better served by standardized, compliance-driven processes.
  4. Outline a realistic transition path from a traditional to an agile HR operating model.

4.1 Introduction

The previous three chapters established what Agile HR is, why organizations are adopting it, and the four principles that animate it. This chapter sets the two operating models side by side. The comparison matters because the traditional model is not a caricature to be dismissed; it is a coherent system that solved real problems for most of a century. Personnel management and its successor, strategic human resource management, were built for organizations that competed on scale, stability, and predictability (David Ulrich, 1997). Annual planning cycles, standardized policies, and functional specialization were rational responses to that environment, not failures of imagination.

The case for agile rests on the claim that the environment has changed faster than the model. When products ship weekly, strategies pivot quarterly, and employees compare their workplace tools to consumer software, an HR function that plans annually and delivers through multi-year programmes finds itself permanently out of phase with the organization it serves (Natal Dank & Riina Hellström, 2020). Lucy Adams (2021) puts the point sharply: HR’s problem is not effort or intent but an operating model designed for a world that no longer exists. This chapter examines that claim dimension by dimension, and then, just as importantly, identifies where it does not hold.

flowchart LR
    subgraph TRAD ["Traditional HR Logic"]
        T1["Annual planning"] --> T2["Standardized programmes"] --> T3["Cascade and control"]
    end
    subgraph AG ["Agile HR Logic"]
        A1["Continuous sensing"] --> A2["Iterative delivery"] --> A3["Feedback and adaptation"]
    end
    style T1 fill:#ffebee,stroke:#C62828
    style T2 fill:#ffebee,stroke:#C62828
    style T3 fill:#ffebee,stroke:#C62828
    style A1 fill:#e8f5e9,stroke:#388E3C
    style A2 fill:#e8f5e9,stroke:#388E3C
    style A3 fill:#e8f5e9,stroke:#388E3C

4.2 The Traditional HR Operating Model

4.2.1 Origins and Assumptions

Traditional HR descends from the personnel departments of industrial-era firms, whose mandate was administrative accuracy: payroll, contracts, discipline, and welfare. The strategic HRM movement of the 1990s raised the function’s ambition, arguing that HR should be a business partner shaping strategy rather than a back office executing it (David Ulrich, 1997). Yet even in its strategic form, the model retained three deep assumptions inherited from its industrial origins.

First, predictability: the coming year can be forecast well enough that an annual workforce plan, budget, and appraisal cycle will still make sense in month eleven. Second, standardization: fairness and efficiency are best achieved by applying identical processes to everyone, administered by specialists in functional silos such as recruitment, learning, and reward. Third, control: quality comes from designing the process centrally and monitoring compliance with it, with information flowing up the hierarchy and decisions flowing down.

NoteThe Waterfall Inheritance

Traditional HR programme delivery mirrors what software engineers call waterfall development: requirements are gathered, a complete solution is designed, sign-off is secured, and the finished programme is rolled out organization-wide in a single release. As Chapter 1 showed, agile emerged in software precisely because this sequence fails when requirements change faster than the delivery cycle (Kent Beck et al., 2001). The same failure mode appears when a two-year HR transformation launches into an organization that has reorganized twice since the requirements were gathered.

4.2.2 Strengths of the Traditional Model

An honest comparison must begin by acknowledging what the traditional model does well. Standardized processes deliver consistency and auditability, which is exactly what legal compliance, payroll accuracy, and equal-treatment obligations require. Functional specialization builds deep expertise in domains such as employment law and compensation design that generalist squads struggle to replicate. Annual cycles align HR with financial planning and governance rhythms that boards and regulators still expect. Any transition to agile that discards these strengths wholesale creates new problems as fast as it solves old ones (Darrell K. Rigby et al., 2020).

4.3 Comparing the Two Models

4.3.1 Planning and Delivery

The sharpest contrast lies in how work is planned and delivered. Traditional HR plans annually and delivers in large batches: the yearly engagement survey, the annual appraisal, the organization-wide competency framework launched as a finished product. Agile HR plans continuously and delivers in small increments: a pulse check every fortnight, feedback conversations every sprint, a pilot onboarding journey tested with one business unit before scaling (Natal Dank & Riina Hellström, 2020). Chapter 3 explained the economics of this difference: small batches make revision cheap, so plans can follow evidence rather than defend it.

4.3.2 Structure and Decision-Making

Traditional HR organizes by function, with each silo owning its process end to end and coordination happening through escalation. Agile HR organizes around outcomes, assembling cross-functional teams that draw on multiple specialisms and hold delegated decision rights, in the manner of the squads discussed in Chapter 3. Stephen Denning (2018) documents how organizations such as ING restructured entire functions on this logic, dissolving departmental boundaries in favour of mission-oriented teams. Decision-making shifts correspondingly: from decisions made centrally and cascaded downward, to decisions made closest to the information, within guardrails set centrally.

4.3.3 Performance and Feedback

Nowhere is the divergence more visible than performance management. The traditional apparatus, annual objectives, mid-year review, year-end rating, forced distribution, assumes that a year is a meaningful performance period and that a single rating can summarize it. Peter Cappelli & Anna Tavis (2016) chart how firms including Deloitte, GE, and Adobe dismantled this apparatus in favour of frequent, forward-looking conversations, precisely because annual feedback arrived too late to change anything it described. The agile alternative treats feedback as a flow rather than an event, a theme Chapter 9 develops in full.

4.3.4 Mindset

Beneath the visible practices sits the difference in mindset introduced in Chapter 2. The traditional model implicitly treats capability as fixed: assess people accurately, sort them into the right boxes, and manage the boxes. The agile model treats capability as developable, echoing the growth mindset described by Carol S. Dweck (2006): assess to develop, not merely to sort. Neither mindset is automatic; each is reinforced daily by the processes the organization runs.

NoteAgile HR and Traditional HR Compared
Dimension Traditional HR Agile HR
Planning horizon Annual cycle, fixed plan Continuous, short cycles, plans revised on evidence
Delivery style Large batch, organization-wide rollout Small batch, pilot and iterate
Structure Functional silos with specialist owners Cross-functional teams organized around outcomes
Decision rights Centralized, cascaded downward Delegated to teams within guardrails
Performance management Annual appraisal and rating Continuous feedback and coaching conversations (Peter Cappelli & Anna Tavis, 2016)
Information flow Filtered upward through hierarchy Transparent by default, visible backlogs
Employee’s role Recipient of programmes Customer and co-creator of HR products
Measure of success Process compliance, on-time delivery Outcomes for employees and the business (Natal Dank & Riina Hellström, 2020)
WarningCommon Misconception: Agile HR Means Abandoning Structure

The comparison table invites a false reading in which traditional means disciplined and agile means loose. The opposite is closer to the truth. Agile HR replaces one form of discipline, compliance with a fixed plan, with another that is arguably more demanding: visible work, short feedback deadlines, and explicit evidence tests for every initiative. Darrell K. Rigby et al. (2020) stress that agile done right is highly structured; what changes is what the structure is designed to produce, learning rather than predictability.

4.4 Beyond the Binary: A Contingency View

4.4.1 Not Everything Should Be Agile

Treating agile versus traditional as a total choice is the most common strategic error in HR transformations. Darrell K. Rigby et al. (2020) argue that the well-run agile enterprise is deliberately dual: innovation-facing work runs in agile teams, while operations that depend on reliability and compliance continue to run as disciplined standard processes. Payroll is the canonical HR example. Nobody wants an iterative, experimental payroll; employees want it identical and correct every month. The same holds for statutory compliance, grievance procedures bound by natural-justice requirements, and much of employment-contract administration.

The practical question is therefore not “should HR be agile?” but “which HR work benefits from agility?” Work that is exploratory, employee-facing, and subject to changing requirements, designing an onboarding journey, building a new performance approach, improving candidate experience, gains from iteration. Work that is repetitive, rule-bound, and correctness-critical gains from standardization and, increasingly, from automation (Stefan Strohmeier, 2020).

TipPractitioner Insight: Sort the Portfolio Before You Transform

Before restructuring anything, map the HR portfolio into two columns: work where the requirement is stable and the cost of error is high, and work where the requirement is uncertain and the cost of a wrong guess compounds over time. Apply agile methods to the second column first. A function that pilots agile on exploratory work builds credibility; one that destabilizes payroll in the name of agility loses the licence to continue.

4.4.2 The Transition Path

Organizations rarely leap from one model to the other. Natal Dank & Riina Hellström (2020) describe a typical progression: first, agile methods appear inside individual HR projects, a Kanban board here, a sprint there; next, HR teams reorganize around products and outcomes with visible backlogs; finally, the operating model itself changes, with funding, governance, and roles redesigned around iterative delivery. Each stage builds the skills and the trust required for the next. Chapters 5 and 6 equip you for the first stage by treating the two most widely used frameworks, Scrum and Kanban, in practical detail.

flowchart TD
    S1["Stage 1:<br>Agile practices in projects"] --> S2["Stage 2:<br>Teams organized around<br>HR products and backlogs"] --> S3["Stage 3:<br>Operating model redesigned:<br>funding, governance, roles"]
    style S1 fill:#e3f2fd,stroke:#1976D2
    style S2 fill:#fff8e1,stroke:#F9A825
    style S3 fill:#e8f5e9,stroke:#388E3C

4.5 Case Studies

4.5.1 Case Study 1: GE, Dismantling the Annual Appraisal

General Electric spent decades as the emblem of traditional performance management, famous for annual ratings and the forced-ranking “vitality curve” that cut the bottom ten percent of performers each year. From 2015 the company retired this apparatus for most of its workforce, replacing annual reviews with frequent “touchpoint” conversations supported by a mobile app called PD@GE, through which employees exchange ongoing priorities and feedback (Peter Cappelli & Anna Tavis, 2016). The firm that had defined the traditional model concluded that yearly feedback could not steer work organized around fast-moving projects.

Discussion Questions:

  1. Why did the annual ranking system that served GE in the 1980s become a liability in the 2010s? Which environmental drivers from Chapter 2 apply?
  2. What risks did GE take on by removing ratings, and how might an organization mitigate them?
  3. Does replacing an annual process with an app guarantee a change in feedback behaviour? What else must change?

4.5.2 Case Study 2: ING, Restructuring Rather Than Retrofitting

Rather than layering agile practices onto its existing structure, the Dutch bank ING dissolved the structure itself. In 2015 its Netherlands headquarters reorganized some 3,500 employees into small multidisciplinary squads grouped into tribes, required existing employees to reapply for positions in the new model, and redesigned HR processes, from workforce planning to performance management, to serve the new structure (Stephen Denning, 2018). The HR function faced both challenges at once: transforming its own way of working while supporting the most disruptive reorganization in the bank’s history.

Discussion Questions:

  1. ING chose revolutionary restructuring where GE chose targeted process replacement. What conditions favour each transition path?
  2. What obligations does an agile transformation of this scale place on HR that a traditional reorganization does not?
  3. Requiring employees to reapply for their own jobs is contentious. Defend and critique the practice from an employee-experience perspective.

4.6 Summary

NoteChapter Summary

Traditional HR is a coherent model built on predictability, standardization, and control, assumptions inherited from an industrial environment and formalized in the strategic HRM era (David Ulrich, 1997). Agile HR replaces annual, large-batch, cascade-driven delivery with continuous, small-batch, feedback-driven delivery (Natal Dank & Riina Hellström, 2020). The models differ across planning, structure, decision rights, performance management, and mindset, but the comparison is not a verdict: compliance-critical and correctness-critical work still benefits from standardization, and the well-designed HR function deliberately runs both modes side by side (Darrell K. Rigby et al., 2020). GE and ING illustrate two transition paths, targeted process replacement and wholesale structural redesign (Peter Cappelli & Anna Tavis, 2016; Stephen Denning, 2018). The next two chapters turn to the frameworks, Scrum and Kanban, through which agile working is put into daily practice.

TipKey Terms

Traditional HR operating model · Waterfall delivery · Annual cycle · Functional silo · Standardization · Forced ranking · Continuous feedback · Contingency view · Dual operating model · Transition path

Summary

Concept Description
The Traditional Model
Traditional HR operating model An HR system built on annual cycles, standardized processes, and centralized control
Predictability assumption The belief that the coming year can be forecast well enough for a fixed annual plan to hold
Standardization assumption The belief that fairness and efficiency come from identical processes applied to everyone
Control assumption The belief that quality comes from central design and monitored compliance
Waterfall delivery Gathering all requirements, designing a complete solution, and rolling it out in one release
Strategic HRM era The 1990s movement repositioning HR as a strategic business partner rather than a back office
Annual planning cycle The yearly rhythm of workforce plans, budgets, and appraisals aligned to financial reporting
Functional silo A specialist HR department owning one process end to end and coordinating by escalation
Forced ranking Rating systems that distribute employees along a curve and act on the bottom segment
The Agile Alternative
Small-batch delivery Delivering HR change in cheap-to-revise increments piloted before scaling
Delegated decision rights Authority moved to the team closest to the information, bounded by central guardrails
Continuous feedback Treating feedback as an ongoing flow of conversations rather than an annual event
Growth mindset in systems Designing HR processes that assess people in order to develop rather than merely sort them
Beyond the Binary
Contingency view Matching the operating model to the work: agile for exploration, standard process for compliance
Dual operating model Running agile teams and disciplined standard operations deliberately side by side
Transition path The staged progression from agile projects to agile teams to a redesigned operating model
Case Evidence
GE touchpoints GE's replacement of annual ratings with frequent app-supported feedback conversations
ING restructuring ING's reorganization of 3,500 employees into squads and tribes with HR redesigned to match