Age vs Experience: Why Being Young Doesn’t Disqualify You

I wrote the bulk of this post the week I turned twenty-three, after a casual Skype call with a friend put me on the defensive about my age. Almost two decades later, the argument has only gotten stronger: age is a terrible proxy for capability, and most of the people who use it as a filter are quietly losing the only competition that actually matters.

I’m leaving the original essay below intact, because the way I argued it at twenty-two is still the way I’d argue it at forty. What I’ve added at the bottom is the framework I didn’t have language for back then, the one I now teach as the 10,000 Hours of Play (10K HP) life-gamification system. It explains why hours-on-task beat years-on-the-clock, why the “experienced veteran” is sometimes the most stuck person in the room, and what to actually do if you’re young and feeling dismissed for it.

Three things you’ll get out of this post: the original Web 2.0 Expo argument I made on the spot in 2009 and never had to retract; the bridge between that argument and Core Drive 2 (Development & Accomplishment) in the Octalysis Framework; and a concrete way to compress your hours so the calendar stops being your bottleneck.

⚡ Speed Run Notes

• Age is a low-information proxy. Hours of focused practice in a field is the better signal, and it’s how I won every “you’re too young” argument I’ve ever been pulled into.
• A passionate twenty-two-year-old who has logged five years of obsessive hours can outperform a forty-five-year-old who logged five months of attention split across twenty-five years on the job.
• This isn’t motivational language. It maps onto Core Drive 2 (Development & Accomplishment) in the Octalysis Framework: progress comes from real reps, not from the calendar.
• The trap most “experienced” people fall into is the NPC trap: showing up for years without ever choosing the game they were playing. Years accrue; mastery doesn’t.
• If you’re young and being filtered out, you don’t argue against the filter. You stack so many genuine hours and shipped results that the filter looks ridiculous on you.

Table of Contents

About the Creator of the Octalysis Framework

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003, years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and 3,700+ more academic publications. Explore his books here.

I started studying gamification in 2003 and have been arguing the hours-not-years thesis ever since I was the youngest founder in any room I walked into. The 10,000 Hours of Play framework I now teach is the formal version of the case I made off the cuff at the Web 2.0 Expo when I was twenty-two, dressed up with the Octalysis Framework’s Core Drive language. Nothing in this post is theoretical for me. I’ve watched the calendar argument lose every time it’s been tested against real shipped work.

Pre-Judgements Made on Age

A few days ago I had a good Skype chat with my friend and internet personality Jamie Varon. We talked about her goals of breaking through social boundaries and setting people free from surrounding expectations.

In the middle of the conversation, we started talking about young social media marketers. Being completely on topic, she asked me, “and how old are you?”

That’s when my mind suddenly made a little pause.

I usually feel a little reserved when people ask about my age, particularly because I know that people inevitably make some judgements based on age. Up until that point, my age did not put me on the good side of that judgement.

I’m a pretty open person, so while my mind had a pause, I promptly answered: “I’m twenty-two. I’ll actually become twenty-three on Saturday.”

Jamie’s response was not surprising: “Wow, you’re only twenty-two? I thought you were much older than me, at least twenty-six. I actually find that fascinating.”

I was already used to that response. While Jamie finds it fascinating that I am only twenty-two, most people don’t. Most people are looking for a reason to short the conversation, and “you’re young” is the cheapest one available.

Is Being Young a Valid Disqualifier for What You Want to Do?

I remember last year at the Web 2.0 Expo, before I gave the closing presentation at the Launchpad section. Tim O’Reilly walked up to greet me. The first thing he said was, “Hi, I’m Tim O’Reilly. Are you ‘wig’?”

“No, but I work for them,” I responded. (At that time I worked for the gamification company called wig.com, which I joined when there were five people in the office.) Then Tim looked at me up and down, blurted out, “Wow you must be only nineteen years old.”

That’s quite a comment to receive from one of the legends of Silicon Valley two minutes before walking on stage.

