Product Owner
For the short version, click here.
We believe that product ownership is fundamentally about focus.
About saying no.
About the relentless pursuit of what truly matters.
On Value
Value isn't what we build.
It's what changes.
We measure outcomes. Not outputs. Not activity. Not effort.
What changed in the world because of our work?
That's the only question that matters.
We ruthlessly eliminate scope. We say no to almost everything. This isn't cruelty. It's clarity.
When you say yes to everything, you commit to nothing.
We choose what to build. But more importantly, we choose what not to build.
The work is in the choosing.
On Prioritization
Not everything can be a priority.
When everything is urgent, nothing is urgent.
We sequence work based on value delivered. Impact achieved. Problems solved.
Not based on who asked loudest. Not based on what's easiest. Not based on what seems interesting.
Based on what matters.
Every yes requires ten nos.
We understand cost. Not just the cost of building. The cost of delay. The cost of choosing wrong. The cost of saying yes when we should have said no.
Opportunity cost is real cost.
We make trade-offs visible. Transparent. Understood.
This feature means not that feature. This timeline means this quality level. This scope means these constraints.
There are no free choices.
We prioritize ruthlessly. Not carelessly. Ruthlessly.
With discipline. With evidence. With clarity about what we're optimizing for.
We don't pretend we can do everything. We choose what we can do exceptionally well.
Then we do it.
On Product
We validate before we build.
This seems simple. But it requires discipline.
The temptation is to build first. To see our ideas realized. To move quickly.
But speed without direction is just motion.
We test our riskiest assumptions first. We seek truth early. We embrace what we learn, even when it contradicts what we hoped.
Understanding increases. This is learning. Not scope creep.
The plan changes because we're smarter today than we were yesterday.
We celebrate this.
On Discovery & Validation
We don't know what to build until we learn what not to build.
Discovery is continuous. Not a phase. Not something we complete.
A practice.
We interview customers. We observe behavior. We run experiments. We ship small things to learn big things.
We prototype to learn. Not to convince.
The prototype that teaches us we're wrong is more valuable than the prototype that makes us look right.
We test assumptions. Risky assumptions first. The ones that could sink the whole effort.
What if customers don't actually have this problem? What if they won't pay for this solution? What if the solution doesn't solve the problem?
Better to learn this in week one than month six.
We validate demand first. Does the problem exist? Will customers pay?
Then solution. Does this solve the problem?
Then approach. How do we build it?
Each step requires evidence. Not conviction.
Conviction without evidence is just hope.
We tackle four risks together with the team:
Will customers value it? Will they buy it? Will they choose to use it?
Can users use it? Is it intuitive? Clear? Obvious?
Can we build it? With our current skills? Timeline? Technology stack?
Does it work for the business? Legally? Financially? Operationally?
All four must be true. The trio ensures all four.
We design experiments that could prove us wrong. Because experiments that can only prove us right teach us nothing.
We learn cheaply. Quickly. Honestly.
Then we build.
On Customers
We begin with the customer.
Not with technology. Not with our ideas. Not with what's possible.
We begin with need.
What problem are we solving? For whom? Why does it matter?
We ask why. Then we ask why again. And again.
We're searching for the root. The real need beneath the surface request.
We talk to customers. Not about them. With them.
Their words inform our decisions. Their problems guide our solutions.
When they're successful, we're successful.
On Stakeholders
Customers are primary. But not alone.
We navigate many voices. Executives. Sales. Support. Engineering. Marketing.
Each has needs. Constraints. Pressures. Perspectives.
Our job is to synthesize. Not to please everyone.
Pleasing everyone means disappointing everyone.
We listen to all. We optimize for the customer.
When stakeholders conflict, we return to first principles. What creates value? What serves the customer? What advances our strategy?
This provides clarity.
We translate between worlds. Customer language to executive language. Technical constraints to business impact. Business goals to technical requirements.
We make the invisible visible.
Budget conversations. Timeline negotiations. Scope discussions. These aren't interruptions to the work.
They are the work.
We communicate clearly. Frequently. Transparently.
We manage expectations honestly. Not optimistically. Honestly.
Better to disappoint early than to surprise late.
We build trust through consistency. Through delivery. Through truth-telling even when the truth is uncomfortable.
Stakeholders don't need us to be perfect.
They need us to be trustworthy.
On Team
The best products emerge when talented people have space to create.
Our role is to provide clarity. Then get out of the way.
We trust the team. We believe they're competent. We believe they care.
This trust isn't blind. It's intentional.
We hire professionals. We treat them as professionals.
We give context. We set boundaries. We define outcomes.
Then we let them work.
The answer to "how" belongs to those closest to the problem.
On Collaboration
We don't own outcomes alone.
We own them with designers. With engineers. With researchers. With the team.
This is partnership. Not hierarchy.
We bring customer insight and business context. They bring technical feasibility and design expertise.
Neither knows enough alone.
We discover together. We decide together. We ship together.
This means real collaboration. Not handoffs disguised as collaboration.
We sit with designers as they sketch. We pair with engineers as they code. We discuss trade-offs in real time.
Not through documents. Not through meetings. Through working together.
We respect expertise. When the designer says "users won't understand this," we listen. When the engineer says "this will take three months," we believe them.
Then we discuss alternatives. Together.
We don't dictate solutions. We describe problems.
"The customer needs to complete this task faster" is a problem.
"Build a dropdown menu here" is a solution.
We bring problems. They craft solutions.
When conflict arises—and it will—we return to principles. What creates value? What serves the customer? What's technically feasible?
This resolves most conflicts.
For the rest, we make a decision and move forward.
Collaboration doesn't mean consensus. It means working together effectively.
Even when we disagree.
The Center
At the intersection of value, product, customer, and team sits something essential.
Outcomes over outputs.
This is the core principle. The organizing truth.
We're accountable for whether the product succeeds. Not for whether we were busy. Not for whether we tried hard.
For whether it worked.
This accountability is clarifying. It forces honesty.
It requires courage.
We make decisions with incomplete information. We accept uncertainty. We move forward anyway.
Better a decision than paralysis.
Better wrong than frozen.
We adapt to learning. When reality contradicts our assumptions, reality wins.
Plans are guesses. Learning is truth.
On Craft
Product ownership is a craft.
Like any craft, it requires practice. Attention. Intention.
We develop instinct through repetition. We learn what works through what doesn't.
We communicate clearly because unclear communication creates unclear products.
We prioritize because not everything matters equally.
We balance short-term tactics with long-term vision. Present and future. Today and tomorrow.
This is difficult work.
It requires us to hold multiple truths simultaneously.
What We Don't Do
We don't ship features for the sake of shipping.
We don't commit to timelines we can't deliver.
We don't pretend to know things we don't know.
We don't avoid difficult conversations.
We don't hide from stakeholders.
We don't ignore data that contradicts our beliefs.
We don't micromanage how the work gets done.
We don't confuse activity with progress.
These are choices. Daily choices.
The discipline is in the consistency.
On Strategy
Strategy isn't something we create once and execute forever.
It's alive. It evolves.
We adjust as we learn. As the market shifts. As customers change.
Stubborn adherence to a broken strategy isn't dedication.
It's denial.
But strategy must remain coherent.
Adaptation doesn't mean scattered. It means focused evolution.
We adjust the path. Not the destination. Not randomly.
Changes connect to the whole. Not random pivots.
Coherent focus. Not chaos.
Strategy and execution aren't separate phases.
They're intertwined. Inseparable.
The doing informs the thinking. The thinking guides the doing.
On Success
Success is when the customer achieves their goal.
Not when we ship a feature.
Not when we meet a deadline.
Not when we stay busy.
When the customer succeeds.
Everything else is secondary.
This clarity simplifies decisions.
Does this help the customer succeed? Then yes.
Does this not help the customer succeed? Then no.
Simple. Not easy. But simple.
On Measuring Success
We measure outcomes. Not outputs.
Features shipped is an output. Customer behavior changed is an outcome.
Story points completed is an output. Value delivered is an outcome.
Hours logged is an output. Problems solved is an outcome.
Outcomes matter. Outputs don't.
We know the difference between a metric that informs and a metric that misleads.
Vanity metrics feel good. Actionable metrics drive decisions.
We choose actionable.
Our metrics answer questions. Is the customer successful? Are we solving the right problem? Is this working?
We measure honestly. We don't hide declining metrics. We don't cherry-pick improving ones.
The truth serves us. Even when it's uncomfortable.
Especially when it's uncomfortable.
We review metrics regularly. We ask: what did we learn? What should change?
Then we change it.
On Evidence-Informed Decisions
Opinions are cheap. Evidence is expensive.
We pay for evidence.
We run experiments. We analyze data. We talk to customers. We measure behavior.
Then we decide.
Not the other way around.
Data doesn't make our decisions. We do.
But data informs our decisions. Grounds them. Tests them.
We're data-informed. Not data-driven.
Because data without judgment is just numbers. And judgment without data is just guessing.
We bring both.
We ask: what would prove us wrong? Then we seek that evidence.
Confirmation bias is real. We don't look only for data that supports what we want to believe.
We look for truth. Even when truth is inconvenient.
When evidence and opinion conflict, evidence wins.
Every time.
We change our minds. Often. Publicly.
This isn't weakness. It's strength.
Clinging to decisions despite contrary evidence isn't conviction. It's pride.
We choose learning over being right.
On Complexity
Some problems are simple. Some are complicated. Some are complex.
We must know the difference.
Simple problems have obvious answers.
Complicated problems need expertise.
Complex problems need experimentation. Because nobody knows the answer yet.
Treating complex problems as if they're merely complicated wastes time.
We probe. We sense. We respond.
We don't plan what we cannot predict.
On AI
AI accelerates our work.
But it doesn't make our decisions.
We set the direction. We define the constraints. We ensure quality.
The tool serves us. Not the other way around.
Speed without judgment creates fast mistakes.
Trust and verify. AI lies.
Even better: consider zero trust of AI.
We remain the anchor.
On Leadership
We lead through clarity. Not authority.
We enable decentralized decisions.
We push authority down to those closest to the information.
We create the conditions for others to make great choices.
Then we step back.
Intent-based leadership.
We state the outcome. The team finds the path.
This is trust in action.
The Capabilities
These are the essential capabilities. Not all of them. Just the ones that matter most.
Empiricism
We learn by testing. Not by having opinions.
When someone says "users will love this," we say "let's find out."
Reality always wins.
Prioritization
We sequence work based on value. Not on what's easy. Not on what's interesting.
On what matters.
Every yes requires a no.
We're ruthless about this.
Accountability
When the product fails, it's on us.
Not the team. Not the market. Not circumstance.
Us.
This is clarifying.
Vision
We know where we're going.
We can articulate it clearly. Simply.
If we can't explain it, we don't understand it.
Adaptability
Plans change because we learn.
We don't cling to decisions when evidence suggests we were wrong.
We adapt.
Communication
We explain the same thing differently to different people.
Executives need one message. Developers need another. Customers need a third.
We translate.
Courage
We decide with incomplete information.
We say no to powerful people.
We kill our own ideas when they don't work.
This requires courage.
Discovery
We validate assumptions before we build.
We test early. We test cheaply. We test honestly.
Discovery before delivery.
Restraint
We resist the urge to add.
More features. More options. More complexity.
We subtract instead.
Less, but better.
Trust
We trust the team to find the how.
We provide the what and where we're headed.
The rest is theirs.
Business Acumen
We understand how businesses work.
Revenue models. Cost structures. Market dynamics. Competitive forces.
We speak the language of business. With executives. With finance. With sales.
Not just product thinking. Business thinking.
Technical Acumen
We understand technology. Enough to have informed conversations.
AI capabilities. Robotics. Platforms. Architecture. Technical constraints.
Not to build it. To understand what's possible. What's practical. What's changing.
We stay current. We ask questions. We learn continuously.
Data Literacy
We read data. We interpret trends. We spot patterns.
When someone shows us a chart, we understand what it means. And what it doesn't.
We show evidence. Not just talk about it.
"Show me" isn't optional. It's essential.
Negotiation
We seek win-win outcomes.
With stakeholders. With teams. With customers. With ourselves.
Trade-offs. Timelines. Resources. Scope.
Not contract games. Not positional bargaining.
Collaborative problem-solving.
We listen first. Then we propose. Then we adapt.
We find alignment without compromising what matters.
Both sides better off. Not one side winning at the other's expense.
Influence
We influence without authority.
Through clarity. Through evidence. Through listening.
We persuade by understanding what others care about.
Not manipulation. Authentic influence.
We change minds by earning trust.
Customer Understanding
We understand the job to be done.
Not what customers say they want. What they're actually trying to accomplish.
The outcome they seek. The progress they desire.
We dig beneath surface requests to find real needs.
This is capability in its essential form.
Not exhaustive. Essential.
The Work
The work is never finished.
Products evolve. Markets shift. Customers grow.
We iterate toward better. Not toward perfect.
Perfect doesn't exist.
Better always does.
We learn. We adjust. We improve.
This is the work.
Day after day.
Decision after decision.
Focus after focus.
In Closing
Product ownership is the intersection of empathy and discipline.
We care deeply about customers. About team. About outcomes.
But care alone isn't enough.
We need discipline. Focus. Clarity. Courage.
The discipline to say no.
The focus to know what matters.
The clarity to communicate it.
The courage to be accountable for it.
Technology should serve people.
The product owner guides this direction.
Translating human need into valuable product.
With care.
With craft.
With focus.
That's the work.
This is what we believe.
This is how we work.
This is product ownership.
Share:
Product Owner –– The Shorter Version –– The intersection of purpose and craft –– At its essence, product ownership is about creating value through focused attention to what matters.
Stakeholder –– The Shorter Version –– Engaging actively. Experiencing value. Validating outcomes.