Curiosity–Iteration Domain Expertise Matrix
Build rare expertise through curiosity and repeated learning cycles
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 98%
The matrix separates domain expertise from management capability and iteration from accumulated experience. Domain expertise belongs with iteration because a person can repeatedly test, inspect results, ask why something happened, and improve without holding a particular corporate role. Management belongs with experience because managing people, relationships, and programs requires real organizational exposure. The practical decision rule is to identify which capability you need and then choose the matching development environment. For domain mastery, create your own cycles and learn from every result. For management mastery, seek situations where you can earn responsibility and build genuine organizational repetitions. Curiosity powers the domain-expertise quadrant by turning every outcome into another question and experiment.
Origin
Extracted from Marketing Against The Grain, where the hosts use a two-by-two to distinguish curiosity-driven domain mastery from experience-driven management development.
Core principles
- 01Curiosity is a prerequisite for deep domain expertise.
- 02Expertise grows through repeated cycles, not tenure alone.
- 03Individuals can develop domain expertise without company permission.
- 04Management expertise requires access to people, programs, and relationships.
- 05Iteration converts experiments into practical knowledge.
How to run it
- 1
Name the capability
Decide whether the desired outcome is domain expertise or the ability to manage people, relationships, or programs.
Pro tip Define the capability narrowly enough that progress can be observed.
Watch out Do not treat a prestigious employer or long tenure as proof of domain expertise.
- 2
Choose the matching path
Use independent experimentation for domain expertise and real organizational responsibility for management expertise.
Pro tip A side project can provide domain repetitions when your job cannot.
Watch out Management simulations cannot fully replace experience with real stakeholders.
- 3
Run an iteration
Try a concrete approach, measure what happened, and compare the result with your expectation.
Pro tip Change one important variable at a time when possible.
Watch out Activity without feedback does not reliably produce expertise.
- 4
Interrogate the result
Ask why the approach worked, why it failed, and which underlying lever mattered.
Pro tip Write the answer before beginning the next iteration.
Watch out Avoid explaining every failure away as bad luck.
- 5
Compound the lesson
Use the newly acquired knowledge to design a more informed repetition and continue the cycle.
Pro tip Maintain a simple experiment-and-learning log.
Watch out Stopping after one success leaves the mechanism untested.
In the wild
A marketer publishes and optimizes a small collection of niche websites. Each ranking change becomes evidence about content, links, and search intent, allowing the marketer to develop expertise without waiting for an employer to assign an SEO role.
→ Repeated independent cycles produce demonstrable domain expertise and a portfolio of results.
A strong specialist who wants to lead seeks responsibility for a cross-functional program, then a small team. The specialist learns stakeholder alignment, delegation, and feedback through real organizational consequences rather than studying those skills only in theory.
→ Practical experience develops the management side of the matrix.
Common mistakes
Confusing tenure with expertise
Time in a role does not guarantee that someone investigated results or improved the underlying craft.
Managing without practitioners
A team rich in program management but poor in domain knowledge may efficiently execute weak ideas.
Repeating without learning
Iterations only compound when each result changes the next attempt.
Is it for you?
Best for
It is best for professionals, founders, and hiring managers deciding how skills should be developed or evaluated.
Not ideal for
It is not ideal for people seeking mastery without sustained experimentation or access to feedback.
From the transcript
“And then on the other axis, we have like iterations. And so for me, domain expertise is really just cycles.”
“The only prerequisite is you have to be curious about a problem and iterate on solving that problem in a bunch of different ways over…”
“But on the domain expertise side of things, really there's no barriers to entry there. So it's just based upon your own will to make…”
From the episode
Curiosity is a Billion Dollar Skill