You're Getting Experience. You're Not Getting Better.

Ten years in the same craft, and still hitting the same ceiling. Not a plateau — the same ceiling. The one you first hit in year three.
This is more common than anyone admits out loud. Not because people are lazy. Because the assumption underlying the value of experience turns out to be wrong: that time in a role accumulates into mastery. It doesn't. Not automatically. Not even usually.
The Automaticity Trap
When you first learn a skill, every decision is conscious. You're thinking through each step, making deliberate choices, catching errors. Then something shifts — the skill becomes automatic. You stop thinking about it. You stop noticing when you're wrong. You start executing in a groove you carved years ago.
K. Anders Ericsson spent decades studying expert performance — violinists, chess players, surgeons, memory athletes. The pattern he found wasn't that experts practiced more hours. It was that they practiced differently. His research, summarized in Peak (2016) and across decades of studies in journals including Psychological Review, showed that what separates elite performers from experienced-but-average ones isn't the volume. It's whether the practice is designed to push past automaticity.
Naive practice — doing what you already do, more times — produces automaticity. That's useful when a skill needs to be reliable under pressure. But automaticity is the death of improvement. When a task runs on autopilot, you stop generating information about what's going wrong. Errors become invisible. The groove gets deeper, not better.
A senior writer who has published five hundred articles in the same format has learned to ship reliably. They may not know — unless someone tells them specifically — that their hooks have become formulaic. They stopped noticing in year two. The pattern that once required conscious effort became a reflex, and reflexes don't self-correct.
Why Knowledge Work Has a Feedback Problem
Ericsson's deliberate practice has four components: it's designed to improve specific aspects of performance, it involves repetition, it provides continuous feedback, and it requires high mental effort. Most knowledge work satisfies one of these. Maybe two.
The feedback problem is the critical one. A tennis coach watches you and tells you in real time that your grip shifts on hard shots. A programmer may not discover their architecture decision was flawed until production, years later — and even then, the learning usually gets attributed to "that project" rather than absorbed as an update to a mental model of design.
Some fields have tight feedback loops built in. Emergency medicine: you know quickly whether the patient stabilized. Competitive chess: the game ends with a winner. Music: the note is in tune or it isn't. These loops make deliberate practice possible even when practitioners aren't explicitly designing it.
Most knowledge work lacks this. Writing, strategy, management, design — the feedback that would tell you what to improve arrives delayed, aggregated, filtered through other people's interpretations. It comes too late and too vague to function as correction.
This isn't an excuse. It's a structural design problem worth solving. Emotional granularity — the ability to make precise distinctions within your experience — applies here: if you can't name specifically what you did well or badly, you can't correct it. Vague feedback produces vague improvement, which looks identical to no improvement at all.
The Flow State Distraction
Flow — Csikszentmihalyi's concept of deep engagement where skill matches challenge — feels like growth. It isn't.
Flow requires that challenge and skill be roughly equal. Too much challenge produces anxiety. Too little produces boredom. The flow channel is where work feels effortless and absorbing. It's also where you're not improving, because you're operating squarely within existing competence.
Deliberate practice requires the opposite: working at the edge of what you can currently do — the zone of proximal development, per Vygotsky — where challenge slightly exceeds skill. That zone is uncomfortable. You make errors. You slow down and think consciously again. Progress feels like regression before it feels like advancement.
This is why people who love what they do often plateau. They keep finding the flow channel and staying in it. Flow is rewarding. Deliberate practice is often not. The people who keep improving aren't always the ones who find the work most satisfying in the moment — they're the ones who have developed tolerance for the uncomfortable edge.
Presence as a discipline involves stepping out of autopilot and attending fully to what's actually in front of you. Improvement requires something structurally similar: a deliberate interruption of the groove. The difference is that presence is about receiving. Deliberate practice is about targeting the specific thing that isn't working.
What a Feedback Architecture Looks Like
If the problem is feedback loop design, the solution is building one deliberately rather than waiting for it to emerge.
For knowledge workers, this means creating structured after-action reviews — not "how did the meeting go?" but "at what specific point did I lose the room, and what signal preceded that moment?" It means finding people two levels above your current skill who can name the gap specifically, not encourage you generally.
It means designing tasks to reveal errors quickly. A writer who submits to editors who give specific feedback gets faster signal than one who blogs to an audience that only says "loved it." A product manager who runs small experiments with clear success criteria gets faster signal than one who ships large features and reads aggregate metrics three months later.
The goal is closing the loop between action and consequence — and making consequences legible enough to learn from. Legibility is the work. Feedback exists; the question is whether it's specific enough to point at the right thing.
The Compound Effect Works Both Ways
Here's what the experience illusion costs over time. Every year of naive practice doesn't just fail to improve you — it cements the current pattern more deeply. Automaticity compounds. Grooves become harder to exit the longer you stay in them.
This is why senior people are sometimes more resistant to correction than junior ones. It isn't stubbornness (usually). They've been executing on autopilot longer. Correction doesn't just feel wrong — it requires dismantling something that has become genuinely automatic, which carries a cognitive cost that's hard to explain to someone who hasn't done it.
The flip side: people who build deliberate practice loops early — who treat feedback as structural rather than incidental — compound in the opposite direction. Not faster accumulation of the same habits, but actual update of the underlying model. The same hours produce different outcomes depending on whether those hours include correction.
The Question That Changes What Experience Means
More time doing what you already do well is not the path to becoming better at it.
The question that matters is not "how many years have I been doing this?" It's "what feedback system am I embedded in, and is it specific enough to generate real correction?"
Without a clear answer to the second question, experience is scar tissue — evidence of past exposure, not evidence of growth. You've been in the room. That's not nothing. But being in the room and learning from it are different things, and only one of them requires intentional design.
You probably don't need more time in the seat. You need someone — or something — that can tell you with precision exactly what you're still getting wrong.
Photo by Matteo Basile via Pexels.