LeSS Role Framework

Product Owner

In LeSS, there is one Product Owner for the entire product. They own the single Product Backlog, facilitate direct team-customer connection, guide strategic prioritization, and advocate for organizational simplicity.

One PO
Single person, not a committee, for the whole product
Strategic Focus
Prioritizes the whole product, not individual teams
Customer Facilitator
Connects teams directly with real users
Empirical Planner
Adapts based on working software, not documents
Simplifier
Advocates for fewer roles and less waste

Whole-Product Ownership

In LeSS, there is exactly one Product Owner for the entire product — regardless of whether there are 2 teams or 8. The PO has full content authority over the single Product Backlog and focuses on strategic prioritization for the whole product.

Click to expand

Direct Customer Connection

The LeSS PO doesn’t act as a proxy between teams and customers. Instead, they facilitate direct team-customer interaction — teams do the refinement work directly with real users.

Click to expand

Refinement Facilitation

The PO doesn’t refine the backlog alone. In LeSS, Product Backlog Refinement is a multi-team collaborative activity where teams work directly with customers and stakeholders to understand upcoming work.

Click to expand

Sprint Planning Leadership

In LeSS Sprint Planning Part 1, the PO presents priorities to all teams simultaneously. Teams then self-select which items to work on, with the PO guiding alignment on the most valuable work.

Click to expand

Adaptive Product Planning

The PO practices empirical product planning — adapting direction based on real feedback from working software, not from documents, roadmaps, or stakeholder opinions divorced from data.

Click to expand

Organizational Influence

The LeSS PO works to simplify the organization and remove waste — advocating for fewer handoffs, fewer intermediaries, and more direct team-to-customer connection.

Click to expand

In LeSS, the Product Owner is deliberately a single person — not a team, not a committee. This constraint forces real prioritization and prevents the diffusion of product accountability. The PO focuses on strategic ‘what’ and ‘why’ while teams own the ‘how’ and work directly with customers for detail.