What Entrepreneurs Can Learn from What Fresh Hell Is This?
Priya had pitched a hundred rooms without flinching, but that Tuesday she froze mid-sentence in front of three investors, unable to find the word "runway." Her face went hot, and she covered by joking about the coffee. Driving home, she replayed it obsessively, certain her edge was slipping and that admitting it to her cofounder would end the round. She told no one for months, quietly rescheduling anything demanding before noon, when the fog seemed worst. It wasn't until a mentor mentioned her own "invisible year" running a company through perimenopause that Priya realized she wasn't malfunctioning. She was mid-transition, unnamed, doing something hard while pretending nothing was happening at all.
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
Naming what's actually happening in the room
For a founder, the instinct is to solve everything, including your own body, silently and fast. But perimenopause resists that instinct because it isn't a bug to patch; it's changing physiology with its own timeline. Naming specific things plainly, brain fog during long meetings, disrupted sleep before a launch, unpredictable heat in high-stakes rooms, turns vague dread into information you can plan around, the way you'd name a supply delay instead of just feeling anxious.
Founders often name symptoms only in private notes and never aloud, which keeps the shame intact even as the vocabulary improves.
Write down the three symptoms affecting your work most this month, in plain language, then say them aloud to one colleague.
Realizing the range is wider than the pitch deck version of you
Entrepreneurs are trained to present a clean, optimized narrative, so it can feel destabilizing to learn how wide this transition is: some sail through with mild changes, others face intense sleep disruption, mood shifts, or physical symptoms that reshape the workday. Neither extreme is a verdict on your competence. Recognizing that range means you stop benchmarking yourself against an imagined founder who never breaks stride, because that founder is a performance, not a population.
Comparing yourself only to founders' polished public personas reinforces the myth that a well-run company requires a symptom-free body behind it.
Ask one founder you trust what their actual experience has been, not their public one, and notice the gap from their LinkedIn.
Talking about it changes the culture you're building
Founders set norms by example more than by policy. A leader who mentions, without apology, that she rescheduled a call because of a rough night quietly signals that bodies are allowed at work. Silence at the top teaches the opposite: that competence means concealment, which eventually costs you your most experienced people right when their expertise matters most.
Founders sometimes disclose to peers but never to their own team, keeping the double standard alive inside the company they're trying to make humane.
Next time a symptom affects your schedule, say the real reason in one plain sentence, to at least one direct report, instead of a vague excuse.
Building your own operating manual
The most useful thing a founder can take from this book isn't a diagnosis, it's a working vocabulary. Knowing what to call sleep disruption, cognitive change, or shifting energy lets you track patterns the way you'd track any business variable, and lets you ask sharper questions of a doctor instead of describing something vague. Self-knowledge here is a founder skill, not a concession, because you cannot delegate what you refuse to name.
Naming a symptom candidly to your team can feel like it contradicts protecting investor confidence, but the tension resolves once you separate disclosure from oversharing: your team needs enough truth to plan around you, not your medical history.
Name one thing, honestly
What is one symptom you have been managing silently that, if named plainly to one person this week, might lighten your load rather than expose it?
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
Next time a symptom affects your schedule, say the real reason in one plain sentence, to at least one direct report, instead of a vague excuse.