If you owned a smartphone about a decade ago, there’s a decent chance you lost an evening to a chubby little pixelated bird with big lips and bewildered eyes. It flapped between green pipes that looked like they had wandered in from an old Nintendo game, and you controlled it with exactly one thing: a tap. Tap too much and you smacked into the top pipe, and tap too little and you plummeted into the bottom one. Either way, you were dead in about four seconds, and somehow you started again.
The game was called Flappy Bird, and it was made by a young programmer in Hanoi named Dong Nguyen. He built it in a few days and quietly released it into the App Store, where for months it did absolutely nothing. It was one more little game among thousands that nobody was playing.
Then, in early 2014, something happened that nobody has ever fully explained. Flappy Bird took off, not gradually but all at once, and suddenly everyone you knew was hunched over a phone muttering at a cartoon bird. People posted their high scores as if they had summited Mount Everest. At its peak, the game was reportedly bringing in around $50,000 a day in advertising revenue.
You would expect that to be the greatest moment of Nguyen’s life. But when people asked him why the game worked, he didn’t have an answer.
“I couldn’t predict the success of Flappy Bird.”Dong Nguyen, to Rolling Stone
The attention soon became unbearable. Reporters howled at him, and he was flooded with messages from players, parents, and teachers saying the game was taking over their lives. In February of 2014, at the very height of its popularity, he pulled Flappy Bird from the app stores and walked away from $50,000 a day.
Meanwhile, the rest of the industry did exactly what you would expect. They tried to copy it.
The clones
Every copy matched the surface. Almost none caught fire.
The app stores filled with imitators, each with a bird or a bee or a dragon flapping between some variation of pipes.
From the outside, they look exactly the same.
Illustration. Same bird, same pipes, very different outcomes.
Nguyen himself said as much at the time. Anyone could clone his game, he said, but nobody would ever make another Flappy Bird. That turned out to include him. About six months later he released Swing Copters, with the same pixel art and the same one-tap control, and the difficulty cranked even higher, almost as if the secret ingredient must have been how maddening the first game was. It got plenty of downloads and mixed reviews, and it never came close to the phenomenon that came before it.
I’m not telling this story to pick on him. He made something delightful, and he made choices about his own life that I respect. I tell it because it captures something every creative professional needs to wrestle with right now. He had a result, and a massive one, but he didn’t have a recipe. He couldn’t trace the line from what he did to what happened, and when you can’t trace that line, you can’t walk it again.
That is the idea I want to develop here. You are responsible not only for the work you produce but for understanding how that work came to be. It’s the third principle in VERVE, the framework at the heart of The Infinite Lever, and it matters more every month, because we are entering an era in which you can get impressive results without ever understanding how you got them.
A result you can’t trace is a lottery ticket. A process you understand is a capability.
We all carry a Flappy Bird machine in our pockets now. You type in a request and out comes a result, sometimes mediocre and sometimes genuinely brilliant, and very often you have no real idea why it turned out the way it did. You get the output without the reps.
I’m optimistic about these tools, and I use them every day. A tool that delivers in seconds what once took days is a near infinite lever, but a lever multiplies whatever force you apply to it. If you can’t say what force you applied, you can’t apply it again. The danger isn’t that the result is bad, because typically it isn’t. The danger is that the result is good and you have no idea how to do it again.
When you can’t explain how a piece of work came to be, three things happen. First, you can’t repeat it. A lottery ticket can be cashed once, but a career is built on delivering great work again and again, when the stakes are high and the deadline is tomorrow. Clients and organizations don’t hire you for one lucky result. They hire you because they trust you can do it again.
Second, you can’t improve it. When something you made falls flat, the only way to fix it is to understand which choices led to that outcome, and if you don’t know which levers you pulled, you can’t adjust them. You end up like Nguyen with his follow-up, guessing at the secret ingredient and turning up the dial on the wrong thing. This is how people slide into the plateau trap: we keep producing, but we stop growing, because there’s no understanding underneath the output to build on.
Third, and this is the hardest one, you can’t defend it. When a licensed engineer finishes a set of drawings for a bridge or a building, they place their professional seal on those drawings. That stamp is a declaration: I understand this design, I stand behind it, and if it fails, it’s on me. It doesn’t matter who drafted the lines or what software calculated the loads.
Every time you put your name on a piece of creative work, you apply that same stamp, whether you realize it or not. “The AI did it” is quickly becoming the modern version of “the dog ate my homework.” It doesn’t fly, and it shouldn’t.
If you ship it, you own it.
Your clients, your manager, and your audience are not paying for the output, because output is becoming nearly free and they can produce it themselves. They’re paying for your judgment, your intuition, and your taste, and judgment requires understanding.
None of this is an argument against using tools. It’s an argument about what you hand off when you use them. There’s a world of difference between handing off a task and handing off your understanding of the work.
Delegation
You can hand off the task.
Let the tools draft, sort, format, and calculate. That is what they’re for, and it frees you to spend your attention where it counts.
Abdication
You can never hand off the responsibility.
The moment you stop understanding why the work is the way it is, you’ve stopped being the author and started being the audience.
There’s one more reason this matters, and it may be the most important. Do you remember your math teacher telling you to show your work? I used to find that infuriating, because I had the right answer and couldn’t see what difference it made how I got there. But the teacher wasn’t asking because they doubted the answer. The answer was never the point. The point was how they knew you understood, and, more importantly, how you came to understand.
The process is where you grow. Every time you understand why something worked or why it didn’t, you make a deposit into your intuition and sharpen your instincts for the next project.
Two ways to collect results
Every result you accept without understanding is a missed deposit.
Do that enough times and you end up with an impressive portfolio and a strangely empty sense of what you’re actually capable of. You have the trophies, but not the muscle.
Illustration. Understanding compounds. Accepted results don’t.
This is why taking responsibility for your process isn’t a burden. It’s a gift you give to your future self, and it begins with a habit you can start before you ship anything this week.
Here is the question I’d ask yourself first.
If someone asked you tomorrow to create something of equal quality from a blank page, could you?
Before you ship
Three questions that put your stamp on the work.
Ask them of anything you’re about to send into the world. If an answer is no, that isn’t a reason to throw the work away. It’s a signal that you have some learning to do before you move on.
A result you can repeat is a capability.
Equal quality, from a blank page, on demand. That is what people are really hiring you for.
Could I do this again?A choice you can explain is a choice you made.
Not every step, but the critical decisions: where the idea came from, why this direction over three others, what you cut and why.
Could I explain how this was made?Hesitation is information.
This is the engineer’s stamp. If you feel any resistance, it usually means you haven’t yet done the work of owning the work.
Would I put my name on this if no one ever knew what tools were involved?If you can’t explain the meaningful choices in a piece of work, then you didn’t really make them. Something else did. Naming that honestly is uncomfortable, but it’s also the first step toward getting those choices back.
Next, start keeping what I call a decision trail. At the end of each meaningful project, take five minutes and write a short paragraph about how it came together. Note the key decisions you made, where you got stuck, what broke through and why it broke through, and what you’d do differently next time.
It doesn’t have to be elegant, and nobody is going to read it. Over time it becomes a map of your own creative process, and it helps you think about how you think. It will reveal patterns you’ve never noticed, because you’re so good at intuiting things that you usually move on without paying attention. You’ll start to see the conditions that bring out your best work, and that is knowledge no tool will ever hand you.
If you lead a team, there’s a small change that can make a big difference. Stop asking only “Is it done?” and start asking “Walk me through how you got there.” Ask it with curiosity, not suspicion, because you aren’t trying to catch anyone. You’re helping your team build the understanding that makes great work repeatable, and when people know they’ll be asked about their process, they start paying attention to it. When they pay attention to it, they begin to share and to grow.
This week’s Action Guide includes three questions to ask before you ship any creative work, a simple practice for tracing your own process, and discussion questions to help your team make great work repeatable instead of accidental. It’s free at toddhenry.com/start, because it’s not what you know but what you do that matters.
You can start the decision trail right now, with the last thing you finished.
Let’s go back to Hanoi for a minute. Dong Nguyen had what nearly every creator dreams of. He had a hit, and he had the attention of the entire world. But because he couldn’t trace the line from his process to his result, the hit was something that happened to him rather than something he could build on. The clones couldn’t recreate it, nobody could, and in the end neither could he.
You are going to have more access to impressive results in the coming years than any generation of creative professionals in history, and people with real skill will use these tools to make things nobody could have imagined. That is a remarkable gift. But results are not capability, and output is not understanding.
The people who thrive in this next season won’t be the ones who generate the most. They’ll be the ones who can explain what they made, stand behind it, and make it again, only better.
A hit is something that happens to you. A process is something you can build on.
Hear the full episode. Daily Creative, episode 132: Could You Do It Again?
Listen to the episode


