01 · Origin
Why I started Brain Leak
I've always been fascinated by one question: how does the brain actually work under the conditions most of us live in — long hours, constant decisions, chronic stress, not enough sleep?
Not the brain in a lab. The brain at work.
I'm not a neuroscientist. I'm someone who reads the science obsessively and wants to understand what it means for how we function every day. Brain Leak is the result of that obsession — and a way to share it with people who face the same pressures.
Brain Leak exists because the gap between what we know about the brain and what gets repeated about the brain is widening — and that gap costs people real time and real attention.
02 · The question
The question that drives every issue
How do you stay sharp, healthy, and effective when work never really stops? Most advice on this is either too generic or not grounded in evidence. I wanted something better — rigorous, honest, and actually useful.
So I started reading peer-reviewed research. And translating it into plain language. And publishing it twice a week.
03 · Editorial rules
What we don't do
- 01
No motivational quotes.
If a sentence would fit on an Instagram tile, it doesn't belong in a neuroscience newsletter.
- 02
No single-study claims.
Every mechanism we describe is replicated. Where the literature disagrees, we say so out loud.
- 03
No hacks.
"One weird trick" is the opposite of how the brain works. We talk about mechanisms, then applications.
- 04
No causal language without causal evidence.
We never say "proves" or "causes" when the study only "suggests" or "indicates." Correlation stays correlation.
- 05
No paywalls.
The newsletter is free, forever. If we monetize, it will never be by gating issues.
04 · Audience
Who Brain Leak is for
Knowledge workers who do thinking for a living — and who suspect the way their week is shaped is fighting their brain instead of working with it.
→ Managers
Trying to build teams that aren't running on sleep debt and adrenaline.
→ Founders
Who want decisions backed by mechanism, not by a podcast quote.
→ Engineers
Curious about why context-switching hurts and what to do about it.
→ Freelancers
Who need to protect their cognitive resources across clients and deadlines.