The Product Manager / Product Owner AS A Scientist


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” 😉



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

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