Micro-Macro-Metagame Model
Manage execution, strategy, and the changing rules of the market at once
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 97%
The Micro-Macro-Metagame Model borrows three layers from StarCraft to structure company attention. Micro is the immediate craft: product design, engineering, sales motions, distribution, and other detailed mechanics. Macro is the company-level system: business model, market, competitors, differentiation, resource allocation, and the transition from one product to several. Metagame is the changing environment around those choices: business cycles, platform or rule changes, evolving player strategies, and permanent shifts in channels. The framework prevents a leader from mistaking excellent local execution for control of the whole game. Review each layer separately, identify whether an observed change is cyclical or structural, and then make coordinated moves across all three. None of the layers is inherently superior; the difficulty is staying competent in all of them simultaneously.
Origin
A longtime video-game player, Houston uses StarCraft's micro and macro concepts and adds the metagame. He applies the model to Dropbox's viral distribution in 2007, later multi-product and competitive decisions, and the recent shift from conventional technology press toward direct social and podcast distribution.
Core principles
- 01Execution quality, business design, and environmental change are separate layers
- 02Mastering one layer does not compensate for ignoring the others
- 03Markets shift because rules, players, and successful strategies all evolve
- 04Cyclical change and permanent change require different responses
- 05Leaders must understand which game they are actually playing
How to run it
- 1
Inspect the micro
Assess the detailed mechanics that create the product and reach customers: design, technology, sales, onboarding, distribution, and operating speed. Identify where practice or execution quality is the constraint.
Pro tip Use direct product and customer evidence; micro failures are often visible before they appear in strategy reviews.
- 2
Inspect the macro
Step up to the business system. Test the business model, market attractiveness, competitive position, differentiation, resource allocation, and whether the organization fits its number of products.
Pro tip Ask how the answers change as the category moves from high growth toward maturity.
Watch out A polished feature cannot rescue a structurally weak business model.
- 3
Read the metagame
Identify how the rules, players, and winning strategies around the company are changing. Separate recurring booms and busts from durable shifts such as a new distribution channel becoming more effective than the old one.
Pro tip Compare the current change with earlier technology cycles to distinguish a familiar pattern from a permanent break.
- 4
Coordinate the three moves
Choose an action for execution, business design, and environmental adaptation, then test whether the three reinforce rather than contradict one another. Repeat because the ecology of players and strategies keeps moving.
Pro tip Name which layer owns every major initiative so a metagame problem is not answered with micro optimization alone.
Watch out Do not use metagame analysis as an excuse to neglect product craft or execution.
In the wild
Dropbox launched Dash with a conventional technology-press motion and received almost no coverage, while direct social work was far more impactful. Houston connected this with political candidates using podcasts and concluded that the nature of marketing had changed, just as viral videos and epidemiology-inspired loops changed startup distribution in 2007.
→ The comparison exposed a metagame shift in distribution rather than a simple need to execute the old press playbook harder.
An early founder may focus on design, engineering, and a viral loop. As the category matures, the same company must also reason about its business model, competitors, defensibility, multiple products, and organizational structure while watching the wider business cycle and channel shifts.
→ The model assigns each question to the correct layer and prevents one kind of competence from standing in for the others.
Common mistakes
Confusing speed with strategy
More activity at the micro layer does not answer a weak market position or a changed business model.
Calling every cycle a permanent shift
Hiring booms and contractions may recur, while other changes in channels or rules can be durable. The response depends on telling them apart.
Obsessing over the metagame
Houston is explicit that meta is not more important. The company still has to execute well at the micro and macro layers.
Is it for you?
Best for
Founders and executives operating in fast-changing technology categories where execution, company design, and market rules move at different speeds.
Not ideal for
A narrow operational problem whose market, business model, and rules are already stable and well understood.
From the episode
Behind the founder: Drew Houston (Dropbox)