Residual Results System
Build once so valuable results continue with minimal maintenance
- Difficulty
- Expert
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 99%
Residual Results shifts attention from completing one-off tasks to building mechanisms that keep producing. Start with a valuable result that currently requires direct effort every time. Identify why the output depends on you, then encode the repeatable knowledge, relationships, funding flow, or operating process into a system. Reduce the continuing maintenance while protecting the value delivered. McKeown's death test makes the standard vivid: if the creator died today, would the result continue? A strong residual system can keep operating with no input or a small amount of stewardship, allowing the original effort to generate returns far beyond a linear one-time exchange. This creates leverage, makes a business less founder-dependent, and can preserve useful impact long after the original builder has stepped away.
Origin
McKeown highlights Kiva's evolution from a proposed $500 gift into a repeatable microloan platform as an example of building a system that creates systems for others.
Core principles
- 01Linear work stops producing when the effort stops
- 02A system can separate output from continuous personal input
- 03Small maintenance can preserve disproportionate results
- 04Durable systems can compound across generations of use
How to run it
- 1
Find the linear result
Locate a valuable outcome that disappears whenever direct effort stops. Confirm that the result is useful and recurs often enough to justify system work.
Pro tip Start with repeated work that already has reliable demand.
Watch out Do not systematize activity merely because it is repetitive.
- 2
Map personal dependencies
List every decision, relationship, skill, and action that currently requires your presence. Identify which dependencies can be documented, delegated, financed, automated, or turned into an asset.
Pro tip Observe a full real cycle rather than mapping from memory.
Watch out Hidden founder knowledge can make a documented system look more independent than it is.
- 3
Build the repeatable mechanism
Create the process, platform, asset, or organization that reproduces the outcome. Give each dependency an explicit owner or mechanism.
Pro tip Build the smallest system that can run one complete cycle.
Watch out Complexity increases maintenance and can erase the intended leverage.
- 4
Reduce maintenance
Measure the continuing intervention required and remove avoidable touchpoints. Preserve oversight where it protects quality or ethics.
Pro tip Track maintenance time separately from output volume.
Watch out Low maintenance must not mean unaccountable operation.
- 5
Run the death test
Ask whether the result would continue if you permanently disappeared today. Use every point of failure as the next system improvement target.
Pro tip Test with a temporary absence before relying on the system long term.
Watch out A system that pauses during one short absence is still linear in disguise.
In the wild
Jessica Jackley's group considered giving $500 to one entrepreneur, then recognized that a loan could help multiple people in sequence. They built Kiva as a microloan system that enables entrepreneurs to build their own income-producing systems. McKeown reports that the platform went on to distribute $1.3 billion in microloans with 97 percent repaid.
→ A one-time contribution became a reusable funding mechanism with compounding reach.
Rob Dyrdek learned that his businesses were not investible because everything depended on him. He shifted toward businesses that build businesses and documented systems for his life and family, reducing the dependence of results on his continuous presence.
→ The businesses became structured for residual rather than founder-bound results.
Common mistakes
Automating before proving value
A system magnifies whatever it contains, including work nobody needs. Validate the recurring result before investing in leverage.
Hiding the founder inside the system
Documentation alone does not create independence if approvals and knowledge still route through one person. Test whether the mechanism operates during a real absence.
Is it for you?
Best for
It is best for proven recurring work whose value can be captured in a process, asset, platform, or organization.
Not ideal for
It is not ideal for an unproven activity that should be validated before it is systematized.
From the transcript
“a residual result is something that you put the effort in to build a system that works for you even if you don't do anything”
“i use sometimes the death test uh if i died today would this result continue”
From the episode
Greg McKeown: Essentialism & The Pursuit of Less
Greg McKeown