2 Drivers of Agile Transformation and the Agile Mindset

Learning Objectives

You will be able to:

Distinguish the external and internal drivers that push organizations toward agile transformation.
Explain why an agile mindset must accompany agile structures and processes for a transformation to hold.
Contrast the fixed and growth mindsets and describe how each shows up in organizational behaviour.
Identify common sources of resistance to agile transformation and the HR responses that address them.

2.1 Introduction

Organizations rarely adopt agile ways of working because the vocabulary of sprints and backlogs is appealing. They adopt it because something has stopped working: a competitor moves faster, a technology shift makes existing capabilities obsolete, or a workforce raised on instant feedback rejects an annual review cycle. Understanding these pressures, external and internal, explains why transformation begins.

A second, less visible condition explains why transformation succeeds or stalls. Stephen Denning (2018) argues throughout The Age of Agile that organizations which install agile ceremonies without adopting the underlying mindset get the appearance of agility with none of its benefit: stand-up meetings that report status rather than surface problems, retrospectives that generate no change, roadmaps still defended as fixed commitments. Structure can be redesigned in a quarter. A mindset, the deeper set of beliefs about ability, failure, and control that shapes how people actually behave under pressure, changes far more slowly, and it is this gap that determines whether a transformation sticks.

flowchart TD
    A["External pressure:<br>markets, technology,<br>workforce expectations"] --> C["Case for agile<br>transformation"]
    B["Internal pressure:<br>leadership, talent gaps,<br>legacy structures"] --> C
    C --> D["Structures and<br>processes change"]
    C --> E["Mindsets shift"]
    D --> F["Transformation<br>that sticks"]
    E --> F
    style A fill:#ffebee,stroke:#C62828
    style B fill:#fff8e1,stroke:#F9A825
    style C fill:#e8eaf6,stroke:#5C6BC0
    style D fill:#e3f2fd,stroke:#1976D2
    style E fill:#ede7f6,stroke:#7E57C2
    style F fill:#e8f5e9,stroke:#388E3C

2.2 External Drivers of Agile Transformation

2.2.1 Market Volatility and Competitive Pressure

Product cycles that once ran for years now run for months. Competitors, including digital-native entrants with no legacy infrastructure to protect, can launch and iterate faster than an incumbent’s planning calendar allows. Darrell K. Rigby et al. (2020) describe this as the defining condition of the modern “agile enterprise”: the parts of an organization exposed to volatility must sense and respond in weeks, not years, while other functions retain the stability that steady operations require.

HR sits directly in the path of this pressure. Every reorganization, every new capability the business needs, and every skill that becomes obsolete first shows up as a people problem before it shows up anywhere else. A workforce plan built on a three-year horizon cannot answer a capability gap that opens in a single quarter.

2.2.2 Technological and Digital Disruption

Cloud computing, automation, and artificial intelligence have compressed the shelf life of technical skill. Stefan Strohmeier (2020) distinguishes the operational use of digital HR platforms, largely automating existing transactions, from their transformational use, which changes what HR is able to sense and respond to in real time. Organizations that only automate old processes gain efficiency; those that use the same technology to shorten feedback loops gain agility.

Digital disruption also changes what “the business” expects from HR. A product team shipping weekly cannot wait a month for a requisition to clear, or a year for a competency framework to catch up with a role that no longer exists in its original form.

2.2.3 Rising Workforce Expectations

A third external pressure comes from the workforce itself. Jacob Morgan (2017) documents employees evaluating organizations the way consumers evaluate services, weighing the whole experience of work rather than compensation alone. Ben Whitter (2019) frames the practical implication directly: design work around the human being, not the process. Employers slow to respond lose talent to ones that are not, and that loss is now visible in public employer reviews, not just exit interviews.

These three external pressures rarely arrive one at a time. A market shock exposes a skills gap, the gap forces a technology investment, and the technology investment raises workforce expectations further; each driver amplifies the others.

Drivers of Agile Transformation at a Glance

Driver	Typical Trigger	What It Demands of HR
Market volatility	A competitor or shock shortens the planning horizon	Faster workforce and capability planning
Technological disruption	New tools change what work looks like	Continuous reskilling, not periodic training
Workforce expectations	Talent compares employers like consumers compare services	Experience-led, responsive people practices
Leadership commitment	A sponsor stakes personal credibility on the change	Visible role-modelling, not delegation to HR alone
Talent and skills scarcity	Critical capabilities cannot be hired fast enough	Build capability internally through agile learning
Structural rigidity	Layered hierarchy slows decisions to a crawl	Flatter, cross-functional operating models

2.3 Internal Drivers of Agile Transformation

2.3.1 Leadership Commitment and Sponsorship

