Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

The Product Manager / Product Owner AS A Scientist

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

We’ve all heard it before – “Talented technology team builds amazing products!” That… doesn’t create the impact that they wanted, not enough customers end up buying or the users aren’t happy with it, or <some other disappointment>…

This is an especially common problem with companies that have a “brilliant” idea or technology that someone goes developing in their garage (if startup) / innovation product development group (if enterprise). This could be a new product or just a new feature of an existing product. Typically, the Product Owner or Product Manager in the organization specifies what to build. If they’re somewhat Agile, they even work closely with the organization to build it incrementally and hopefully deliver it continuously. But still, even then, too often the product or features don’t provide the expected impact/benefits. Overcoming this challenge is a common theme that is discussed by attendees at our SAFe POPM Course.

The POPM is often SURE they know what’s the right thing to build (aka the “God complex”) – usually this is based on market research, customer interviews, etc.

But too often, the POPM doesn’t know that they don’t really know. Other times, the POPM knows that they don’t know, but aren’t sure how to drive the learning so that more is known.  The Agile approach is to build a working product and engage on an on-going basis with the customer, getting early feedback so that as a result of the customer’s interaction with your product – you will gain knowledge.

Does this sound familiar from another domain/world? Where else do people make concerted learning a matter of principle?

As can be guessed from the title of this article – the answer is in science – a close cousin of engineering. One of the basic pillars of modern science is using the scientific method and specifically its well-known-but-hard-to-pronounce hypothesis.

For those who are a bit fuzzy or unconvinced about how closely the hypothesis fits in here – the meaning of hypothesis as per the dictionary:

  • A supposition or proposed explanation made on the basis of limited evidence is a starting point for further investigation.
  • A proposition made as a basis for reasoning, without any assumption of its truth.  
    [emphasis added]


The famous British Biologist Thomas Huxley (a friend of Charles Darwin) once said:

“The great tragedy of science – the slaying of a beautiful hypothesis by an ugly fact.”

Archangel Michael slays the Devil. Painting by Guido Reni.

Who would have thought there could be such drama in science and the hypothesis 🙂

With this in mind, let’s see how “without any assumption of its truth” and “starting point for further investigation” applies to the POPM roles.

To approach things as a scientist, a POPM should first modestly understand that they have some underlying assumptions, honestly identify them, curiously phrase the hypothesis and openly and bravely seek the truth by evaluating the outcomes and then flexibly adjust based on the learnings.

For example, phrasing the expected business outcome as a hypothesis could be as follows:

We hypothesize that Feature A will generate 30% more transactions (or will cause users to do things 20% faster or to make 15% fewer mistakes, whatever the expected outcome).

It can be much simpler to have this approach as a startup, after all, you typically have to prove yourself quite quickly or the money will run out. In a larger more traditional enterprise, it’s often more difficult to adopt this mindset for various reasons such as the long lead time until reaching the customer to test the hypothesis, on-premise B2B environments, high customization as in professional services, etc. Nevertheless, as a POPM, one must always strive to make the desired impact, regardless of the organization’s size. In fact, the importance of having the right mindset in an enterprise is incredibly important to minimize the waste of developing too many (wrong) features. In large organizations, this is true for both Product Owners and Product Managers.

Once the hypothesis has earned its place of respect, as Konrad Lorenz once said:
“It is a good morning exercise for a research scientist to discard a pet hypothesis every day before breakfast. It keeps them young.

So, to openly and bravely receive the truth, the POPM must evaluate the measured outcomes and decide whether they must show flexibility and discard their hypothesis or keep it. The Lean Startup movement introduced the terms for this as to pivot (change direction) or to persevere (keep on with the direction).

Applying pivot might feel difficult to the POPM, as it means that we have disproved our hypothesis. On the other hand, we will have learned something and hopefully avoid an “OMG” headline, and as Lorenz said, pivots keep us “young” 😉

Subscribe for Email Updates:

Categories:

Tags:

