TL;DR: At HRcoreNordic 2026, Natal Dank, co-author of Agile HR and the person who launched the first Agile HR Meetup back in 2016, named "Agile HR is Dead" as a top priority in PXO Culture's 2026 HR & People Priorities Report. Hold for the plot twist: she isn't abandoning agility. She's retiring the cargo-cult version of it — teams that copied the rituals, frameworks and squad structures without the intent behind them. The principles were never the problem. The framework-first implementation was.
A room that already knew the answer wasn't "more"
Two days in Copenhagen with 250+ HR leaders, and a clear pattern ran through the sessions. AI is accelerating faster than most organizations can absorb. Skills are shifting before strategies can catch up. And when everything feels uncertain, the instinct is to reach for more: more dashboards, more assessments, more frameworks.
The room didn't buy it. What kept surfacing was the opposite instinct: less framework adoption, more contextual thinking. Which is exactly why one of the event's most-discussed ideas was a deliberately provocative one — Natal Dank's claim that Agile HR is dead.
Who said it, and why it carries weight
The claim matters because of who made it. Dank co-founded PXO Culture, is Chief Trendwatcher at the HR Trend Institute, and was named one of HR Magazine's Most Influential HR Thinkers in 2022. She hosted that first London-based Agile HR Meetup in 2016, which grew into a global movement, and co-authored Agile HR: Delivering Value in a Changing World of Work (Kogan Page, 2020) with Riina Hellström.
So this isn't a skeptic taking a swing from the sidelines. It's the movement's own architect saying the thing didn't land the way it was meant to. That's what makes it a plot twist rather than a hot take.
What did Natal Dank actually mean by "agile HR is dead"?
She did not say agility was wrong. As her report puts it plainly: "we still stand by Agile HR". What she's describing is the death of a specific, hollowed-out version — agility-as-theatre, where teams perform the visible artifacts of agility and quietly lose the purpose those artifacts were meant to serve.
In other words, HR borrowed the ceremonies from software development without borrowing the mindset. You can run stand-ups, sprints and retros every week and still be just as rigid, slow and disconnected from real outcomes as the process you replaced.
What went wrong with agile HR?
Dank's diagnosis is a list of six trade-offs where HR optimized for the wrong half of each pair:
- Framework-led adoption instead of a contextual toolkit. Teams rolled out a named framework wholesale rather than picking the few practices that fit their actual context.
- Rituals and ceremonies instead of work flow. The meetings became the point. The flow of work they were meant to improve got lost.
- Speed instead of sustainability. Agility got read as "go faster," not "stay adaptable over time."
- Customer needs instead of product value. Reacting to every request rather than building durable value for people and the business.
- Functional teams instead of an organizational system. Optimizing one HR squad while ignoring how the whole system connects.
- Episodic change instead of fundamental uncertainty. Treating change as a project with a start and end date, instead of building for a world that doesn't stop moving.
The pattern is consistent: HR kept the surface and dropped the substance. Or, in the report's words, rituals outpaced outcomes.
Is agility still relevant in 2026? Yes, that's the point
The report's subtitle says it directly: "Plot twist...it's an evolution." Declaring Agile HR dead is a way of clearing space for what agility was always supposed to be: a way of working that absorbs uncertainty, fits its context, and improves the flow of real work. The intent survives. The branded, ceremony-first implementation is what gets retired.
The shift Dank points to is from doing agile to being adaptive — what she frames as "a shift away from agility as a method toward adaptability as a system capability." Practically, that means choosing practices for your context rather than installing a framework because it's the standard; measuring whether work actually flows better, not whether the ceremonies happened; designing for the whole system, not one team's local efficiency; and building for ongoing uncertainty rather than treating each change as a discrete event with a finish line.
Where this meets the work we see every day
Here's the part that connected the report to the room at HRcoreNORDIC. Dank's "contextual over framework" and the event's wider mood — less admin, more leadership; less framework, more thinking — are the same instinct seen from two angles. And it's the same instinct behind the talk Lisa Gentou-Hedkvist gave on Day 2: The visibility paradox — why HR has more data and less workforce clarity than ever.
Her case was that clarity doesn't come from more information. It comes from better connection — linking skills intelligence to real decisions, so HR stops guessing and starts leading with confidence. Put the two talks side by side and they rhyme. Dank says stop performing agility and start being adaptive. Lisa says stop gathering data and start connecting it. Both are arguing that the answer isn't more — it's better-connected, more contextual, anchored in the actual problem you're trying to solve.
That matters because adaptability isn't free-floating. In the report, the thing Agile HR evolves into is workplace elasticity — and as Dank writes, "Workplace elasticity doesn't reject Agile HR. It absorbs it." But you can't be elastic about a workforce you can't see. Bending, stretching and reforming under pressure depends on knowing what your people can actually do — which skills you have, where the gaps are, and where the next move should come from. Contextual thinking needs a foundation, and for skills-based organizations that foundation is a clear, connected view of the workforce. Without it, adaptability is just another ceremony.
What HR teams can take from this
The shift Dank points to is from doing agile to being adaptive. Practically:
- Choose practices for your context rather than installing a framework because it is the standard.
- Measure whether work actually flows better, not whether the ceremonies happened.
- Design for the whole system, not one team's local efficiency.
- Build for ongoing uncertainty rather than treating each change as a discrete event with a finish line.
If you want the constructive other half of this, the version of HR that PXO calls product-led and systemic, we unpack it in our companion piece on product-led HR and treating talent as a system.
Yes. It appeared as a stated priority in PXO Culture's 2026 HR & People Priorities Report, presented at HRcoreNORDIC 2026, and framed explicitly as a "plot twist" given her role as co-author of Agile HR.
No. The critique targets superficial, framework-first adoption. The underlying principles of adaptability, flow and context-fit remain central.
A co-founder of PXO Culture, Chief Trendwatcher at the HR Trend Institute, co-author of Agile HR (2020), and one of HR Magazine's Most Influential HR Thinkers in 2022. She launched the first Agile HR Meetup in London in 2016.
Optimizing for the visible artifacts of agility — rituals, frameworks, speed — instead of the outcomes they were meant to produce: flow, context-fit and sustainable adaptability.