External pressure explains why transformation becomes necessary; it rarely explains why it begins on a particular date, in a particular organization. That usually traces to a leader who commits publicly and stays committed once the disruption of change becomes visible. Natal Dank & Riina Hellström (2020) note that agile HR initiatives launched without senior sponsorship tend to survive as isolated pilots, admired in a single department and never scaled, because scaling requires trade-offs, budget, and political cover that only leadership can provide.

Practitioner Insight: Sponsorship Is a Behaviour, Not a Signature

A leader’s endorsement in a town hall is not sponsorship. Sponsorship is visible in smaller, repeated choices: attending the retrospective instead of sending a deputy, letting a pilot team miss a deadline without punishment because it produced a valuable lesson, and changing a decision publicly when evidence from an experiment contradicts the original plan.

2.3.2 Talent and Skills Scarcity

Many organizations cannot hire their way out of a capability gap; the specific combination of skills a transformation requires is often scarce in the external labour market at any price. This scarcity is itself a driver of agile transformation, because it forces the organization toward continuous internal capability building rather than periodic, large-batch training. Katharina Harsch & Marion Festing (2020), in a qualitative study of talent management functions undergoing agile change, find that the organizations best able to respond to volatility are not those with the deepest talent pipelines but those with the most dynamic talent management capabilities: the routines that let a function sense a capability gap and redeploy or reskill people quickly, rather than waiting for the next annual planning cycle.

2.3.3 Organizational Structure and Legacy Process Rigidity

Deep hierarchies, narrow job descriptions, and approval chains built for a stable era slow decisions in a volatile one. Frederic Laloux (2022) documents organizations that abandoned multi-layer command structures for self-managing teams precisely because each additional approval layer added delay without adding judgement. Legacy HR artefacts, rigid grading structures, annual headcount plans, and job descriptions written to be exhaustive rather than adaptable, tend to entrench this rigidity long after the business case for it has expired.

2.4 Barriers and Resistance to Agile Transformation

Understanding drivers explains why transformation starts. It does not guarantee it finishes. Several recurring sources of resistance appear across agile HR transformations regardless of industry.

Middle-management loss of control. Flatter structures and self-managing teams remove the coordination role many managers built their careers around; resistance here is rational, not merely emotional.
Incentives that still reward the old behaviour. A bonus structure tied to individual annual targets actively punishes the collaboration and iteration a transformation asks for.
Change fatigue. Employees who have lived through previous “transformations” that changed labels but not practice greet a new one with justified scepticism.
Risk-averse governance. Audit, compliance, and finance functions built to prevent errors can, without intending to, block the small, reversible experiments agile ways of working depend on.

Common Misconception: Restructuring Is the Transformation

Redrawing the organization chart into squads and tribes is often mistaken for the transformation itself. Lucy Adams (2021) argues the opposite: structure is the easy part precisely because it can be mandated from above, while the harder, slower work is unlearning management habits, letting go of control, tolerating visible failure, that no org chart can enforce. Organizations that stop at restructuring typically see the new boxes on the chart behave exactly like the old ones within a year.

flowchart LR
    subgraph FM ["Fixed Mindset"]
        F1["Abilities seen as fixed<br>Failure is avoided<br>The plan is defended"]
    end
    subgraph GM ["Growth Mindset"]
        G1["Abilities seen as developable<br>Failure is treated as data<br>The plan is adapted"]
    end
    FM -.->|"transformation that lasts<br>requires this shift"| GM
    style F1 fill:#ffebee,stroke:#C62828
    style G1 fill:#e8f5e9,stroke:#388E3C

2.5 The Agile Mindset

2.5.1 Defining the Agile Mindset

Natal Dank & Riina Hellström (2020) describe the agile mindset as a set of beliefs, transparency is safer than concealment, collaboration outperforms solo heroics, and adapting to new evidence is a strength rather than an admission of failure, that underpins every visible agile practice. Without it, a daily stand-up becomes a status report to a manager rather than a coordination tool between peers, and a retrospective becomes a ritual nobody expects to change anything.

2.5.2 Fixed versus Growth Mindset

The psychological foundation for this idea predates the agile movement. Carol S. Dweck (2006) distinguishes a fixed mindset, the belief that ability and intelligence are largely set, from a growth mindset, the belief that ability develops through effort, feedback, and deliberate practice. People holding a fixed mindset tend to avoid challenges that risk exposing a limitation and treat setbacks as verdicts on their competence. People holding a growth mindset tend to seek out challenge and treat setbacks as information about what to try next.

