What Entrepreneurs Can Learn from Complex PTSD
Mara had just closed her best sales quarter ever, but the investor meeting left her rattled for days. A board member asked one pointed question about churn, and something in her chest seized up — not annoyance, but a wave of dread closer to being caught doing something wrong as a kid than to running a company. She replayed the exchange for nights, drafting apologies she never sent. Her cofounder noticed she'd gone quiet in meetings where she used to lead. Mara told herself she just needed thicker skin. But what if the reaction belonged to an earlier chapter of her life?
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
The pitch-meeting flashback
A tense investor call or blunt cofounder message can trigger shame or panic that outsizes the event. This is worth noticing as a possible emotional flashback — a present cue landing on old wiring from a time when disapproval felt genuinely dangerous. The moment is small; the feeling is enormous. Recognizing this gap isn't an excuse to avoid tough feedback, but it can stop a founder from irreversible decisions, like firing someone while flooded. Naming it internally as "this is old, not just today's information" often creates enough space to respond rather than react.
Naming a flashback doesn't make legitimate business problems disappear, and real feedback still needs real attention.
Before responding to harsh feedback, wait ten slow breaths and ask whether the intensity matches the actual stakes.
Fight, flight, freeze, or fawn in the founder's seat
Founders often build their drive from an early adaptation, learned where safety had to be earned constantly. A fight-dominant founder may over-control every decision; a flight type over-works to outrun anxiety; a freeze type stalls on hard calls; a fawn type over-promises to keep investors happy at their own expense. None of these is a character defect — each was once a sensible way to stay safe. Seeing the pattern as learned, not innate, opens room to choose differently.
A real market threat sometimes does call for urgent fight-or-flight action, not just reflection.
Name your own default pattern this week, and notice one moment it activates before you act on it.
Quieting the inner investor who never approves
Many founders carry an internal voice sharper than any real critic, treating every setback as proof of failure. This voice often formed early, as a way to preempt outside criticism by delivering it first. In a company it can masquerade as high standards, but it corrodes decisions and burns out the person running the show. A more accurate narrator, one separating outcome from worth, supports steadier leadership, not by lowering standards but by removing the shame that makes thinking harder.
Some self-critique is genuinely useful for course-correcting a business; the goal is accuracy, not blanket self-approval.
After a setback, write down what a fair, supportive mentor would actually say to you.
Becoming your own steady cofounder
Self-reparenting means deliberately offering yourself the steadiness and encouragement that may not have been reliably available growing up. For a founder, this can look like scheduling recovery the way you'd schedule a board meeting, or privately acknowledging effort even when a launch underperforms. It is not a weekend fix but an ongoing practice, built in small repeated moments, that gradually changes how safe it feels to lead from a grounded place.
Founder culture prizes fast action, but recognizing a flashback often asks you to slow down first. A founder in fight-flight overdrive may resist pausing, believing speed is the only survival strategy. Both can be true: swift decisions are sometimes necessary, and some of that urgency is old rather than current. The practical move is triage — reserve immediate action for real emergencies, and treat everyday friction, like a critical email, as a candidate for the slower response.
Name one thing, honestly
- Does my urgency in this decision match today's actual stakes? - Whose voice am I hearing when I judge my own performance? - What would steadier, not harsher, leadership look like this week?
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
After a setback, write down what a fair, supportive mentor would actually say to you.