Double Down on the Pull
When something you made gets unexpected traction, drop the plan and lean all-in
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 90%
Orosz's key advantage as a solo operator is the freedom to abandon his plan the moment a piece of work generates disproportionate interest ('pull'). Rather than sticking to the roadmap, he reallocates his time toward whatever the audience is unexpectedly excited about — that's how his side content turned into books and, eventually, the newsletter.
Origin
Gergely Orosz's own operating principle, drawn from watching a long mobile-engineering blog post generate a flood of unsolicited interest during his post-Uber break.
Core principles
- 01Unexpected, intense interest is a signal worth more than your original plan
- 02Being in charge of your own time is what lets you pivot toward pull instantly
- 03Follow demand you didn't manufacture — it's rarer and more reliable than demand you hoped for
- 04A single strong pull can redirect months of work
How to run it
- 1
Ship things and watch for disproportionate reaction
Put work out and pay attention to reactions that far exceed your baseline — a spike in messages, requests, or shares relative to normal.
Pro tip Track your normal engagement baseline so you can recognize a genuine outlier (Orosz normally got 3-4 Twitter messages a day; one draft got 20 in an hour).
- 2
Interpret the pull as a mandate to reallocate
Treat the surge as permission to change what you're working on. Ask what the audience is actually asking for and whether you can give them more of it.
Pro tip Listen to specific suggestions from engaged people — someone told Orosz his long post could be an ebook, which he acted on.
Watch out Requires the autonomy to pivot; this is why control over your own time is the enabling condition.
- 3
Commit real time to the thing being pulled
Block dedicated time to iterate on what's resonating rather than returning to your original plan.
In the wild
Two months into a planned six-month book-writing break, Orosz published a long blog post on mobile engineering at scale. He normally got 3-4 Twitter messages a day; he got 20 in an hour asking to read the draft. Someone suggested turning it into an ebook, so he spent the next two months doing exactly that as a pay-what-you-want (later free, sponsored) book.
→ He never expected more than a few hundred people to care about large-scale mobile apps — thousands did. Doubling down on the pull produced a book and revenue he hadn't planned for.
Common mistakes
Sticking to the plan when the audience signals otherwise
Orosz's plan was to write a specific book, but a different post generated the real pull. Ignoring that signal to stay on the roadmap would have missed where actual demand was.
Dismissing a topic you assume no one cares about
He assumed only 'a few hundred people' would care about large mobile apps; thousands did. Pre-judging demand instead of reading the pull leads you to under-invest in your best opportunities.
Is it for you?
Best for
Solo creators and early-stage founders with the autonomy to reallocate their own time toward emerging traction
Not ideal for
People locked into fixed commitments or roadmaps who can't pivot, or those chasing every minor uptick without a clear baseline
From the transcript
“one of the biggest best things about doing what we do when you're in charge of your time is you can double down on polls”
“I just felt this pull of like this huge interest of people caring about this”
“I usually get like used to get like three or four messages on Twitter per day I got 20 in an hour”
“the point was I was able to double down on on something that I felt like this is super interesting”
From the episode
Leaving big tech to build the #1 technology newsletter
Gergely Orosz (The Pragmatic Engineer)