2.1 The Preferred Product Owner Stances: Visionary, Collaborator, Customer Representative

The Preferred Product Owner Stances: Visionary, Collaborator, Customer Representative

Core PSPO II Principle: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How a Product Owner fulfills this accountability depends heavily on the behavioral stances they adopt. Rather than acting as a static requirements writer, an advanced Product Owner dynamically embodies stances that foster shared understanding, strategic alignment, and customer empathy.

In complex product environments, success is rarely determined by technical capability alone. It is driven by how effectively the Product Owner navigates human systems, aligns divergent interests, and uncovers real customer problems. Scrum.org identifies six preferred stances that represent the mature, value-maximizing expression of the Product Owner accountability:

1. The Visionary
2. The Collaborator
3. The Customer Representative
4. The Decision Maker
5. The Experimenter
6. The Influencer

This section delves deeply into the first three preferred stances, examining their behavioral foundations, practical artifacts, operational challenges, and practical implementation in Professional Scrum.

---

1. The Visionary Stance

Communicating an Inspiring Future State

The Visionary Product Owner is the chief storyteller and strategic compass of the product. Complex work requires intrinsic motivation; individuals do not commit their creative energy to arbitrary feature lists or transactional backlog tickets. They rally around an inspiring, purpose-driven future state that articulates why the product exists and how the world will be different once it succeeds.

In this stance, the Product Owner:

• Articulates the overarching Product Vision: Paints a vivid picture of the long-term destination, illuminating the positive change the product creates for customers, the organization, and society.
• Defines and champions the Product Goal: Under the 2020 Scrum Guide, the Product Goal serves as the commitment for the Product Backlog. The Visionary ensures that every Sprint Goal and Product Backlog Item (PBI) visibly bridges the gap between today's reality and the next strategic milestone.
• Connects daily execution to strategic purpose: Explains the economic and strategic rationale behind mundane or highly technical backlog items (e.g., technical debt remediation, security compliance, architectural refactoring), showing Developers how foundational work enables future capabilities.

+-------------------------------------------------------------------------+
|                           THE STRATEGIC CASCADE                          |
|                                                                         |
|  Organizational Mission  ---> Why the enterprise exists                 |
|           |                                                             |
|     Product Vision       ---> The inspiring long-term future state      |
|           |                                                             |
|      Product Goal        ---> The current strategic milestone (Commitment)|
|           |                                                             |
|      Sprint Goal         ---> The tactical outcome for the Sprint       |
|           |                                                             |
| Product Backlog Items    ---> The granular options to achieve the goal  |
+-------------------------------------------------------------------------+

Practical Frameworks for the Visionary

To translate abstract ambition into tangible focus, advanced Product Owners utilize structured strategic canvases:

• Roman Pichler's Product Vision Board: Anchors the vision across four core dimensions: Target Group (who is the product for?), Needs (what problem does it solve?), Product (what are the 3-5 key attributes?), and Business Goals (how does it create economic value for the enterprise?).
• The Elevator Pitch (Geoffrey Moore): Forces radical clarity using the standard template: For [target customer] who [statement of need], the [product name] is a [product category] that [key benefit/compelling reason to buy]. Unlike [primary alternative], our product [statement of primary differentiation].
• Cover Story & Press Release (Amazon Working Backwards): Drafting a mock future press release or magazine cover story celebrating the product's successful launch two years from now, capturing hypothetical customer testimonials, headline metrics, and market reactions.

Avoiding Ivory-Tower Hallucinations

A common failure mode for the Visionary is becoming an "Ivory-Tower Dreamer" who pontificates about grand futures while disconnected from technological realities and empirical feedback. An advanced Product Owner balances vision with empiricism:

• The vision provides direction, but intermediate Product Goals are continuously inspected and adapted based on real Increments.
• The Visionary welcomes empirical evidence that disproves strategic assumptions, pivoting the vision when market conditions or customer behaviors invalidate the original thesis.

---

2. The Collaborator Stance

Moving Beyond the "Requirements Hand-Off"

In traditional project management, product managers write exhaustive specifications (e.g., 50-page Business Requirement Documents) in isolation and toss them over an organizational wall to engineering. In complex software development, this hand-off model fails catastrophically because software development is an act of discovery, not an assembly line.

The Collaborator stance dismantles this wall. The Product Owner recognizes that the best solutions emerge through co-creation between business knowledge, customer empathy, and technical craftsmanship.

Partnering Across the Scrum Ecosystem

The Collaborator operates across three primary interfaces:

