Residual Results: Build the One-Click Solution
Invest once to build systems and teams that produce results while you sleep.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 83%
McKeown's third stage distinguishes linear results, where one unit of effort yields one reward, from residual results, where a slightly larger upfront investment produces returns again and again. The aspiration is a one-click solution: a system and team so well constructed that a recurring output arrives finished and you only approve it. Building it requires the right people (high integrity, intelligence, and initiative) empowered correctly, plus several iteration cycles until they internalize your voice and standards. The same logic applies to knowledge via Elon Musk's semantic tree: learn the first-principles trunk once and every later fact attaches to a structure you can reuse thousands of times. For those without capital, McKeown redirects leverage toward network and deeply learned principles rather than hiring.
Origin
McKeown describes residual results as the single biggest idea in Effortless, born from realizing he had spent too much of his life making tasks easier to do himself rather than building systems that deliver results while he sleeps.
Core principles
- 01Linear results are one effort for one reward; residual results flow again and again.
- 02A little extra setup effort compounds into repeated returns.
- 03The goal is results that flow to you whether you work or not.
- 04The gap between 2x and 100x is systems, not more personal effort.
- 05Even without money you can build leverage through network and principles.
How to run it
- 1
Separate linear from residual
Identify which outputs are one-effort-one-reward and which could flow repeatedly from a single setup.
- 2
Target a recurring output
Choose something you currently produce by hand each time, like content or reporting.
- 3
Design the system and its owner
Map the process and identify the person or tool that could own it end to end.
Pro tip Give owners direct access to your source material so they can work without you.
- 4
Staff with the right people
Empower high-integrity, high-intelligence, high-initiative people to run it.
Pro tip Initiative matters most here since they must do the thinking in your absence.
- 5
Iterate until they know your voice
Expect several rounds before the team internalizes how you think and what good looks like.
Watch out Do not expect a true one-click result on the first project; it is built over repetitions.
- 6
Reduce yourself to approve-or-not
Get to a point where the finished output arrives and your only job is to approve it.
Pro tip A voice note or short brief can be the single 'click' that triggers the whole system.
In the wild
Chris outsourced almost all his social media production to Joe, who listens to episodes, understands the voice, makes trailers, and repurposes the weekly newsletter into tweet storms. Chris's involvement shrank to a single voice note flagging an upcoming episode; the finished content then appears online with no further input.
→ Scaled content output collapsed to a one-message trigger, freeing the founder's time entirely.
Asked how he learned so fast with no formal background in rocketry, Elon Musk described knowledge as a semantic tree: get the trunk of first principles clear first, then attach branches and leaves. McKeown adds that mastering the principles once lets you apply them hundreds of times, making learning itself a residual asset rather than a linear one.
→ One deep investment in principles yields reusable understanding across countless future situations.
Common mistakes
Optimizing only your own effort
Endlessly making tasks easier to do yourself keeps you at linear 2x output and never unlocks the 10x or 100x of systems.
Expecting one-click on the first try
Skipping the iteration cycles where a team learns your voice guarantees disappointment; residual systems are built over repetitions.
Is it for you?
Best for
Founders, creators, and leaders ready to shift from doing the work to designing the machine.
Not ideal for
One-off tasks with no recurring output where building a system would be wasteful over-engineering.
From the transcript
“that's the difference between linear results that is one effort equals one reward versus residual results which is you put in a little more effort…”
“construct systems hire the right people get the right teams in place empower them... they can produce results while you're sleeping or not”
From the episode
How To Make Life Effortless - Greg McKeown - #314
Greg McKeown