Roots Not Fruits
Study the conditions that produced a result, not the result itself.
- Difficulty
- Easy
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- —
Beshara warns that we study the fruits of a tree — the company, the exit, the valuation — when the replicable information lives in the roots: the soil, the climate, the decisions, the mechanism. A winemaker will tell you the grapes reveal almost nothing; the playbook is in the soil and the exact spot on the hill. Yet we do the opposite with people in history and business all the time, lifting surface behaviors from a Steve Jobs or a hot startup without understanding the underlying cause. The discipline is to keep asking, for any admired outcome, 'what were the roots?' — the conditions, constraints, and mechanism — rather than mimicking the visible fruit.
Origin
Taught by James Beshara on the Habits & Hustle podcast, using a vineyard/tree metaphor; he ties it to a lesson from Apple via Steve Jobs's long-time chief of staff James Higa.
Core principles
- 01The visible result carries little of the information you need to reproduce it.
- 02Causes live one layer below the outcome — in conditions and decisions.
- 03Imitating surface behavior of the successful is the default trap.
- 04Ask 'what was the soil?' before 'what did they do?'
How to run it
- 1
Name the fruit
State the visible outcome you admire — the exit, the product, the physique, the valuation — as plainly as possible.
- 2
Refuse to copy the fruit
Consciously reject the instinct to replicate the surface behavior or output, the way a winemaker refuses to read the grapes for the playbook.
Watch out Surface imitation feels productive and is the most common failure mode.
- 3
Excavate the roots
Investigate the underlying conditions and decisions: the constraints they faced, the mechanism behind the result, the environment that made it possible.
Pro tip Look for the non-obvious 'soil' — e.g. Apple optimizing decisions around relieving suffering, not features.
- 4
Transplant a cause, not an effect
Apply the root-level lesson to your own situation rather than the copied output.
In the wild
Beshara notes a winemaker would say you cannot look at the grapes and learn much — the real playbook is the soil and the exact climate and position on the hill.
→ A concrete image for why outcome-copying fails.
Via Steve Jobs's chief of staff, Beshara learned Apple's executive team quietly evaluated choices by 'which route would relieve suffering most' — a root he'd never heard despite consuming everything about the company.
→ Shows the causal layer is invisible if you only study the fruit.
Common mistakes
Lifting behaviors from biographies
Copying what a famous founder visibly did ignores the constraints and conditions that made it work for them.
Mistaking correlation for the recipe
The grapes (results) look like the answer but carry almost none of the causal information.
Is it for you?
Best for
Founders and learners who study role models, case studies, and competitors and want durable lessons.
Not ideal for
Situations where the surface output genuinely is the thing to replicate (pure imitation tasks).
From the episode
Episode 559: James Beshara: Top #2 Angel Investor Shares Why He Backs The Founder Not The Business
James Beshara