There is a particular kind of noise in organizations right now and it goes something like this: “Your skills are already half-obsolete, the pace of change is accelerating, the half-life of expertise has shrunk to somewhere between two and five years depending on your field and your proximity to AI…”
And the only rational response, so it seems, is to embrace continuous learning with a kind of urgent, restless fluidity; to reskill before you become irrelevant, to unlearn before your old frameworks close off the new reality, to move faster because the world demands it.
I don’t think this is entirely wrong. Some of it is genuinely important, and the World Economic Forum’s Future of Jobs Report 2025 gives it real empirical weight: 39% of key skills will be transformed or rendered obsolete by 2030, and the pressure to reskill is as real for senior leaders as it is for anyone else.
I am not arguing against learning. I am passionate about it. But the assumption embedded in almost every L&D conversation I witness is that faster is categorically better, that urgency is always a useful emotional fuel. I am increasingly convinced that the particular tempo we have assigned to learning is itself a problem we have not yet named clearly enough.
The marathon we’ve been asked to sprint
The half-life of a skill in AI-adjacent fields is estimated at around two years. In more traditional professional domains, it sits somewhere between four and five. These numbers arrive in most organizational conversations in a specific emotional register, which is alarm. “Act now. Change your learning culture. Build new competencies before the old ones expire.” The implied logic is that the appropriate response to a shorter half-life is a higher learning velocity.
And yet, alongside all of this, there is another reality that rarely appears in the same conversation. Lynda Gratton and Andrew Scott documented it carefully in The 100-Year Life: half of the five-year-olds alive today can expect to live to 100. The Stanford Center on Longevity has been convening researchers and leaders around the implications of that fact for years now, and what comes out of that work is that most of the people currently in leadership positions will spend somewhere between 35 and 50 years in active professional life.
The question therefore is not just how to reskill. It is what kind of learner a person needs to become to sustain purpose and relevance across half a century of working, across a career that will almost certainly require not one but several fundamental reinventions, across a professional life that will be shaped by forces we cannot currently name or anticipate.
Place these two realities side by side, and the mathematics becomes, to me, quite vertiginous. If the half-life of a skill is two to five years, and a career now spans 40 to 50 years, then to sustain relevance through purely additive, velocity-first reskilling, you would need to rebuild yourself completely somewhere between 10 and 25 times.
This is not a learning challenge. It is a structural mismatch between the temporal logic of human development and the temporal logic we have been sold about it, and I think we are only beginning to pay for it in the form of a very particular kind of organizational exhaustion, a professional hollowness, a feeling that no sooner have you arrived somewhere than you are already behind again.
What Carlo Petrini understood about slowness
When thinking about how tempo correlates with the human experience, how the passage of time and value creation interact, it’s hard not to think of Carlo Petrini, the founder of the slow-food movement, who passed away just this month. He frequently comes up in discussions with my partner around food and what we want our child to understand about eating.
Petrini is one of those rare figures whose argument, once really internalised, becomes hard to leave behind. TheItalian activist and gastronome spent four decades building Slow Food International, founding Terra Madre and the Salone del Gusto in Turin, growing a network of nonprofits and food communities that now spans more than a hundred countries, all from a single, stubborn conviction that what we eat is never just sustenance, it is a form of knowledge, a form of culture, a form of politics.
In 1986, reflecting on seeing a McDonald’s open near the Spanish Steps in Rome, he started what became the Slow Food movement, not a protest against eating, but against what eating was becoming: decontextualized, rapid, disconnected from the intelligence embedded in how food grows, how it is prepared, and what it means to sit with people and eat together.
What Petrini argued is that speed applied to the wrong things destroys the very quality it promises to deliver efficiently. What is lost when food is made fast is not only flavor. It is the accumulated, non-codifiable knowledge of how to grow things well, how to work with the nature of ingredients rather than against them, how to understand what you are eating and why it matters that it comes from somewhere specific.
The Cittaslow movement, the slow architecture of Christopher Alexander, the slow tourism and slow arts movements that have followed, all make the same underlying discovery: that slowness, as a practice, is a proxy for depth, attention, and the recognition that some forms of quality require time not as an inconvenience but as a condition of possibility. Slow, in this sense, has nothing to do with pace. It is the opposite of thoughtless.
Carl Honoré, who has spent years documenting these movements, argues in his Substack newsletter Tempo that slow learning is not lazy or resistant to change. It is learning that is genuinely digested, connected to experience rather than merely overlaid on it, developed through the kind of sustained attention that turns information into understanding and understanding into something you can actually use under pressure. The quality of learning, the degree to which new understanding becomes embodied and available, is overwhelmingly a function of the depth of attention given to it, not the speed of its acquisition.
Towards a practice of slowness in learning
So what would it mean to take slowness seriously as a learning practice in organizations? Not as resistance to change, and certainly not as a romantic attachment to anything already obsolete, but as a considered, deliberate, even strategic claim about how human beings actually build durable capability across long careers.
In the work we do at WDHB, we encounter something quite consistently. Leaders who navigate complexity – the kind that does not resolve into a new skillset or a refreshed competency model – tend to be people who have spent real time with a small number of difficult questions. They have let their understanding slow down enough to become something close to wisdom, which is distinct from knowledge in that it includes the felt sense of when to apply what you know, and, equally important, when not to. This is not something you can acquire at an accelerated pace.
The Revue Gestion at HEC Montréal describes slow management partly as the practice of “wasting time” usefully, which is perhaps a formulation, somewhat paradoxal, that actually carries the idea well. To take slowness seriously (as part of a learning culture) means creating deliberately protected time for depth, asking which skills are worth developing with real, sustained attention rather than just surface fluency, and trusting that a person who has understood something difficult is more durably capable than one who has completed 40 modules. It means designing programs that return to the same hard questions from different angles rather than moving perpetually toward whatever is newest. It means, at its most fundamental, refusing the equation between learning velocity and learning quality, which are not, in fact, the same thing, and may sometimes move in opposite directions.
The slow movements in food, architecture, and urbanism made their argument against a dominant logic that seemed, at the time, irresistible. They were not nostalgic. To me, they were and still are making a different claim about what quality means, and about what, in the end, lasts.
So what does lasting experiential learning look like in practice?
At WDHB, we have noticed something that I think is worth naming as a kind of empirical footnote to the argument above:
People come to our programs the first time for the content, because that is what excites them at the point of registration.
They return for a second time for the reflection and debriefings we offer, because somewhere along the way they have understood that it is in the space we create for reflection and emergence of collective ideas, not in the input, that the needle actually moves.
They come the third time for even less structured elements of our experiences, like the transfer bus time, the somewhat captive idle time between sessions where the conversations happen without a specifically assigned outcome. They have come to recognize that it is there, in what might look like inefficiency, that something closer to genuine insight tends to occur. We think of these as systems of serendipity, and they are not accidents of program design, they are the point.
What follows is an attempt to translate the argument of this article into a brief, for three different kinds of actors.
For those who design learning experiences:
Design for return, not for novelty: Build programs that bring participants back to the same hard questions from different angles, rather than perpetually introducing new content. The second and third pass at a question is often where understanding actually forms.
Protect the margins: build in unstructured, bounded time without assigning it an outcome. These are not inefficiencies to eliminate, they are conditions to design for deliberately.
Resist the completion metric: a participant who has grappled with one difficult question is more durably capable than one who has completed 40 modules.
For those who facilitate:
Understand the arc of return and design your attention accordingly: The content brings people in, the debriefing is where the needle moves, and the bus time is where the real connections form, which means the margins deserve as much care as the sessions themselves.
Create space for unlearning before adding new content: surface the existing frameworks in the room, make the old assumptions visible, before building on them. And when the group signals it wants to move faster, that is often the moment to slow down and ask what would be lost if you did.
For individuals navigating long careers:
Choose depth over breadth: Identify the two or three questions worth sustained attention, and resist the anxiety of reskilling in every direction simultaneously. The half-life argument is real, but its answer is not to rebuild yourself completely every two years.
Stay with what you find difficult: discomfort with a situation or idea is usually a signal that your current model is
Let's start a conversation!
Whether you have a specific need, are looking for a new partner, or simply curious about what we do, our team would love to hear from you.