Session-to-Principle Harvest
After each session, extract the principle that outlives the problem you just solved
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 85%
This is how Rubin turned decades of intuitive studio practice into a book. On the day of a session, he would come home and take whatever specifically happened in the studio, especially the moments where nobody knew what to do and the group talked it out until the problem was solved by an idea from anywhere in the room. He would then look at that episode and ask whether there was a principle at work in the solution bigger than this problem, applicable to other problems. Over hundreds of hours of these interviews the harvest accumulated into a toolbox of potential methods, all grounded in things that had actually worked, some of them fairly esoteric. Crucially the abstraction step is deliberate and same-day, not a retrospective reconstruction years later.
Origin
Extracted from The Tim Ferriss Show
Core principles
- 01Solutions are disposable; the principle underneath is the asset
- 02Tacit skill only becomes teachable once it is abstracted from its story
- 03New problems rhyme with old ones rather than repeating them
- 04A toolbox of past moves beats improvising from scratch
- 05Esoteric methods count if they worked
How to run it
- 1
Capture on the day
After a working session, record what specifically happened while it is fresh. Rubin did this coming home from studio days.
Pro tip Voice-record it as an interview with yourself; it is faster than writing and preserves the texture.
Watch out Weeks later you will have the story but not the detail the principle hides in.
- 2
Target the stuck moments
Focus on the episodes where nobody knew what to do and something eventually broke it open, regardless of who supplied the idea.
Watch out Smooth sessions where everything worked teach you much less than the ones that jammed.
- 3
Ask the abstraction question
Look at the solution and ask: is there a principle at work here bigger than this problem, one that would apply to other problems?
Pro tip If the answer is no, say so and move on rather than manufacturing a lesson.
- 4
Strip the story out
Restate the principle so it stands on its own without the names, the project or the room. Rubin deliberately kept his book free of his own projects for exactly this reason.
Pro tip If the principle only makes sense with the anecdote attached, it is not yet abstracted.
- 5
File it in the toolbox
Add it to a growing set of potential methods, each grounded in something that demonstrably worked at least once.
Pro tip Keep the odd and esoteric entries; Rubin notes some of his are pretty esoteric and still earn their place.
- 6
Reach for it when a problem rhymes
When a later situation resembles or rhymes with an earlier one, pull the stored method and try it rather than starting from nothing.
Watch out Rhyming is not identity; treat the retrieved method as a hypothesis, not an answer.
In the wild
Asked how he got to the information in The Creative Act, Rubin says it came through hundreds of hours of interviews. On the day of a studio session he would come home and take whatever specifically happened, particularly moments where no one knew what to do and the group talked until the problem was solved collectively. He would then look at it and ask whether there was a principle at work in the solution bigger than that problem. Years of this produced roughly a thousand pages of talk about creativity, which later became the book.
→ Intuitive practice he could not previously explain became a communicable body of method.
Common mistakes
Collecting stories instead of principles
Without the deliberate abstraction question, the debrief produces anecdotes that entertain but cannot be applied to a different problem.
Debriefing only the wins
The transferable principle usually lives in the moment nobody knew what to do, not in the session that went smoothly from the start.
Leaving the principle welded to the anecdote
A principle stated as a story about a specific artist gets heard as a story about that artist, and the reader never pictures themselves using it.
Is it for you?
Best for
Experienced practitioners whose skill is intuitive and who want to teach it, scale it, or reuse it deliberately.
Not ideal for
Beginners who have not yet solved enough real problems to have anything worth abstracting.
From the transcript
“Is there a principle at work in that solution bigger than this problem, where it's applicable to other problems?”
“So it's like increasing the toolbox of potential methods, all based on ones that have worked in the past for one reason or another.”
From the episode
#649: Rick Rubin, Legendary Producer — Timeless Methods for Unlocking Creativity, Secrets Hidden in Plain Sight, The Future with AI, Helpful Distractions, Working with Strong Personalities, Breaking Out of “The Sameness,” and More