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.
Key Activities
Own and maintain a single Product Backlog for the complete shippable product
Make strategic ordering decisions that optimize the whole product, not individual team output
Say ‘no’ to low-value work — the PO is the bottleneck by design, forcing prioritization discipline
Maintain a product-wide view — understand how all features connect to create customer value
Resist pressure to split PO authority across multiple people in basic LeSS (that’s a LeSS Huge pattern)
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.
Key Activities
Connect teams directly with real customers and users for requirements clarification and feedback
Facilitate — not mediate — the relationship between teams and the people who use the product
Ensure teams attend Sprint Reviews and interact directly with stakeholders
Avoid becoming a requirements bottleneck — teams should talk to customers, not wait for the PO to translate
Bring market and strategic context that teams may not have, while teams bring customer-level detail
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.
Key Activities
Facilitate multi-team and single-team refinement sessions where teams interact directly with customers
Ensure the top of the Product Backlog is refined enough for teams to select items in Sprint Planning
Help teams identify cross-team dependencies during refinement and design them away when possible
Participate in but don’t dominate refinement — teams are responsible for understanding and estimating their own work
Schedule refinement so that 2–3 Sprints of work is always refined and ready
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.
Key Activities
Present the highest-priority Product Backlog items to all teams in Sprint Planning Part 1
Guide teams in self-selecting work — the PO suggests priorities but teams choose what they can deliver
Clarify the relative priority and business context of items when teams have questions
Ensure that Sprint Planning Part 1 produces clear team commitments with minimal cross-team dependencies
Be available during Sprint Planning Part 2 for clarification but let teams drive their own planning
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.
Key Activities
Adapt the Product Backlog ordering after every Sprint Review based on real stakeholder and customer feedback
Use working software — not documents or plans — as the primary basis for product decisions
Practice ‘just enough’ planning — avoid detailed long-range plans that create false certainty
Track value delivery outcomes, not just feature throughput, to measure product success
Continuously challenge assumptions about what customers need using experiments and validated learning
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.
Work with management to remove organizational impediments that prevent teams from delivering value
Resist creating PO proxy roles, business analyst layers, or requirements teams that add distance from customers
Support the adoption of feature teams over component teams to reduce cross-team dependencies
Champion the LeSS principle: more value with less waste, more ownership with fewer roles
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.