Manufactured Deadlines
Impose external constraints so solo creative work actually ships
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 95%
When you work for yourself, self-discipline collapses because nothing forces output. Orosz's fix is to deliberately manufacture external obligations — a public weekly promise, paying subscribers, a publisher contract — so that the deadline, not your willpower, produces the work. He argues these constraints are what make solo creators finish anything.
Origin
Gergely Orosz's own hard-won lesson after leaving Uber; he credits the serialization tactic to Alexandre Dumas, who wrote The Three Musketeers as a paid magazine serial because he was low on money and needed to keep readers buying the next issue.
Core principles
- 01A deadline you can't quietly move is worth more than motivation
- 02Being a 'star employee' does not transfer to self-employment — structure does
- 03Recurring public commitments (a weekly newsletter) beat open-ended projects that lose momentum midway
- 04Constraints can be engineered on purpose, not just endured
How to run it
- 1
Name a fixed, public deliverable
Commit out loud to a specific cadence and audience — e.g. 'I will publish something in-depth every week starting next week' — so backing out has a social cost.
Pro tip Announce it to people whose opinion you care about (audience, family) so the commitment is witnessed.
- 2
Attach a real external party to the deadline
Bring in someone who holds you accountable: paying subscribers, a publisher contract, an editor, or a co-writer. Orosz notes a book advance in software is tiny (~$5k), so the point of a publisher is the accountability, not the money.
Watch out If the only person you answer to is yourself, expect the discipline to 'go out the window' — Orosz saw exactly this happen to him.
- 3
Let the recurring output assemble the bigger project
Piggyback a large goal onto the cadence. Orosz quietly wrote newsletter posts mapped to chapters of his book so the book would 'just kind of come together' instead of stalling as one giant project.
Pro tip Keep a chapter-to-post checklist so each deadline advances the long-term work.
In the wild
Orosz announced he would write something in-depth about software engineering every single week and told his wife he'd give it his all for six months — treating it like a startup obligation rather than an optional creative project.
→ He kept the cadence, later added a second weekly post, and produced 'four or five books worth of content' in a single year.
Alexandre Dumas, low on money, agreed to write for a magazine that needed content readers would buy — so he wrote each installment to be interesting and cut it off so people came back for the next issue, and a full, long novel emerged.
→ A now-classic book was produced purely because a paying deadline forced consistent output.
Common mistakes
Relying on willpower instead of structure
Orosz was a diligent employee for ~15 years, yet working for himself he caught himself wasting days. Assuming self-motivation will carry a solo project is the core failure; only imposed constraints fixed it.
Starting a huge open-ended project with no cadence
He feared his book would 'take months and I'll lose motivation midway.' Big projects with no recurring deadline stall; breaking them into a forced weekly rhythm is what keeps them alive.
Is it for you?
Best for
Solo creators, newsletter writers, and would-be authors who have time and ideas but keep failing to ship consistently
Not ideal for
People in structured jobs who already have externally imposed deadlines and instead need more autonomy
From the transcript
“if you put in ways that you have to do do certain things no put in constraints for the things that you need to do…”
“if you if you want to write a book the easiest way is go to a publisher and sign a contract not because of the…”
“but I fixed it by if I telling people you're gonna get this every week and now I have to do it I just have…”
“he wrote the book for magazine he was apparently just low on money”
From the episode
Leaving big tech to build the #1 technology newsletter
Gergely Orosz (The Pragmatic Engineer)