1. Collaborating with Developers:

   • Rather than bringing pre-baked technical solutions, the PO brings problems to be solved and desired customer outcomes.
   • Backlog Refinement becomes a vibrant working session where Developers ask probing questions, challenge assumptions, and suggest creative technical shortcuts that achieve 80% of the customer value with 20% of the development effort.
   • Techniques such as Example Mapping (Friends of Scrum / BDD) are employed: decomposing user stories into concrete business rules, realistic positive/negative examples, and unanswered questions.

2. Collaborating with the Scrum Master:

   • The PO and Scrum Master form an agile leadership partnership. The Scrum Master coaches the PO on effective Product Backlog management techniques, facilitates objective stakeholder workshops, and shields the PO from organizational politics.
   • Together, they monitor team health, eliminate systemic organizational impediments, and foster an environment of high psychological safety.

3. Collaborating with Business Stakeholders:

   • The PO transforms stakeholders from demanding "clients" into strategic collaborators.
   • Instead of receiving demands, the PO invites stakeholders into collaborative mapping sessions (such as Jeff Patton's User Story Mapping), building shared empathy for delivery trade-offs and capacity limits.

---

3. The Customer Representative Stance

Becoming the Voice of the Customer

The Customer Representative stance embodies deep, unapologetic customer empathy. In many organizations, product development becomes an echo chamber of internal opinions, executive pet projects, and sales-driven promises. The Customer Representative acts as the empirical counterweight, constantly asking: "What problem does this solve for our real end users, and what evidence proves they care?"

The Danger of Internal Proxies

A central topic on the PSPO II assessment is the danger of relying on internal customer proxies. Sales representatives, account managers, customer support agents, and marketing directors frequently claim: "We know exactly what the customer wants; you don't need to speak with them."

While proxy stakeholders provide valuable perspective, relying exclusively on them creates systemic distortions:

• The Sales Proxy Bias: Sales professionals are incentivized to close immediate contract opportunities. They consistently advocate for custom, one-off features demanded by the largest prospective client in the current quarterly pipeline, often at the expense of general product-market fit and long-term maintainability.
• The Support Proxy Bias: Support teams interact primarily with struggling or dissatisfied users. Over-indexing on support feedback causes teams to focus on edge-case bug fixes and UI band-aids rather than reimagining flawed core workflows.
• The "Telephone Game" Effect: Nuance, emotional context, and subtle user friction are stripped away when feedback passes through multiple organizational layers before reaching the Scrum Team.

   REAL USERS  --->  Sales / Support  --->  Product Manager  --->  Developers
 (Actual Need)      (Proxy Filter)        (Spec Filter)         (Code Built)
   
   RESULT: High latency, severe distortion, zero empathy, feature bloat.
   
   AGILE REMEDY: PO connects Developers directly with Real Users.

Practical Customer Discovery Techniques

The Customer Representative employs rigorous qualitative discovery methods:

• Direct User Interviews: Conducting open-ended contextual inquiries observing users in their natural operating environment rather than sterile conference rooms.
• Customer Journey Mapping: Visualizing the end-to-end customer experience across cognitive stages: Awareness, Consideration, Onboarding, Daily Usage, Friction/Disappointment, and Advocacy.
• Validated Personas vs. Proto-Personas: Creating behavioral archetypes grounded in empirical user research rather than demographic marketing stereotypes. A validated persona captures user motivations, jobs-to-be-done, specific pain points, and triggers for product adoption.
• Jobs-to-be-Done (JTBD) Framework: Focusing on the functional, emotional, and social "jobs" users are hiring the product to perform. As Clayton Christensen famously framed: customers do not simply buy products; they pull them into their lives to make progress against specific struggles.

Direct Exposure for Developers

A hallmark of the advanced Customer Representative is democratizing user empathy. The PO does not hoard customer contact as a personal power base. Instead, they invite Developers to participate in live customer interviews, observe usability tests, and interact directly with users during Sprint Reviews. When Developers witness a user struggle with an unintuitive workflow firsthand, the motivation to craft an elegant solution is exponentially higher than reading a Jira ticket.

---

Comparative Analysis: The Three Stances in Harmony

These three stances do not operate in isolation. In high-performing Scrum Teams, they form a continuous generative loop: the Customer Representative uncovers deep, unarticulated customer pain; the Visionary synthesizes those insights into an inspiring Product Goal; and the Collaborator invites the Scrum Team and stakeholders to co-create the high-value solutions that bring that goal to life.