The Centaur StrategyDear Reader, Garry Kasparov's hands begin to sweat. Garry is the world's greatest chess player, but he has run out of moves. His opponent sits there, quietly waiting for Garry to hand him the victory. Garry realizes it's over...not only is he going to lose this game, chess has just changed forever. That's because Garry's opponent was an AI. On May 11, 1997, the world's leading chess player got beat by IBM's Deep Blue chess program, and it shocked the world. The summer after that defeat, Garry did some soul-searching in the wake of his defeat by AI. I'm sure you can relate. Garry didn't give up. He ran some experiments with another chess player and ended up inventing something that would be called the Centaur Strategy. Garry used a basic chess software to help him compute moves before he made them. This allowed him to find blind spots and offload the grunt work of calculating moves to the computer. Garry didn't have supercomputers or IBM compute tokens, so he made do with what was available. Years later when other chess players started using the strategy, they realized that he could beat the fancier chess programs and other chess masters. human + computer was greater than either the human alone or the computer alone. That's why the centaur name is so perfect because a centaur could totally kick the ass of both a human and a horse. The sum is greater than the parts. Amateur players using the Centaur Strategy and mid-tier computers beat both elite grandmasters and massive supercomputers. They won because their collaborative process was superior. You're probably already doing this without realizing it, but here's how to lean into the Centaur Strategy as a designer/builder with AI. Process beats genius and computeThe beauty of the Centaur Strategy is that a competent human with a good process for AI beats either a lone design genius or a lone AI most of the time. So think about your process and iterate on it. Here are some things you might try:
2 tests for a healthy centaurThe centaur strategy is about splitting up the work smartly, but AI is getting better every day, so the split will evolve. But there are two tests you can run on a task. Test 1: Are you above average or do you want to become above average at something? For example, I don't like AI to write for me, but some may prefer to hand over copy to AI. I've spent a lot of time trying to improve my writing, and I think it makes me a better thinker, so I will continue to struggle with writing copy. That test may not look the same for you, and that's ok. That test may also look different in five years, and that's ok, too. Test 2: Does it need a human touch regardless of "skill-level"? AI will probably get better than humans at many things, but that doesn't mean you should let AI do everything it's "better" at. For example, you will probably want to handle client and stakeholder communication yourself when real money is on the line. Strategy passes both tests for almost everyone which is why it's worth treating strategy as a domain you own no matter what. I like to think of Strategy as the Human Layer orchestrating AI and ensuring that the process is a human-driven collaboration. Here's 2 ways to start:
Cory Doctorow (author of Enshittification) has a new book that talks about what happens when you aren't in control of how you use AI, something he calls a "Reverse Centaur." The process for AI-human collaboration is still being determined, so now is the right time to start taking ownership of your process. The Centaur Strategy works best when you own the collaboration. TL;DR: Don't be a purist designer who gives up on AI and don't turn into a lazy slopper that treats AI output like an oracle. Be the Centaur. Guide the technical powers of the machine with strategic thinking. No More MosquitoesTornyol, a Y-combinator startup, has invented a drone that kills mosquitoes mid-air for $50/month. I guess you'll need another drone to clean up the mess. The internet is realizing that LLMs sound annoying because they're based on Reddit answers. Source Source Pre-Call Intel Prompt Use this to get some info and talking points before a call: You are an expert research assistant preparing me for an upcoming call. Use web search to look up [INSERT NAME HERE] and their company [INSERT COMPANY HERE], combined with any notes I paste below.
Provide a concise, highly scannable brief structured in exactly these sections:
Who They Are: Name, role, tenure, and a 1-sentence summary of what their day-to-day job likely entails.
Company Snapshot: What the company does, size/scale, and how they make money.
Likely Priorities & Pain Points: 2 or 3 core metrics, goals, or challenges this specific role faces right now.
Recent Signals: Any recent news, funding, product launches, or company changes.
Landmines to Avoid: Topics, old info, or sensitivities to steer clear of.
3 Sharp Questions: Tailored, high-value questions I can use to open the conversation or drive discovery.
Here is my extra background/notes (if any): [PASTE NOTES HERE]
Adapted by Jeff Humble from this Source
Talk to you in 2 weeks! ✌️ |
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
Founder of... Dear Reader, With all the hype around the new role designer/builder, it's worth looking at what that role looks like when you cut out the middle man. By that I mean, you build for yourself rather than your employer. I saved this on my Tumblr back in 2014: Think about how much harder it was to become a designer/founder in 2014 vs. 2026. That's great news, but the bad news is that the title "designer" has never been more uncertain. I'm bullish on designers in the age of AI. I'm...
How the Fountain Institute Started and Where It's Going by Jeff Humble Dear Reader, In case you missed it, Hannah dropped a pretty big announcement in the last newsletter. I wanted to tell the story of how the Fountain Institute started, why we’ve never had an “About Us” page, and where I think we’re headed next. How it started The Fountain Institute started when two friends decided to grab a beer and work...then kept doing it for 7 years. There were many false starts along the way. Starting...
A goodbye and the story that goes with it By Hannah Baker Dear Reader, There's an idea I've been chasing for most of my working life, and I didn't know it. I want to tell you about it, and about something that happened a few years ago that I haven't talked about much publicly, but that belongs in this story. Some of you might already know this about me, but I used to work in education departments at museums. The thing that grabbed me in the museums was a shift that happened, away from the...