What Entrepreneurs Can Learn from Feeling Good
Founders live inside a feedback loop where a single bad number can feel like a verdict on the entire venture and on them personally. The trap is treating a fast, unexamined thought — "this means we're failing" — as settled fact, and then spending the rest of the day acting on that thought instead of on what actually happened.
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 4 selected
The core lessons, applied to you
Notice the automatic thought behind a mood dip
For a founder, the shift usually starts with one specific sentence that flashes through the mind right as a metric or message lands — not a vague cloud of worry, but a concrete claim.
A founder opens the dashboard Monday morning, sees signups down for the week, and within seconds is convinced "the market has moved on and this company is done." The rest of the morning gets spent rewriting the pitch deck instead of checking whether the dip has an ordinary explanation.
When a mood shift hits after checking a number, stop and write down the exact sentence that just ran through your head, in quotation marks, before doing anything else.
Recognize common thinking patterns that make a bad moment worse
A single rough data point often gets treated as proof of a permanent, company-wide trend, and a founder's private read of the situation gets treated as though everyone else on the team already shares it.
After one customer cancels, a founder tells themselves "we're going to lose everyone" and starts drafting a defensive all-hands message, without checking whether the cancellation was even related to the product.
Before reacting to a single data point, ask what other explanation would look identical from where you're sitting, and name at least one.
Question the thought and write a more balanced version
The automatic thought is a claim, not a verdict, and it holds up better once it has to survive being written down next to the actual evidence for and against it.
A founder assumes a delayed investor reply means the deal is dead, and spends two days privately grieving it before the investor writes back with an offer — the days of dread were spent on a thought that was never tested.
Write the automatic thought at the top of a page, then list the evidence for it and the evidence against it in two columns before deciding what to believe.
Let the reframed thought change what you do next
Once "this means we're failing" becomes "this is one data point that needs one more week of context," the response changes from a defensive reshuffle to a specific, targeted check — pulling the cohort data, asking a churned customer why they left, or simply waiting for the next data point before acting. A more accurate read of the situation routes energy into the one or two actions that actually address it, instead of into a broad, anxious overcorrection that touches everything at once.
When runway is tight, pausing to write out a thought before reacting can feel like a luxury the business can't afford. But the fastest founders aren't the ones who react quickest — they're the ones who spend sixty seconds checking whether today's alarm is worth this week's pivot before committing the team to it.
Name one thing, honestly
What's one number you reacted to this month that, in hindsight, deserved a slower second look before you changed anything?
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
Write the automatic thought at the top of a page, then list the evidence for it and the evidence against it in two columns before deciding what to believe.