Software Development Estimation
ScrumMaster Tales
System Team
Lean Agile
Implementing SAFe
Agile Delivery
Lean and Agile Principles and Practices
Lean-Agile Budgeting
Scrum.org
Jira Cloud
Business Agility
Certified SAFe
speed at scale
SA
Agile Risk Management
Slides
Lean Agile Leadership
Agile Outsourcing
ART Success
What Is Kanban
Large Scale Scrum
Agile Development
Lean Risk Management
PI Planning
Lean Budgeting
Product Management
Software Development
User stories
Pomodoro Technique
Risk Management on Agile Projects
ROI
Perfection Game
SAFe Release Planning
Sprint Retrospectives
AI
Agile Basics
Achieve Business Agility
Professional Scrum with Kanban
SPC
Jira Plans
Test Driven Development
Atlaassian
The Kanban Method
Agility
Reading List
Advanced Roadmaps
Continuous Integration
RTE Role
Development Value Streams
SAFe
Agile Contracts Best Practices
lean agile change management
Agile
Code
Accelerate Value Delivery At Scale
Self-organization
Lean and Agile Techniques
Managing Projects
Portfolio for Jira
Lean Startup
LAB
Jira
Coaching Agile Teams
Agile Program
ATDD
Effective Agile Retrospectives
ATDD vs. BDD
Agile Games and Exercises
SAFe DevOps
Rapid RTC
Kanban Game
Systems Thinking
Change Management
Agile Marketing
Scrum and XP
Acceptance Test-Driven Development
PI Objectives
Kaizen
Scrum Master Role
Planning
Agile and DevOps Journey
Product Ownership
Games and Exercises
Agile Project
Agile Product Development
Scrum Values
Agile for Embedded Systems
Kanban Kickstart Example
QA
Legacy Code
Professional Scrum Product Owner
Agile Games
Nexus
Lean Software Development
A Kanban System for Software Engineering
Atlassian
GanttBan
WIP
Agile in the Enterprise
Kanban Basics
Spotify
RSA
Webinar
Daily Scrum
NIT
TDD
Implementation of Lean and Agile
Agile Testing Practices
Scrum Master
Built-In Quality
Kanban
Agile Israel Events
System Archetypes
ARTs
Value Streams
Kaizen Workshop
IT Operations
Agile Techniques
Releases Using Lean
Video
agileisrael
Introduction to Test Driven Development
Continuous Planning
Scrum Primer
Agile Exercises
Agile Community
chatgpt
Certification
Principles of Lean-Agile Leadership
Sprint Iteration
Agile Israel
Agile Release Planning
Story Slicing
AI Artificial Intelligence
RTE
Lean Agile Management
Managing Risk on Agile Projects
predictability
Agile Mindset
Manage Budget Creation
Agile Product Ownership
Scaled Agile Framework
Nexus vs SAFe
Covid19
Engineering Practices
Legacy Enterprise
Continuous Improvement
Introduction to ATDD
System Integration Environments
Scrum
Release Train Engineer
Nexus and SAFe
Iterative Incremental Development
Quality Assurance
Sprint Planning
Artificial Intelligence
DevOps
Entrepreneurial Operating System®
EOS®
An Appreciative Retrospective
Risk-aware Product Development
Jira admin
AgileSparks
Scrum Guide
BDD
Agile Release Management
Tools
Lean Agile Basics
ALM Tools
speed @ scale
Process Improvement
Nexus Integration Team
Tips
Hybrid Work
Agile India
Agile Assembly Architecture
LPM
Program Increment
Professional Scrum Master
POPM
Operational Value Stream
Applying Agile Methodology
The Agile Coach
Amdocs
Elastic Leadership
Presentation
Limiting Work in Progress
Lean Agile Organization
LeSS
Risk Management in Kanban
Frameworks
Kanban 101
Continuous Delivery
Continuous Deployment
Lean-Agile Software Development
Scrum With Kanban
Nexus and Kanban
Agile Project Management
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart