Horizon-Based Product Prioritization
Sequence product bets by readiness, focus, and user value
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 93%
Horizon-Based Product Prioritization converts a broad vision into a sequence governed by readiness. The team lists desired capabilities, then evaluates each against technical prerequisites, community acceptance, strategic value, and current resource limits. Work is divided into immediate steps, intermediate extensions, and long-term outcomes rather than treated as one simultaneous roadmap. Monetization and user-value initiatives are deliberately balanced so commercial progress does not outrun product quality or community trust. The framework lets teams preserve an ambitious destination—such as native commerce—without allowing it to distract from foundational work like video, messaging, advertising formats, or infrastructure. Its output is a focused next move that still compounds toward the larger mission.
Origin
Emily White explained how Instagram’s small team sequenced monetization, video, messaging, stories, and eventual commerce according to technological and community readiness.
Core principles
- 01A compelling destination does not justify building everything now
- 02Technical and community readiness determine sequencing
- 03Monetization and user value must advance together
- 04Small teams should turn scarcity into focus
- 05Near-term work should remain aligned with the long-term mission
How to run it
- 1
Describe the destination
State the long-term product outcome without assuming it can be built immediately. Connect it to the organization’s mission and user value.
Pro tip Keep the destination stable while allowing the implementation path to change.
Watch out A distant vision is not a current execution plan.
- 2
Map prerequisites
List the technology, infrastructure, user behavior, trust, and operating capabilities each major feature requires. Mark dependencies between them.
Pro tip Include external ecosystem constraints such as payments or mobile-web maturity.
Watch out Seemingly simple features often rest on substantial unseen foundations.
- 3
Test community readiness
Estimate how users will perceive each change and what evidence would demonstrate acceptance. Delay changes that would outrun established behavior.
Pro tip Use smaller adjacent launches to build familiarity before introducing a major shift.
Watch out Technical feasibility does not mean the community is ready.
- 4
Assign horizons
Place initiatives into now, next, and later horizons based on prerequisites and strategic value. Keep each horizon small enough to preserve focus.
Pro tip Promote an initiative only when its key prerequisites have moved with it.
Watch out Do not fill every horizon with unrelated bets.
- 5
Balance the portfolio
Sequence monetization work alongside features that increase user value, engagement, or product capability. Ensure one does not consume the entire roadmap.
Pro tip Explain how commercial and non-commercial initiatives reinforce the same strategic story.
Watch out Excessive monetization can weaken the user base that makes revenue possible.
- 6
Execute the smallest coherent step
Choose the next initiative that creates learning or infrastructure for later horizons. Revisit the roadmap after evidence changes.
Pro tip Prefer steps that preserve future options while delivering current value.
Watch out Avoid building an incomplete fragment that cannot create useful feedback.
In the wild
Instagram could envision purchases inside its visual discovery experience, but payments and mobile infrastructure were not ready. The team began with visual feed advertising while the product separately developed capabilities such as video and messaging, leaving richer transactions for a later horizon.
→ The company advanced monetization without overcommitting to an immature transaction ecosystem.
A small collaboration team wants autonomous project execution but first lacks reliable permissions, audit logs, and structured task data. It places full autonomy in the later horizon, builds permissions and observability now, and introduces assisted task planning next.
→ Each release delivers value while reducing the risk of the eventual autonomous feature.
Common mistakes
Building the destination first
A desirable final experience may depend on technology, user habits, or trust that does not yet exist. Skipping those foundations creates a brittle product.
Doing every important thing at once
Importance does not eliminate capacity constraints. Simultaneous pursuit of every valid opportunity produces loss of focus and slow learning.
Separating revenue from user value
A roadmap that advances monetization without strengthening the underlying experience eventually depletes the source of commercial value.
Is it for you?
Best for
Teams with an ambitious product vision, limited resources, and dependencies that make some desired features premature.
Not ideal for
Single-purpose projects with one fixed deliverable and no meaningful sequencing choices.
From the transcript
“the demise of many a business comes when there's lack of focus and you want to do everything.”
“we knew we could not do everything at once.”
“And so you start to think about horizons and when does it make sense to do something?”
From the episode
Instagram Revisited (with Emily White)
Emily White