Organizations exhibit a parallel pattern at scale. A fixed-mindset organization defends its existing plan and treats a failed initiative as something to bury; a growth-mindset organization treats the same failed initiative as a data point and asks what it revealed. Stephen Denning (2018) makes essentially this argument about firms rather than individuals: an organization’s willingness to run small, visible experiments and change course on the evidence is what separates genuine agility from its imitation.

Fixed and Growth Mindsets, Individual and Organizational

Level	Fixed Mindset	Growth Mindset
Individual (Carol S. Dweck, 2006)	Avoids challenge; treats setbacks as a verdict on ability	Seeks challenge; treats setbacks as information
Team	Defends the sprint plan against new information	Revises the plan when a retrospective surfaces evidence
Organization (Stephen Denning, 2018)	Buries failed initiatives; protects the roadmap	Publicizes failed experiments; protects the learning

2.5.3 The Agile Mindset in HR Practice

For an HR function, the mindset shift shows up as a change in what “good” looks like. A fixed-mindset HR team measures itself by policy compliance and process completion; a growth-mindset HR team measures itself by whether its practices actually helped a team perform better, and revises the practice when the evidence says otherwise. Lucy Adams (2021) calls the required capability “unlearning”: HR professionals must let go of the comfort of comprehensive policy and tolerate the ambiguity of a practice that is still being tested.

Katharina Harsch & Marion Festing (2020) connect this directly to capability: functions with dynamic talent management routines, the ability to sense a gap and act on it quickly, are demonstrating the agile mindset in practice, not merely describing it in a values statement.

Practitioner Insight: Watch the Language, Not the Poster

An organization’s mindset shows up faster in its everyday language than in any values poster on the wall. Listen for whether a missed target is followed by “who is responsible for this” or “what did we learn from this.” The first sentence indicates a fixed mindset defending itself; the second indicates a growth mindset extracting value from the miss.

2.5.4 Building the Mindset: What HR Can Do

A mindset cannot be mandated by policy, but HR can design conditions that make a growth mindset more likely to take hold:

Run genuinely small, reversible experiments before scaling any new people practice, so failure carries low cost and clear learning value.
Redesign recognition so that surfacing a problem early is rewarded at least as visibly as hitting a target.
Train managers in questions that invite reflection, “what did this teach us,” rather than questions that assign blame.
Protect psychological safety explicitly: teams that fear visible failure will hide problems rather than surface them, no matter what the mindset training says.

Common Misconception: Mindset Training Is a One-Off Workshop

A single workshop on growth mindset changes vocabulary for a few weeks and behaviour for almost nobody. Carol S. Dweck (2006) is explicit that mindset is reinforced or eroded by the everyday feedback people receive, not by a slogan. If performance reviews, promotion criteria, and manager language continue to reward the appearance of infallibility, a workshop will not outcompete the incentives employees actually live under.

flowchart TD
    A["Frame a small,<br>safe-to-fail experiment"] --> B["Run it with<br>real employees"]
    B --> C["Reflect on what<br>the evidence shows"]
    C --> D["Adjust the<br>practice"]
    D --> A
    style A fill:#e3f2fd,stroke:#1976D2
    style B fill:#e8eaf6,stroke:#5C6BC0
    style C fill:#ede7f6,stroke:#7E57C2
    style D fill:#e8f5e9,stroke:#388E3C

2.6 Case Studies

2.6.1 Case Study 1: Microsoft, Resetting from a Fixed to a Growth Culture

When Satya Nadella became CEO of Microsoft in 2014, he identified the company’s dominant internal culture, competitive, siloed, and defensive of past success, as the primary obstacle to renewal, more than any product or technology gap. He named Dweck’s growth-mindset framework directly as the model for the culture he wanted, and used it to reframe internal language: from “know-it-all” to “learn-it-all.” Business school case studies of the transition, including one published by London Business School, document the shift from competing internal fiefdoms toward cross-team collaboration, and from punishing failed bets to treating them as sources of learning, as central to Microsoft’s subsequent turnaround in cloud and productivity businesses.

Discussion Questions:

Why might a leadership-level statement of “growth mindset” fail to change behaviour without matching changes to performance evaluation and promotion criteria?
What internal metrics could distinguish a genuine mindset shift from a rebranding of the same competitive culture?
How does Microsoft’s case illustrate the difference between an internal driver (leadership commitment) and a mindset (growth versus fixed) as discussed earlier in this chapter?

2.6.2 Case Study 2: ANZ Bank, Structural and Mindset Change Together

Australia and New Zealand Banking Group reorganized large parts of its technology and operations functions into agile “tribes” and squads, adopting practices, including daily stand-ups and sprint “ceremonies,” from the same Spotify-influenced model that shaped ING’s transformation. Public accounts of the change describe a deliberate emphasis on training people in the underlying agile mindset, not only the new organizational vocabulary, because leaders recognized that renaming departments “tribes” without changing how decisions were made would produce the appearance of agility rather than its substance.

