Focused Hours Over Long Hours
Overwork lets you skip the hard work of deciding what matters — force the constraint that makes you decide
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 90%
Fournier's core claim is diagnostic, not motivational: long hours are a way of avoiding the genuinely hard question of what's important. Her practice is to impose an artificial hard stop, run a regular audit of what you actually did against what mattered, and delegate aggressively — which she frames as the only real path to scale, despite costing more time up front.
Origin
Camille Fournier, describing the philosophy she has run her own career on and encouraged in teams she has led — she is explicitly not a believer in working too hard, while being known for teams that work hard and still have work-life balance. The framing borrows the logic of Elon Musk's 'if you don't add back 10% of what you cut, you didn't cut enough' cutting principle, and of a prior Lenny's Podcast guest's line that if you've never regretted firing someone you don't know where the line is.
Core principles
- 01Overwork sidesteps the hard work of figuring out what's important in the first place.
- 02Unlike firing, you can't learn the importance line once — you have to regularly re-test where it is.
- 03If you're not routinely auditing your time and cutting the things that don't matter, you're wasting a lot of time on things that don't matter.
- 04You're allowed to love working a lot — but you could be getting far more valuable work done in the same hours.
- 05You will never scale without delegating, and you'll be overwhelmed because your team can't do anything you never taught them.
- 06Thinking about work after hours is different from doing it. The boundary still counts.
- 07This is not a one-time exercise. It's an active process of constant reflection.
How to run it
- 1
Impose an artificial hard stop
Pick a concrete constraint and hold it: stop at 4pm every Friday, log off at 6pm every day this week, no work this weekend. The constraint is the mechanism — it forces prioritisation you'd otherwise avoid.
Pro tip Fournier says this is one of the best ways to do it precisely because it's scary and people don't like doing it.
Watch out Your brain will keep churning on work in the gap. That's fine — thinking about it is not the same as doing it.
- 2
Run the retrospective the constraint creates
At the hard stop, ask what you actually got done. That question, asked against a shortened week, exposes which activities were real value and which were guilt-management.
Pro tip Name the guilt explicitly: am I really producing the best value, or am I just assuaging an internal need to be seen as a 60-hour, sleeping-in-the-office hard worker?
- 3
Audit your time regularly and knock things off the list
Periodically go through your commitments and actively cut what doesn't matter. What's important changes over time, so the audit has to recur — you can't set the line once.
Pro tip Borrowing the cutting logic: if you never regret something you cut, you probably aren't cutting enough. Testing the limits is the point.
Watch out This will feel scary and dredges up the forgot-to-finish-the-assignment anxiety, especially for the overachievers who end up in these jobs. Do it anyway.
- 4
Delegate even though it costs more up front
Hand work to your team and accept that teaching them usually takes more time initially than doing it yourself. That investment is what frees you to scale — and occasionally they turn out to be better at it than you.
Pro tip Delegation also empowers: people get a visible chance to prove they can take on more, and they enjoy it.
Watch out Skipping this creates the self-fulfilling trap — you're overwhelmed because your team can't do anything, and they can't do anything because you never delegated.
- 5
Build a focus ritual
Construct a repeatable environment for deep work. Fournier uses caffeine rituals (tea in the morning, caffeinated water, a Diet Coke at lunch), a quiet place, and instrumental music with no lyrics and an unpredictable structure.
Pro tip Her specific picks: Fourtet, and the Andre 3000 flute album — not-quite-predictable, wordless music. Any lyrics and her brain can't ignore the words.
In the wild
As a hands-on programmer she was extremely good at being focused at work — she didn't want to work weekends or stay until 9pm, so she coded heavily for most of the day, did fewer coffees, skipped the daily lunchtime chats. She notes this was pre-heavy-social-media and she isn't sure she could do it as easily now.
→ She learned to get a lot done in a short period of time — and credits that focus discipline as one of the reasons she reached technical mastery at all.
Lenny brings up Elon Musk's optimisation process, one step of which is to cut aggressively — if you don't have to add back roughly 10% of what you cut, you didn't cut enough. Fournier agrees on testing the limits while being candid that doing it is genuinely scary.
→ The importance line is only discoverable by overshooting it, so the audit needs to actually remove things, not just rank them.
Common mistakes
Using hours as a substitute for prioritisation
Long hours let you avoid ever deciding what's important. The work gets done, but you never find out which parts of it mattered.
Never delegating
Because delegating costs more time initially, managers skip it — and then drown, with a team that hasn't been taught to do anything. There is no version of scaling that skips this step.
Treating the audit as a one-off
Unlike firing, where one regretted decision teaches you the line quickly, the importance line moves. You have to re-test it regularly or you drift straight back into busywork.
Is it for you?
Best for
Managers and senior ICs who feel busy but unproductive, and leaders trying to build a hard-working team culture without burnout.
Not ideal for
Genuine crunch periods with a real external deadline, and very early-stage founders where the fundamental constraint is that nothing is delegable yet.
From the transcript
“but older work kind of lets you just sidestep doing the hard work of figuring out what's important in the first place”
“not regularly doing an audit of your time and trying to knock things off that list that don't matter you're probably wasting a lot of…”
“I'm going to log off I'm going to log off every day this week at 6 PM”
“I also think like people don't delegate enough”
From the episode
The things engineers are desperate for PMs to understand
Camille Fournier (author of “The Manager’s Path,” ex-CTO at