The Skill Isn't Using AI — It's Reading the Moment
Three weeks. Two continents. Two clients. A reminder I needed.
Over the past few weeks I ran innovation sprints with two very different organizations — one in aviation, one in MedTech. Same toolkit. Same facilitator. Two completely different rhythms — and by the end, the contrast had taught me something I keep having to relearn.
The airline: build fast, learn faster
At the airline, we went straight to the airport. We watched how people actually work, and we talked to the teams on the ground. Within hours, I was coding working prototypes based on what we'd learned — and handing them right back to the people who would use them. Not to impress anyone. To learn faster.
Where will this screen live? How do you hold the device? What matters in the 30 seconds you actually have? Each answer made the next version better. By day five, we had a functional MVP. Not a concept. Not a slide deck. A working solution — built with AI, shaped by the people who'll actually use it.
The MedTech sprint: the discipline to slow down
At the MedTech company, the energy was completely different. We had a motivated team, great people, and AI tools ready to go. By day two, everyone wanted to start building. The pull was real.
But we slowed down. The challenge was more complex, and we needed to understand it properly first. So we kept talking to people. We ran interviews. Sometimes we used AI in parallel — to research and process what we were hearing in real time.
And then it happened. One person shared an insight that had never been written down anywhere. Not in any report. Not in any database. Not in any AI. The room went quiet. Nobody expected it. And it gave us exactly what we needed — the confidence that our direction was right, clarity on where to focus, and a wave of new opportunities we wouldn't have seen without that conversation.
Same team, same AI tools, same energy. What's the move?
You can't read it off the surface — only off the signals. Flip them and watch the right call change.
Reading the moment
Here is what I took away from these three weeks. It is not about choosing between AI speed and human depth. It is about reading the moment. Sometimes the right move is to build fast, test fast, and iterate the same day. Sometimes it is to slow down, stay in the conversation, and trust that the insight you need hasn't been written down yet.
The skill isn't using AI. Everyone can do that now.
The skill is knowing when to accelerate — and when to stay in the room a little longer.
Keep reading
Stop Delivering Recommendations
The gap between insight and implementation is where good ideas die. It doesn't have to exist.
8 min readNot Everything Needs AI
We've started reaching for a model the way we used to reach for Google — by reflex. But much of what we hand to AI is work a plain rule does faster, cheaper, and more reliably; in one study a regex matched an LLM at around 28,000x the speed. The scarce skill was never using AI. It's knowing what doesn't need it. With a small switch you can feel.
6 min readAI Made Building Free. Taste Is the New Bottleneck.
Andrej Karpathy can build an app in an hour, in a language he doesn't know. When anyone can build anything, why is so much of it still worthless? Because building was never the hard part — and now that it's free, the one scarce thing left is taste: knowing what's worth building, what "good" is, and what to cut. With a small test you can feel.
7 min read