---
# System prepended metadata

title: Product Owner (PO)

---

*Editors of this document: Casey Alt, Sean Moss-Pultz, Cuong Le*

# Product Owner (PO)

In Bitmark, we aim for a PO-Engineering partnership. This means joint discovery, decision making, and shared accountability. Engineers join POs in customer interviews, and POs are in cycle meetings to help unblock tasks or clarify requirements. 

The two roles respect the line where one starts and the other stops. POs understand what’s being coded but don’t tell engineers how to code, and engineers have empathy for customers’ needs but leave the prioritization to the POs.

The biggest questions POs should always be asking is if they're solving the right set of problems and in what order. You don't want just a bunch of nice to have features, you want some features that are really really good. Which feature are you going to "sell" to the user first?


## Responsibilities
- Own vision, strategy, and roadmap of the product.
- Articulate the business value of the product to the team.
- Prioritize improvements through experiments (Eg: customer inverviews, user tests, ...)
- Come up with pricing and revenue modeling
- Define and track success metrics

## More Background

The reason we seek a PO-engineering partnership is we develop software products and bits don’t have marginal cost. Therefore the process of manufacturing software can and should be radically different from the past.

Fully embrace the unique opportunity to take what is incomplete and imperfect and make it more perfect by combining real-time understanding of customer needs with the latest technological advances:


- BEFORE: finished product, painstakingly crafted with integrity
- NOW: unfinished product, modified by observing how it survives in the wild