I don’t fault people for noticing my age. The judgement isn’t always wrong. People with less life experience often have less perspective, fewer reps, less calibration on how badly things can go. The lazy version of the heuristic is to use age as a hard filter and skip the question that actually matters: what has this person actually done with their hours?

The good news is that filter cuts both ways. The same heuristic that tries to disqualify you also under-estimates you, which gives you free upside if you can ship.

Kids Doing Magic Tricks

You’ve seen it. A six-year-old does a clean three-card monte, or a nine-year-old plays Chopin from memory, and the entire room reacts the same way: “How is that even possible?”

It’s possible because the kid has logged thousands of hours on the specific thing they’re showing you. Most adults react with surprise because they’ve spent zero hours on it themselves and they assume hours are accumulated by aging. They’re not. Hours are accumulated by spending them. A six-year-old who has done card tricks for an hour every day for three years has more card-trick reps than the forty-five-year-old in the room who has watched magic on YouTube three times.

Once you internalize that hours-on-task is the actual variable, the “but you’re so young” reaction starts to look upside down. The right reaction to a young person who’s good at something is not surprise. It’s a calibration update: this person has been spending their hours differently than the people I usually see at this age.

It’s Hours, Not Years

Here’s the cleanest way to state the argument:

Capability tracks hours of focused practice in a domain. It does not track years on a calendar.

If a twenty-two-year-old has been obsessively doing one thing for ten years, fifty hours a week, they have ~26,000 hours on that thing. If a forty-five-year-old has been doing the same thing as a side concern for a few hours a week across twenty-five years, they have ~10,000 hours on it. The twenty-two-year-old has more reps. They’ve shipped more, failed more, recovered more, calibrated more, and built more pattern-matching muscle. The forty-five-year-old has more candles on their birthday cake, which is a different thing.

This is why I’ve never seen a calendar-based argument hold up under inspection. The moment you ask “how many hours have you actually put into this,” the conversation shifts away from age and toward something measurable.

The same logic explains why kids who’ve spent their early years gaming, programming, building Lego sets, learning languages, or running little side hustles often outpace adults who walked the conventional career path. Their hours hit the meter early. The conventional adult was never measuring hours, only years. They weren’t lazy; they were unmeasured.

The Key Is to Level Up Faster than Others

Since ability and credibility track hours and not age, the move for a young person is obvious: spend committed time leveling up faster than your peers, in a direction you’ve actively chosen.

That is why identifying your life goals and your real passions matters so early. Direction multiplies hours. The wrong hours don’t compound; they pile up sideways. The right hours stack into capability that other people can see and feel within a couple of years.

The earlier you start, and the more focused hours you put into something each day, the stronger you will become in that field. By the time you’re twenty-two, twenty-five, twenty-eight, you’ll already be operating at a depth most of your peers won’t reach until forty.

Then the calendar argument inverts. The same people who told you “you’re too young” will move to “you’re too unique to compete with.” That’s a much better problem to have. As long as you continue to create real value for everyone around you, your credibility builds itself, and the respect of your colleagues follows.

Soon, the next generation of high schoolers will think they’re more capable at a lot of things than most grown-ups, and they will probably annoy the heck out of the millennials. Each wave covers the one before, the way the ocean covers the beach. The trick is to keep being the wave instead of the sand.

The 10,000 Hours of Play Update (My Modern Lens)

That’s where the post used to end. Here’s what I’ve added since I formalized my own thinking into a framework called 10,000 Hours of Play (10K HP).

10K HP is the system I now teach for treating your career, your purpose, and your personal mastery the same way you’d treat a serious RPG: choose a game, pick a class, log focused hours, level up your stats, and design the next ten thousand hours instead of letting them happen to you.

The framework starts with one question. Are you actively playing your own game, or are you a non-player character in someone else’s?

An NPC is a background character: someone who exists to serve someone else’s plot. They show up. They react. They don’t choose. Most “experienced” people I meet who failed to compound their decades on the calendar were NPCs the whole time. Their forty-five years aren’t forty-five years of focused reps. They’re forty-five years of someone else’s quest log being passively executed. That’s why a young person with three years of self-directed hours can leapfrog them. The young person picked a game. The veteran never did.

