Pull-It-Apart Learning Method
Deconstruct a topic, question its parts, then progress from learning to making
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 94%
The method begins by treating understanding as an act of deconstruction rather than passive consumption. Select a subject, pull apart its claims, mechanisms, assumptions, and terminology, then ask why each part exists and whether it withstands scrutiny. Questions and counterexamples reveal where understanding is shallow. The learner then reconstructs the topic in a clearer form and decides whether they remain a learner or possess enough command to create an explanation or build an application. This progression prevents premature claims of expertise while giving learning a practical destination. Its output is not merely accumulated information but a tested mental model that can support creation, experimentation, or implementation.
Origin
Extracted from Marketing Against The Grain during Kieran's explanation of how he approaches learning about Web3.
Core principles
- 01Understanding grows through deconstruction
- 02Questions expose hidden assumptions
- 03Learning precedes creating and building
- 04Expertise is a progression rather than a fixed identity
How to run it
- 1
Choose the subject
Define the unfamiliar topic or claim you want to understand and the practical reason for learning it.
Pro tip Start with a specific question rather than an entire field.
Watch out A topic that is too broad will produce superficial analysis.
- 2
Pull it apart
Separate the subject into its major claims, mechanisms, actors, incentives, and assumptions.
Pro tip Write each component as a question you could investigate independently.
Watch out Do not accept specialist terminology as an explanation.
- 3
Interrogate the parts
Ask why each component exists, what causes it, and under what conditions it fails.
Pro tip Use concrete examples and opposing cases to test your interpretation.
Watch out Do not confuse familiarity with genuine understanding.
- 4
Reconstruct the model
Explain how the components interact and restate the subject in your own words.
Pro tip Try teaching the mechanism to another person without jargon.
Watch out If you cannot connect the parts, continue learning before drawing conclusions.
- 5
Advance your role
Once the model is coherent, use it to create an explanation, experiment, or working implementation.
Pro tip Build the smallest artifact that tests your understanding.
Watch out Do not claim builder or creator status before producing something concrete.
In the wild
A marketer studying wallet-to-wallet messaging separates the subject into wallet identity, permissions, incentives, privacy, delivery, and user experience. They question each mechanism, compare it with email, and then create a small campaign design that tests whether token-based permissions reduce unwanted messages.
→ The marketer moves from vague familiarity to a testable channel strategy.
Common mistakes
Consuming without questioning
Listening to explanations without decomposing their claims creates recognition but not operational understanding.
Claiming expertise too early
Calling yourself a builder or creator before producing anything obscures the gaps that further learning should address.
Is it for you?
Best for
It is best for curious practitioners learning complex, fast-changing subjects without claiming premature expertise.
Not ideal for
It is not ideal when an urgent task requires immediate execution from an already established procedure.
From the transcript
“And then try to figure out like why things are the way they are, or like pose questions.”
“And so I break people into three buckets, right? You're a learner. When you've actually learned something, you're either creating or building.”
“I don't claim to be an expert in web 3. I claim to be a learner.”
From the episode
Is Web 3 Coming?