What Entrepreneurs Can Learn from How We Learn
You built a system that works for you — the same desk, the same morning block, the same runbook for figuring out a new market or a new tool — and you trust it because it feels productive. But founders are constantly forced to learn fast, under pressure, in domains they didn't train for: pricing, hiring, a regulatory filing, a new ad platform. The habits that feel most disciplined — one dedicated learning environment, long unbroken study blocks, waiting until you've "got it" before testing your understanding on a real customer or investor — are exactly the intuitive habits that don't hold up well against how memory actually works. That mismatch is expensive when the thing you're learning is your own business model.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Question the founder study habits you assume are working
Founders often treat a single, tightly controlled work environment as a badge of discipline — noise-canceling headphones, one desk, one system, every time. It feels efficient. But that consistency is one of the intuitive habits worth questioning rather than trusting by default.
A founder learning a new analytics platform blocks off three uninterrupted hours at the same desk, reads the documentation start to finish, and closes the laptop feeling prepared — only to freeze the first time a real dashboard doesn't match the tutorial.
Before your next deep-work block, write down the one assumption you're making about how you'll retain what you learn — then deliberately test it against a real scenario, not just the material itself.
Vary where and when you wrestle with new material
Founders tend to concentrate learning into marathon sessions because it feels like the only way to make a dent. But changing the setting — a different room, a different time of day, a different device — and spreading the same material across several shorter sessions tends to stick better than one long sitting, even though the long sitting feels more thorough in the moment.
A founder trying to learn a new fundraising framework spends one full Saturday cramming it, then can't reconstruct the logic three weeks later in an actual investor meeting, because the material was never touched again after that single sitting.
Take one thing you're currently trying to learn and split it into three shorter sessions this week, in three different locations or times, instead of one long one.
Test your understanding before you feel ready
Founders often wait to pitch, price, or present until they feel fully prepared — polishing internally before showing anything externally. But attempting the real thing early, and getting parts of it wrong, primes you to absorb the correction far more deeply than more private preparation would.
A founder rehearses a pitch alone for two weeks before ever saying it out loud to another person, then discovers in the actual investor meeting that the core assumption doesn't survive first contact with a skeptical question.
This week, explain your current hardest problem out loud to one person before you feel ready to, and let their first reaction be part of your preparation rather than the final exam.
Let the hard problem sit for a while
Founders often treat stepping away from a stuck problem as a failure of discipline. But letting a genuinely hard problem incubate — walking away from a pricing puzzle or a product decision and returning to it later — is a legitimate part of how understanding forms, not a substitute for the grinding work you've already put in.
Testing early and varying your environment can pull against each other when you're under real deadline pressure: you don't always have time to space things out before a customer call forces an early test. When that happens, let the deadline set the test date, and use whatever time remains before it to vary the setting rather than repeat the same session twice.
Name one thing, honestly
Which piece of your business are you currently "preparing" for instead of testing — and what would happen if you tested it a week earlier than feels comfortable?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
This week, explain your current hardest problem out loud to one person before you feel ready to, and let their first reaction be part of your preparation rather than the final exam.