Deep-to-Wide Problem Study
Move between system detail and the big picture to find leverage
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 95%
Ek attributes much of his problem solving to spending hundreds or thousands of hours with a subject, then moving repeatedly between granular detail and the wider system. For music, that meant learning copyright regimes, rights categories, identifiers, industry actors, and consumer needs. For healthcare, he describes studying incentives, public and private systems, costs, disease groups, and longevity over years. The mechanism is neither endless research nor instant first-principles intuition. Map the system, learn enough detail to see constraints, zoom out to locate leverage, order the problems by dependency, and test the first decisive uncertainty. Ek says people often fail by remaining too high-level or becoming trapped in details.
Origin
Ek says he spent roughly 500 hours studying music before committing and later accumulated extensive knowledge of copyright; he describes a similarly long study of healthcare.
Core principles
- 01Sustained attention reveals options invisible at a distance
- 02System incentives matter alongside technical details
- 03Useful insight requires movement between detail and overview
- 04Problem order can matter as much as individual solutions
How to run it
- 1
Map the system
Identify the actors, incentives, rules, costs, and user needs shaping the problem. Capture how each part affects the others.
Pro tip Include institutions and constraints that sit outside the product itself.
- 2
Learn the machinery
Study the technical, commercial, and regulatory details that determine what can work. Continue until you can explain them plainly.
Pro tip Keep a notebook of unanswered questions and possible connections.
Watch out Do not mistake memorizing terminology for understanding the mechanism.
- 3
Zoom out
Return to the full system and ask which constraint now appears decisive. Look for a narrow point where change could alter the wider outcome.
Watch out Staying inside one specialty can conceal the actual bottleneck.
- 4
Order the problems
Sequence uncertainties by dependency and leverage. Solve the issue that determines whether later work is worth doing.
Pro tip Distinguish a product problem from an adoption or permission problem.
- 5
Demonstrate the answer
Build or gather evidence that tests the first critical uncertainty. Use the result to update the system map and next question.
Pro tip A convincing prototype can turn a broad debate into a specific remaining obstacle.
In the wild
After the small Spotify team built a product that felt as if the world's music were on a hard drive, Ek concluded that consumer appeal was no longer the primary uncertainty. The decisive remaining question was whether the music industry would permit the service, which required another 18 months of work.
→ The team focused on licensing as the bottleneck rather than continuing to treat the whole venture as one undifferentiated problem.
Common mistakes
Staying above the details
A broad view without operational knowledge misses the constraints and nuances that determine what is possible.
Getting buried in detail
Deep research loses strategic value when it never returns to the system-level question or problem order.
Is it for you?
Best for
It is best for consequential problems involving multiple actors, incentives, regulations, or technologies.
Not ideal for
It is not ideal for simple, reversible decisions where prolonged study would only delay action.
From the transcript
“I probably spent 500 hours learning about this problem”
“how do you dive deep enough where you see it and figure out which problem to solve in what order”
From the episode
Spotify Founder: “Spotify Was A Stupid Idea!” How A 23 Year Old Shy, Underdog, Introvert, Built A $31 Billion Business! - Daniel Ek