What Entrepreneurs Can Learn from Uniquely Human
Mara built her startup's culture around one rule: ship fast, explain later. Her lead developer, Theo, worked differently. He needed to talk through a problem before touching a keyboard, flapped his hands when excited, and went quiet in loud all-hands meetings. An investor asked, after a demo-day rehearsal, whether Theo was really founder material. Mara almost apologized for him. Instead she paused. Theo's quietness wasn't disengagement; it was the same focus that had solved their hardest architecture problem at 2 a.m., meeting a different kind of pressure. She changed how she prepped him for the room, not who he was, and watched his contributions shift. It cost her almost nothing, and made her wonder what else she had been reading wrong.
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
Reading signals as information, not a confidence score
In a startup, a raised voice, sudden silence, or a need to leave a loud room often gets filed under team fit rather than treated as information. Seeing behavior as an attempt to manage a real internal state translates directly: a teammate who goes quiet before a big meeting may be regulating, not withdrawing, and a founder who reads that correctly can adjust the meeting instead of the person.
A founder is not a clinician, and treating every unusual behavior as meaningful can slide into over-reading ordinary stress.
Before your next high-stakes meeting, ask each core teammate privately what would help them do their best work in it.
Trust as the actual retention strategy
Many founders default to correcting behavior that looks unprofessional, asking someone to hold eye contact or soften a delivery, because compliance feels like the fastest fix under deadline pressure. Trust-based relationships outperforming compliance-based ones maps onto retention numbers any founder tracks: people who feel understood tend to stay and take more risks for the company.
Some behaviors genuinely need to change for the team to function, and trust-first can become an excuse to avoid a hard conversation.
Replace one scripted correction with one open question about what makes a situation hardest and what would help.
Designing the workspace, not just the headcount
Open-plan offices, back-to-back calls, and unscheduled pivot meetings are startup fixtures, and also close to a worst-case sensory environment for many people, autistic or not. Adjusting environments rather than expecting tolerance is a cheap, high-leverage move: quiet rooms, camera-optional calls, and predictable agendas remove friction for more of the team than you would guess.
A ten-person startup often cannot offer the space or scheduling flexibility a larger company can afford.
Add one standing option to the team calendar, such as a camera-off day, and notice who uses it.
Hiring for what someone builds when no one's watching
The instinct in early hiring is to smooth out anything unusual and hire for polish. Treating a person's deep interests and real strengths as the foundation to build from, rather than a quirk to manage, is close to what good early hiring already does best: some of the most valuable early engineers got there through narrow, obsessive focus that looked odd before it looked like an advantage.
The tension sits between building trust and moving at startup speed: trust takes time you often don't have before a launch, and the instinct under pressure is to default to fast correction because it feels quicker than a conversation. Holding both means treating trust as infrastructure invested in during calm weeks, so it is already there when the deadline arrives, rather than built for the first time mid-crisis.
Name one thing, honestly
- Where have you mistaken a different way of processing pressure for a lack of confidence? - What would change if you treated one teammate's unusual working style as a strength to build around? - Which of your current meeting or office norms exist mostly out of habit?
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
Add one standing option to the team calendar, such as a camera-off day, and notice who uses it.