The belief about how teams move, and the structure that carries it. If you want the product itself, start at how it works.
The philosophy
Hoarded plans drift. Shared conviction moves.
Before the framework and the product, there is a philosophy about how teams navigate together. Navigate by Conviction is the belief that alignment is built through shared understanding — not better documents, not more meetings, not clearer OKRs.
A philosophy by Hans Carlson · Pilgrim Product Work
Product teams using AI have already changed how they work — but not what holds their work together. Strategy lives in documents nobody reads. Decisions disappear between sessions. The thread from a single work item to a long-term goal exists only in the head of whoever has been here long enough to remember.
The drift happens quietly. Not because teams lack talent. Not because they don’t care. But because no one ever built the conditions for it. Strategy lives in documents. Identity lives in the heads of a few. And everyone else navigates by whatever context they managed to pick up along the way.
The result is a team that moves — but not together. Every crossroads becomes a negotiation. Every decision waits for someone with enough context to make the call. And the organization keeps stopping to plan, align, and restart — mistaking the pause for the work.
We believe there is a better way. It starts with four convictions.
Conviction One
Alignment is a movement, not a moment
Most organizations treat alignment as something you achieve — a strategy is shared, and now everyone is aligned. We believe that is a category error. Alignment isn’t a state. It’s a continuous movement. A team that genuinely moves as one doesn’t do so because they read the same document. They do so because they share a deep enough understanding of who they are and what they believe to navigate independently — and pull each other in the same direction when things get uncertain. You cannot communicate your way to alignment. You have to build it, together, over time.
Conviction Two
Conviction must be distributed, not carried
In most teams, conviction lives in one place — the product manager, the CPO, the founder. Everyone else borrows enough context from summaries and slide decks to do their work. This is a structural problem, not a communication problem. When anyone on the team can articulate why we choose X over Y — and use that understanding to navigate an unexpected situation without being asked — that is what distributed conviction looks like. It cannot be handed down. It has to be genuinely shared.
Conviction Three
Movement is the norm. Stopping is the cost.
Most product organizations treat planning as the default and movement as something you earn once planning is done. We believe it is the other way around. Momentum is the default. Stopping requires a reason — and carries a cost. Make assumptions. Stay in motion. Gather learning along the way. The goal is not the perfect process for learning — it is to keep moving while learning. Workshops that pause everything to produce a new plan are not strategy. They are expensive stops that feel like progress.
Conviction Four
Enable the conditions. Don’t deliver the answer.
The instinct of most product leaders is to carry the context, make the call, and communicate the decision. We believe this instinct — however well-intentioned — is the root of the problem. Alignment cannot be handed down. It has to be grown. The role of structure, tools, and leadership is not to produce better artifacts that people should read. It is to create the conditions in which a team builds shared conviction naturally — through their daily work, through real decisions, through the accumulation of understanding over time.
Conviction is not above strategy. It is beneath it — the foundation that makes strategy something a whole team can actually use.
This is what we mean by Navigate by Conviction. Not a philosophy for the few at the top. A way of building teams where the understanding of who we are and where we’re going is genuinely shared — distributed deeply enough that every person can navigate, contribute, and move forward without waiting for permission.
That kind of team doesn’t need to stop at every crossroads. They already know which way to go.
“Know who you are. Make sure everyone around you knows it too. Then watch what alignment actually feels like.” — Hans Carlson
Navigate by Conviction — the framework
Structure → Dialog → Conviction
How conviction is built and distributed across a team.
Component 01
Structure — the throughline, from work to why
Most product teams have structure. What they lack is a throughline — a continuous, navigable connection from a daily work item to a strategic objective to a conviction about who we are.
Without it, fragmentation is the default. A developer lives in delivery context. A designer holds the user’s journey — the map the rest of the work is meant to serve. A product manager carries the connections in their head. And everyone else makes rational decisions to stay within their own context — not because they don’t care, but because going on a treasure hunt across documents, tools, and processes to find the bigger picture is no one’s job description.
The result is a team that works hard in parallel but rarely pulls in the same direction. Not because the strategy is wrong. Because no one can see it from where they sit.
Structure solves this not by adding more documents but by making connections explicit and navigable. When the throughline exists — when anyone can trace from their work upward to the why — conviction becomes distributable. People navigate independently because they genuinely understand, not because they were told.
Ask your AI client why we’re building this — it already knows.
Component 02
Dialog — structure that activates in the room
Structure creates the conditions. Dialog activates them.
Decisions aren’t made in documents — they’re made in rooms, in refinement meetings, in unexpected moments where no one has time to consult a plan. Dialog is the recurring practice of bringing structure into those moments — using shared reference points to make conversations sharper, shorter, and more aligned.
But dialog has natural enemies. Teams default to what is easier:
Easier to focus on solutions than problems
Easier to stay in tactical space than strategic space
Easier to optimise process than make progress
Easier to align on tools and plans than on actual alignment
The result is the -ish syndrome — “we’re agile-ish, outcome-driven-ish, discovery-led-ish” — a series of compromises between different people’s interpretations of how things should work, dressed up as a way of working. Not wrong, but never quite honest about what is actually driving decisions.
Good dialog names these forces and works against them. It replaces scoring models with honest vibe checks. It replaces paralysis with assumptions. It keeps artefacts alive by returning to them at the right moments — not letting them become static documents that drift further from reality with every sprint.
Conviction moments are where dialog becomes visible: someone in the room traces the throughline, names a principle, and the group recalibrates without being asked.
Component 03
Conviction — what structure and dialog build over time
Conviction is not decided. It is not written in a values document or announced in an all-hands. It percolates — through repeated reflection, tested against real decisions, accumulated across many conversations and perspectives over time.
When structure gives the team a shared picture and dialog gives them the practice of activating it, conviction grows as a natural result. Not in the leaders only — distributed across the team. Every person builds enough understanding to navigate, contribute, and move forward without waiting for permission.
This is where storytelling becomes a mechanism, not a metaphor. A team with distributed conviction can tell the story of their product — from a single work item all the way up to a guiding policy — because they have lived it, not just read it. That ability to tell the story is both the proof of conviction and the means of spreading it further.
That is the goal. Not better plans. Not better tools. A team that already knows which way to go — and can bring others with them.
The six domains
The framework organises product work into six overlapping domains. These are not sequential stages — they are always connected. Work in one domain informs and reshapes all others.
The three primary domains (Direction Space, Priority Space, Progress Space) hold the core flow of product work. The three alignment domains (Identity, Landscape, Learning) run alongside all three simultaneously — they are not passive, they are the mechanism that keeps work coherent and conviction distributed.
Direction Space
Where are we going and why?
Direction Space holds the long-term direction. Not a plan — an ambition. Stable enough to hold over time, clear enough to actually steer decisions.
Most teams have a strategy document. Few have a direction that actually steers decisions when the plan runs out.
Direction Space is where you define the overarching principle that channels all strategic energy — specific enough to rule things out, broad enough to accommodate what you cannot yet foresee. A Guiding Policy that never makes you say no to anything attractive isn’t guiding anything.
Themes are the interface between direction and work. They translate long-term ambition into outcome-focused areas that the team can act on. Horizons show sequencing — not as a project plan, but as a story of why this focus, in this order, against these objectives.
When Identity and Direction are aligned, strategic decisions become faster and less political. The team already knows which way to go.
Priority Space
What do we focus on next and in what order?
Where Product primarily operates. Initiatives are the aggregation point — focused ambitions gathered around a goal, not projects with fixed scope and deadlines.
Most prioritisation conversations are really arguments about urgency dressed up as strategy. Priority Space is the antidote.
An Initiative is not a project. It has no fixed scope, no committed deadline, no requirement list. It is a focused ambition with a hypothesis: we believe that doing this will move us toward our objectives. That framing changes the conversation — from “when will this be done?” to “what are we learning and does it still matter?”
Prioritisation is a dialogue, not a formula. Value vs Effort — how well does this align with our objectives and principles, and how clear and complex is the work? — is a running conversation. It changes as the team learns. That is not a sign of poor planning. It is a sign of good judgment.
Progress Space
How do we move forward together?
Where the team builds. Work items aggregate up to the initiative. Progress is the norm — stopping requires a reason and carries a cost.
Progress Space is not delivery. It is movement.
The distinction matters: delivery implies a predetermined output. Movement implies continuous calibration toward a goal. Under an initiative, all types of work can happen — exploration, prototyping, building, shipping — without the team needing to debate whether it is “discovery” or “delivery.” The question is simpler: does this advance the initiative’s goal?
Work Items live at epic level. The team breaks them down further in their own delivery tools. The connection upward — to the initiative, to the theme, to the direction — is what keeps the work from becoming disconnected from the why.
Progress is the norm. Stopping requires a reason and carries a cost. Like a runner on a long course: adjust pace, never halt. Make assumptions. Stay in motion. Gather learning along the way.
Landscape
Who are our users and what is their reality?
The map of the reality the product operates in. Not a process step — it runs horizontally, giving human-centric context to all other domains.
A persona tells you who your user is. A journey tells you what they experience — and where the product succeeds or fails them.
Landscape is the domain that runs horizontally across all the others. A theme connects to journey phases. An initiative maps to where users are in their experience. A principle can be anchored to a specific journey step — so that when the team is working in that area, the relevant constraints are visible without a meeting to establish them.
The journey does not need to be exhaustive. A few phases at the right level of abstraction hold over time and provide a shared language that cuts across the traditional strategy-to-delivery hierarchy. When in doubt: map it to the journey. Where does this work belong in the user’s experience? That question alone creates alignment that a backlog cannot.
Learning
What are we learning and how does it change things?
Learning flows in all directions and reshapes what it touches. A Finding is not storage — it is an active force that connects to a decision and changes something.
Most teams capture learning. Few teams use it.
The gap is connection. A customer interview disconnected from the initiatives it should inform is not learning — it is storage. Learning happens when a Finding connects to a decision and changes something: a hypothesis revised, an initiative reprioritised, a principle updated.
Materia is where everything begins — raw source material before interpretation. A Finding is what emerges when Materia is processed and connected to the elements it affects. A Signal is lighter and faster — a quick observation that may not yet be a Finding but should be visible.
The real test: a Finding should be able to reshape an objective or theme directly. If your learning process never challenges direction, it is not learning — it is confirmation.
Identity
Who are we and what do we believe?
Not above the other domains — alongside all of them, always present. When a strategic decision feels wrong, Identity is usually the signal.
Identity is not a vision statement. It is not a values deck. It is the answer to “why are we doing this?” that goes deeper than any initiative goal — and that holds when the plan runs out.
Most product teams outsource identity to leadership. The CPO carries the conviction, distils it into a strategy, and communicates it downward. The team borrows enough context to do their work. This is a structural problem: borrowed conviction does not navigate. Only owned conviction does.
Principles are Identity’s most operational element. A principle takes five minutes to write and saves weeks of debate. It works because it is testable — you can hold any decision against it and get a clear answer.
A Diagnosis grounds Identity in reality — where we are strong, where we are challenged, what we believe about the market that others do not yet. It is not a one-time exercise. It is the situational awareness that keeps Identity from becoming a document on a wall.
The relationships
Five relationships hold the structure together. None are hierarchical — all are continuous and bidirectional. A sixth — Conviction Moments — is the mechanism that activates all of them.
Progress Space → Priority SpaceWork items aggregate up to the initiative. Not a handover — a continuous calibration.
Priority Space → Direction SpaceInitiatives calibrate against themes. Themes give initiatives their strategic context. Horizons provide sequencing.
Direction Space ↔ IdentityIdentity informs Direction — Guiding Policy and Objectives should be consistent with who we are. When a strategic decision feels wrong, Identity is usually the signal. This relationship is always active, never completed.
Landscape ↔ All domainsLandscape maps horizontally across everything — themes, initiatives, work items can all connect to journey phases.
Learning ↔ All domainsLearning flows in all directions. A Finding can challenge a Direction Space theme. Learning that does not connect to a decision is storage, not learning.
Conviction Moments — the sixth relationshipNot a domain — the mechanism. The natural points where structure and dialog intersect: someone names a principle, traces the throughline, the group recalibrates without being asked. Can arise in any domain, in any direction.
Element inventory
Every building block in the framework, grouped by domain.
The overarching principle: what we do and don’t do
Objective
Concrete ambition that carries out the Guiding Policy
Success Metric
How we measure movement in the right direction
Theme
Outcome-focused area, interface toward Priority Space
Horizon
Strategic focus period with success criteria and sequencing
Assumption
Strategic-level assumption
Priority Space
Initiative
Focused ambition gathered around a goal
Opportunity
Human-centric input: problem, need, or desire
Assumption
Initiative-level assumption about the goal
Progress Space
Work Item
Concrete work at epic level, aggregates up to initiative
Assumption
Work item-level assumption being tested
Initiative Board = view of Priority Space, not an element
Landscape
Journey Phase
Step in the user’s experience with two-way relationships
User Role
Person or actor interacting in one or more steps
Learning
Materia
Raw source material: interviews, notes, transcripts
Finding
Distilled learning linked to affected elements
Signal
Quick observation, can trigger a Conviction Moment
Workspace level
Workspace
The outermost container: a product team’s home in Ambix
Member
Person in a workspace with role and permissions
Audit entry
Documented decision, learning, or Conviction Moment
The name
The patient apparatus. Always ready. Never in the way.
Ambix is named after the alchemist’s distillation vessel — the apparatus that separates the essential from the noise. Product work is transmutation. Raw material — interviews, decisions, assumptions, impulses — enters the process and must become something durable: strategy that holds, initiatives that connect to why they exist, teams that know where they’re going.
That is what Ambix distils. Not as a document nobody reads. As context the AI you already work in can actually reach.
Where to go from here
The philosophy is the why. The product carries it.
Ambix turns this framework into your team’s product memory — the convictions, decisions, and findings behind your product, structured so the whole team and the AI tools they already work in can navigate by them.