Discussion Questions:

What risk does adopting agile vocabulary, tribes, squads, ceremonies, carry if the underlying decision rights do not actually change?
How might a large, regulated organization such as a bank need to adapt agile practices differently from a technology start-up?
What role should HR play in ensuring new structural labels are matched by genuine changes in behaviour?

2.6.3 Case Study 3: TCS, Reskilling at Scale in Response to Talent Scarcity

Tata Consultancy Services, one of India’s largest IT services employers, has run one of the sector’s most visible large-scale reskilling programmes, retraining substantial portions of its workforce in cloud, artificial intelligence, and other emerging digital capabilities rather than relying solely on external hiring for scarce skills. The scale of the effort, spanning hundreds of thousands of employees, illustrates the internal driver of talent and skills scarcity discussed earlier: when a capability cannot be bought fast enough in the external market, building it internally through continuous, iterative learning becomes a strategic necessity rather than a discretionary training budget line.

Discussion Questions:

Why might reskilling at very large scale require agile, iterative learning methods rather than a single standardized training rollout?
What does TCS’s approach suggest about the relationship between talent scarcity and the internal capability described by Katharina Harsch & Marion Festing (2020)?
What risks does an organization take if it relies on reskilling alone, without also adjusting recruitment and role design?

2.7 Summary

Chapter Summary

Agile transformation begins under pressure from external forces, market volatility, technological disruption, and rising workforce expectations, and internal ones, leadership commitment, talent and skills scarcity, and structural rigidity (Natal Dank & Riina Hellström, 2020; Katharina Harsch & Marion Festing, 2020; Darrell K. Rigby et al., 2020). These drivers explain why transformation starts; they do not guarantee it survives contact with resistance from middle managers, misaligned incentives, change fatigue, and risk-averse governance.

What separates transformations that last from those that regress to old behaviour is the mindset that accompanies the structural change. Drawing on Carol S. Dweck (2006)’s distinction between fixed and growth mindsets, Stephen Denning (2018) and Natal Dank & Riina Hellström (2020) argue that organizations able to treat failed experiments as evidence, rather than as verdicts to be hidden, are the ones that sustain agility once the initial reorganization is complete. Microsoft, ANZ Bank, and TCS each illustrate a different driver, leadership-led culture change, structural and mindset change together, and talent scarcity, but all three depend on the same underlying shift in how people relate to failure and evidence.

Key Terms

External driver · Internal driver · Market volatility · Digital disruption · Leadership sponsorship · Talent and skills scarcity · Structural rigidity · Change fatigue · Fixed mindset · Growth mindset · Agile mindset · Dynamic talent management capability · Safe-to-fail experiment · Psychological safety

Summary

Concept	Description
External and Internal Drivers
External driver	A pressure originating outside the organization that makes existing people practices unsustainable
Market volatility	Shortened business cycles that outpace long-horizon workforce planning
Technological disruption	New technology that compresses the shelf life of existing skills and process design
Workforce expectations	Employees evaluating employers the way consumers evaluate services
Internal driver	A pressure originating inside the organization that drives or blocks transformation
Leadership sponsorship	Visible, repeated leadership behaviour that gives a transformation political cover to continue
Talent and skills scarcity	A capability gap the external labour market cannot fill fast enough
Dynamic talent management capability	The organizational routine of sensing a capability gap and redeploying or reskilling people quickly
Structural rigidity	Layered hierarchy and narrow role design that slows decisions built for a more stable era
Barriers to Transformation
Change fatigue	Employee scepticism toward a new transformation after prior relabelled but unchanged initiatives
Risk-averse governance	Compliance and control functions that unintentionally block small, reversible experiments
The Agile Mindset
Fixed mindset	The belief that ability and intelligence are largely fixed, leading to avoidance of visible failure
Growth mindset	The belief that ability develops through effort and feedback, leading to treating failure as information
Agile mindset	The set of beliefs, transparency, collaboration, and adaptability, that underpins visible agile practices
Safe-to-fail experiment	A deliberately small, low-cost trial used to generate evidence before scaling a new practice
Psychological safety	A climate in which employees can surface problems and failures without fear of punishment
Case Evidence
Microsoft culture reset	Satya Nadella's public adoption of the growth-mindset framework to shift Microsoft's competitive, siloed culture
ANZ tribes and squads	ANZ Bank's structural reorganization into agile tribes and squads, paired with explicit mindset training
TCS reskilling at scale	TCS's large-scale internal reskilling programme addressing digital talent scarcity