YAGNI and the Three Horizons: How to Build for Today Without Sacrificing Tomorrow

There’s a quiet tension that exists in every product organization. On one side sits the pressure to ship what customers need right now. On the other side sits the responsibility of preparing for what customers might need years from now.

Most teams wobble between the two -swerving from tactical fire drills to grand architectural overhauls - and in that zigzag, they often fall into the most expensive trap in product development:

Building for imagined futures instead of validated realities.

This is where two ideas, one from strategy, one from engineering, come together with surprising harmony:

• The Three Horizons Framework (H1/H2/H3), which describes how organizations balance now, next, and later.
• YAGNI (“You Aren’t Gonna Need It”), a principle that says: build only what delivers value today.

Together, they form a simple rule for modern product teams:

·       Dream in H3 ( 2-5 Years, 10% resources)

·       Shape in H2 ( 1-2 Years, 20% resources)

·       Build in H1 ( 0- 12 Months, 70% resources)
And use YAGNI to keep them from leaking into each other.

Horizon 1: The Now - Where YAGNI Is the Law

H1 is the world of committed customer value: the features that sales promises, the reliability improvements users expect, the adoption blockers you already know you must solve.

·       Here, certainty is high.

·       Here, the clock is always ticking.

·       Here, the mantra is simple: If a user doesn’t need it today, you aren’t gonna build it today.

This isn’t “being shortsighted” - it’s honoring the reality that every hour spent building hypothetical infrastructure is an hour not spent delivering real value.

In H1, YAGNI is your shield against complexity, delay, and the temptation to engineer for a future no one has validated yet.

Horizon 2: The Next -Where You Balance Options with Discipline

H2 lives in the in‑between: you see signals, but not certainties. Maybe a new customer segment is emerging. Maybe the product wants to move upmarket. Maybe there's early traction in a workflow you haven't fully explored.

H2 is where product managers love to imagine futures and where engineers love to start “getting ahead” of those futures.

This is where you need a measured version of YAGNI.
Not “don’t think ahead,” but: Think ahead boldly. Build ahead carefully.

In H2, your job is to test, validate, and keep options open without turning those options into premature features or bloated systems.

·       Maybe you introduce a clean boundary.

·       Maybe you add a seam that can expand later.

·       Maybe you build the feature narrowly but store data in a way that offers flexibility.

H2 is strategy with a seatbelt on.

Horizon 3: The Later -Where Exploration Should Be Wild

H3 is the playground: future bets, business model experiments, disruptive ideas. Here, YAGNI doesn’t constrain vision

Think big. Sketch wildly. Redraw the boundaries of what’s possible.

Just don’t build production-grade systems based on speculative futures.

·       H3 should produce insights, not infrastructure.

·       Your prototypes should be disposable.

·       Your ideas should be expansive, but your code should be minimal.

The mistake many teams make is baking H3 dreams into H1 systems and spending years untangling them.

Where It Breaks Down: The Leaky Horizon Problem

Most product debt doesn’t come from mistakes. It comes from leakage:

• H3 ideation leaks into H1 engineering.
• H2 shaping gets interpreted as H1 requirements.
• Teams build for future customers while current customers struggle.

The result is familiar: slow velocity, heavyweight architecture, and features no one uses.

YAGNI is the boundary that keeps horizons honest.

A Simpler Way to Work: The Strategy Formula

Here’s the operating philosophy that emerges when you blend YAGNI with the Three Horizons:

H3 - Wonder without building.

Define the future you want.
Don’t ship it yet.

H2 - Prepare without committing.

Test the future with experiments.
Protect options without expanding scope.

H1 - Ship without overthinking.

Deliver the smallest thing that solves the real problem.
No extra layers. No architecture flights of fancy.

This is how you move fast today and stay ready for tomorrow.

Why This Works

Because customers don’t reward complexity.
Because strategy is only real when it connects to execution.
Because product teams move fastest when they separate:

• what must be true someday, from
• what must be built today.

YAGNI keeps you grounded. The Three Horizons keep you balanced.
Together, they give you a way to build innovation pipeline, and products that are both immediate and inevitable.