Part 3 of 4: Implementation Frameworks, Pitfalls to Avoid, and Real-World Success
From Concept to Operating Discipline
Understanding the three-horizon framework is one thing. Actually implementing it in a fast-moving scale-up is something else entirely. In Parts 1 and 2, we explored why roadmap-only thinking fails and how the three-horizon framework creates sustainable competitive advantage. Now comes the hard part: making it operational in your organization.
The challenge isn’t conceptual understanding, most executives immediately grasp why portfolio thinking matters. The challenge is organizational: how do you maintain strategic discipline when everything feels urgent, how do you defend Horizon 2 and 3 investments when customers are demanding Horizon 1 features, and how do you structure teams and metrics to support different horizons simultaneously. After implementing this framework across dozens of scale-ups, we’ve developed a battle-tested approach that works even in high-pressure, resource-constrained environments.
Step 1: Portfolio Audit and Reality Check
Before you can rebalance your portfolio, you need to understand your current state. Most leadership teams significantly overestimate their Horizon 2 and 3 investments. They remember the strategic initiatives they discussed in quarterly planning but forget how many got deprioritized for urgent customer needs.
Conduct a ruthless audit by mapping every active initiative, every engineering team’s current focus, every product manager’s roadmap commitment, to one of the three horizons. Horizon 1 improves the core product for the existing customer base and use cases. Horizon 2 extends capabilities to new segments, use cases, or platform advantages. Horizon 3 explores fundamentally new technologies, business models, or market opportunities. Then calculate actual capacity allocation by engineering time, not by number of initiatives. A Horizon 3 exploration that gets five percent of one engineer’s time doesn’t represent ten percent of your portfolio.
What most teams discover is that they’re running 85 to 90 percent Horizon 1, 10 to 15 percent Horizon 2, and zero to 5 percent Horizon 3, regardless of what their quarterly plans say. Watch for hidden Horizon 1 work: strategic initiatives that are actually core product improvements disguised with ambitious language. If it’s serving existing customers in existing use cases, it’s Horizon 1 no matter how innovative it sounds.
Step 2: Define Strategic Target Allocation
Now that you know where you are, decide where you need to be. Your target allocation should be based on your current market position, your funding runway and revenue growth, competitive dynamics, and your technical debt burden. Early in your category, you want heavy Horizon 1 to establish dominance. In a mature market with entrenched competitors, you want more Horizon 2 and 3 to differentiate. Limited runway demands Horizon 1 focus on revenue and retention, while a strong position enables more strategic investment.
Example allocations by stage: pre-Series A companies proving product-market fit should run roughly 75 to 80 percent Horizon 1, 15 to 20 percent Horizon 2, and 5 percent Horizon 3. Series A and B companies establishing market position should run roughly 60 to 70 percent Horizon 1, 20 to 30 percent Horizon 2, and 10 percent Horizon 3. Series C and later companies pursuing market leadership should run roughly 50 to 60 percent Horizon 1, 25 to 35 percent Horizon 2, and 10 to 15 percent Horizon 3. The critical principle is that your target allocation should be explicit, documented, and jointly owned by your CPO and CTO. It’s not a suggestion, it’s a strategic commitment.
Step 3: Establish Governance and Decision Rights
Strategic allocation means nothing without governance to protect it. The operational challenge is that Horizon 1 work generates constant pressure to reallocate resources. A major customer threatens to churn. A competitive deal demands a specific feature. A technical incident requires immediate attention. Without governance frameworks, these pressures will consume your Horizon 2 and 3 capacity every single time.
Create decision frameworks for promotion criteria, meaning when a Horizon 3 experiment graduates to Horizon 2 investment, which should require validated customer demand, technical feasibility, strategic alignment, and resource commitment. Create frameworks for sunset decisions, meaning when you kill initiatives that aren’t delivering, with quarterly reviews and explicit continuation criteria, so Horizon 3 experiments that haven’t generated learning in two to three months get killed or pivoted. Create frameworks for resource reallocation, meaning under what circumstances you can pull resources from Horizon 2 or 3 to address Horizon 1 needs, limited to customer-affecting incidents or strategic opportunities that would be materially accretive to business value, requiring joint CPO-CTO approval and a documented payback plan. And establish a review cadence: monthly portfolio reviews for tactical adjustments, quarterly strategic reviews for major rebalancing, and annual planning for fundamental strategy shifts.
Step 4: Align Organization and Metrics
Different horizons require different team structures and success metrics. The structural challenge is that if you measure all teams by the same metrics, such as features shipped, customer adoption, or revenue impact, you’ll kill Horizon 2 and 3 work.
Dedicated Horizon 1 teams should optimize for delivery velocity, operational excellence, and customer satisfaction, measured by feature adoption, system reliability, and customer retention. Cross-functional Horizon 2 squads should balance customer development with capability building, measured by market validation, technical feasibility, and strategic option creation. Small Horizon 3 exploration teams should emphasize learning speed over shipping speed, measured by hypotheses tested, insights generated, and graduation readiness. Teams should have primary horizon ownership while maintaining awareness of portfolio objectives.
The Four Deadliest Pitfalls
The first pitfall is Horizon 1 gravity, where urgent customer needs and revenue pressure consistently pull resources away from Horizon 2 and 3 work, and “just this once” becomes every quarter. The solution is to ring-fence capacity for strategic horizons and treat Horizon 2 and 3 allocations as non-negotiable infrastructure investment, with executive accountability and board-level reporting on portfolio allocation.
The second pitfall is Horizon 3 delusion, where teams label incremental Horizon 1 work as strategic innovation to make it sound more important or to get access to Horizon 3 resources. The solution is to define ruthlessly clear criteria: Horizon 3 should feel genuinely uncertain and exploratory. Ask whether the initiative would make sense if your current business model disappeared. If not, it’s not Horizon 3.
The third pitfall is disconnected horizons, where Horizon 2 and 3 initiatives don’t leverage Horizon 1 customer relationships and market position, becoming science projects disconnected from business value. The solution is to require all strategic initiatives to articulate how they build on core advantages, since the best Horizon 2 and 3 work multiplies the value of Horizon 1 rather than diversifying away from it.
The fourth pitfall is missing the transition, where promising Horizon 2 or 3 initiatives prove their value but die because there’s no clear path to scaling them or integrating them into Horizon 1. The solution is to establish explicit graduation criteria and resource commitments, including a graduation budget of reserved capacity for scaling validated initiatives into Horizon 1.
Real-World Case Study: A Series B Transformation
Consider a B2B SaaS platform with a mid-market focus, fifteen million dollars in ARR, eighty employees, strong product-market fit but increasing competitive pressure, and preparing for a Series C raise. Their initial portfolio audit found 92 percent Horizon 1, 8 percent Horizon 2, and 0 percent Horizon 3, despite Horizon 3 work being discussed but never funded. Investors wanted to see defensible competitive advantages, enterprise prospects demanded platform capabilities, new competitors were launching with AI-powered features, and the team felt stuck on the feature treadmill.
Over a six-month transformation, months one and two focused on audit and strategy, including a comprehensive portfolio audit, a joint CPO-CTO strategic planning workshop, and board alignment on three-horizon strategy, landing on a target allocation of 65 percent Horizon 1 for enterprise features and technical debt, 25 percent Horizon 2 for platform API and vertical modules, and 10 percent Horizon 3 for AI-powered automation and embedded product experiences. Months three and four focused on organization and governance, restructuring teams around horizon ownership, establishing monthly portfolio reviews, creating different success metrics by horizon, and protecting Horizon 2 and 3 capacity in sprint planning. Months five and six focused on execution and validation, shipping key enterprise features and improving reliability in Horizon 1, launching a platform beta with twelve early adopters in Horizon 2, and validating an AI automation concept with design partners in Horizon 3.
Eighteen months later, the company raised its Series C at three times the initial projected valuation, with investors specifically citing platform strategy and AI roadmap as differentiators. Customer retention improved fifteen percent despite maintaining feature velocity. Platform revenue reached twelve percent of total ARR within a year. Two Horizon 3 initiatives graduated to Horizon 2 with dedicated resources. Team satisfaction increased as engineers valued strategic work alongside execution. The transformation required weekly portfolio reviews, monthly board updates jointly delivered by the CPO and CTO, and explicit agreement on trade-offs. The key success factor was treating portfolio allocation as a strategic commitment, not a planning suggestion.
Making It Stick
Three-horizon thinking isn’t a one-time planning exercise, it’s an operational discipline that requires consistent reinforcement. Monthly rituals should include a portfolio allocation review of actual versus target, Horizon 2 and 3 progress updates, and resource reallocation requests and decisions. Quarterly disciplines should include a strategic portfolio assessment, graduation and sunset decisions, market validation reviews, and board communication on portfolio strategy. Annual planning should include a fundamental strategy refresh, target allocation adjustments, and multi-year horizon roadmaps.
In Part 4, we’ll explore how to measure portfolio health, communicate strategy to stakeholders, and build the competitive advantages that compound over time.
Ready to transform your product planning? Our Board Alignment and Investment Prep service helps leadership teams articulate three-horizon strategy to investors and establish the governance frameworks that ensure execution. We also offer Horizon Planning workshops that take you through the complete implementation process.