10K HP has six steps grouped into two phases:

• Phase 1, Know Yourself: Choose your game. Know your class. Know your party.
• Phase 2, Grow Yourself: Build your stats. Build your guild. Beat the boss.

The argument I made at twenty-two was Phase 2 logic without the Phase 1 vocabulary. I was telling people that hours mattered more than years, but I hadn’t yet given them the upstream filter: hours only compound if they’re spent on a chosen game. A young person who logs 26,000 hours of NPC behavior is no more capable than the forty-five-year-old NPC, just younger and more burned out.

Why “Leveling Up” Is a Real Mechanic, Not a Metaphor

The Octalysis Framework I developed is built on eight motivational forces I call Core Drives. The most relevant one to this post is Core Drive 2 (CD2): Development & Accomplishment. CD2 is the engine behind every “I leveled up” feeling you’ve ever had, and it’s why games hold you for thousands of hours when most jobs can’t hold you for one quarterly review.

CD2 has three working parts:

• Visible progress. An XP bar, a stat sheet, a published portfolio, a public commit history. Without visible progress, the hours blur and motivation collapses.
• Meaningful challenge. Something you have to actually be better than yesterday to clear. Not a participation ribbon.
• Earned reward. A bump in capability the world recognizes. Not a fake badge.

The reason age-based judgement feels so deflating is that it ignores all three. It tells you that what you’ve actually built doesn’t count because the calendar didn’t tick the right number of times. CD2 doesn’t work that way. CD2 works on reps, on visible progress, on real challenge cleared. If you’ve been logging the work, your stats are higher than your age suggests, and the people who matter will eventually price that in.

The practical move: build your XP bar in public. Ship work that anyone can see. Speak about it. Write about it. Let the hours leave a trail. The older people in the room don’t have a way to argue you down once your trail is longer than theirs.

What I’d Tell Twenty-Two-Year-Old Me Now

If I could re-record the Skype call with Jamie, here’s what I’d add to the answer I gave her.

One. Don’t argue with the calendar. The calendar argument is bait. Every minute spent defending your age is a minute not spent extending your hours. Smile, nod, build.

Two. Pick the game now. The biggest cost of being young isn’t being underestimated. It’s spending years racking up hours in a direction you didn’t choose, then waking up at thirty and realizing the hours don’t compound the way you wanted. Phase 1 of 10K HP exists to prevent exactly that.

Three. Make your hours public. The kid doing magic tricks works because you can see it. Whatever your craft is, build the equivalent of a stage. A blog. A GitHub. A YouTube. A weekly Substack. Hours that nobody can see don’t establish your credibility. Hours that anyone can verify do.

Four. Find older mentors who measure hours, not years. The senior people who will help you most are the ones who already know that calendars lie. The ones who don’t aren’t worth the energy of the conversation. The filter applies in both directions.

Five. Stop asking permission. The Web 2.0 Expo gave me the closing keynote slot in the Launchpad section because I’d already done the hours by the time I was twenty-two. Tim O’Reilly’s surprised reaction had no bearing on the slot they’d already given me. The work earned the slot. Permission would have cost me years.

The original post ended with “each wave covers the one before.” I still think that’s right. The deeper move is to be the wave that’s already studied the shoreline, the tide tables, and the rocks underneath, instead of the wave that’s just energetic and young. Both crash. Only one knows where it’s going.

Related Reading

• Core Drive 2: Development & Accomplishment — The Complete Guide
• The Octalysis Framework Overview
• Life as an RPG: Convert Your Life into a Game Worth Playing
• How to Master Almost Anything With a Few Principles
• Actionable Gamification — The Book

If you’re young and stuck in the calendar argument, the most useful thing you can do this week is spend the next two hours putting your hours somewhere visible. Start a public log of what you’re working on. The senior people who matter will look at it. The senior people who never look weren’t going to help you anyway. If you want the full 10K HP playbook, my book Actionable Gamification is the closest thing I have to it in long form, and the Core Drive 2 guide is the place to start if you want to design your own visible-progress system.

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?