Product development often feels like driving through heavy fog.
You are moving forward, but visibility is limited. You cannot see far enough to plan with confidence, road signs appear too late, and every turn is a decision made with incomplete information. You react to obstacles as they emerge and only later understand whether a choice was right or wrong.
This is how many product teams operate. This is rarely caused by incompetence; more often, it is a structural problem.
But the fog itself is not the main problem. Uncertainty is inherent to product development and cannot be removed. The real problem is the lack of reference points.
When driving in fog, to reach your destination you need two things:
- a map, to understand where you are going and why;
- a compass, to know whether you are moving in the right direction.
Product development works the same way.
Without a map, movement becomes chaotic.
Without a compass, movement feels confident — but may lead in the wrong direction.
Why product teams struggle with decisions
Across companies of different sizes and maturity levels, the same patterns appear again and again:
- Product managers are overloaded.
In many teams, PMs combine several roles at once: discovery, delivery, stakeholder communication, analytics, and sometimes even growth. Under constant pressure to ship, there is little time left for structured thinking, user research, or learning from experiments. - Specialization without alignment.
As teams grow, companies hire designers, analysts, growth specialists, and researchers. However, without a shared decision model, their work becomes fragmented. Teams optimize local goals, but there is no single direction or common understanding of what matters most. - Shipping without learning.
Features are released and experiments are run, but conclusions are weak or missing. Some teams move fast without reflection; others overanalyze and ship very little. In both cases, product development does not meaningfully change user behavior. Even failure, which should generate insight, often leads to no learning at all.
In all these scenarios, teams lack the same thing: a shared way to understand where they are going and how to decide what to do next.
The map: understanding direction and destination
In product development, the map defines why you are moving in a certain direction and what the destination actually is.
This map is built from three core elements:
- Jobs To Be Done (JTBD):
what problem users are trying to solve and why they choose your product for it. - Barriers and friction:
what prevents users from making progress and reaching the outcome they expect. - Value Moments (VMs):
where and when users experience real value, and how complex the path to that moment is, especially during activation and early usage.
These elements shift product discussions away from features and opinions toward user motivation, constraints, and value delivery. Without this map, teams tend to make decisions in isolation, reacting to symptoms instead of addressing root causes.
The compass: knowing whether you move in the right direction
Even with a clear map, teams need feedback to understand whether their actions actually make sense.
This is the role of the North Star Metric (NSM).
The NSM acts as a compass. It does not tell you how to move, but it shows whether your direction aligns with user value and business outcomes. A well-chosen NSM connects product improvement with sustainable growth and monetization.
On its own, a single metric is not enough. That is why leading indicators are essential. They explain what influences the North Star and how different parts of the product contribute to it. Together, they allow teams to detect problems earlier and adjust course before months of effort are lost.
What this changes in practice
The fog does not disappear. Product development will always involve uncertainty.
What changes is how teams navigate it.
The map — JTBD and Value Moments — explains why users come, what they are trying to achieve, and where value is delivered.
The compass — the North Star Metric and leading indicators — shows whether product decisions move the system in the right direction.
With both in place, decisions become explicit, trade-offs are discussed using shared concepts, and experiments are connected to clear hypotheses. Learning accumulates instead of being lost between iterations.
What the Product Decision Framework includes
The Product Decision Framework is a structured system that combines:
- JTBD hypotheses,
- a clearly defined North Star Metric,
- Value Moments and micro-Value Moments,
- a feature decision checklist,
- supporting assumptions and indicators that evolve over time.
It is not a static document, but a working model that is continuously refined as new data and insights appear.
This is the type of system we build and apply in practice at X91 Tech, helping product teams navigate uncertainty with shared direction, explicit assumptions, and continuous learning.
Written by X91 Tech, Growth Studio for Digital Products.
