Chapter
Business context defines everything
we do
What influences product success?
Chapter 2 - Invest in Key Business Outcomes
Time-bound priorities for Key Business Outcomes
Investing in Key Business Outcomes
Playing the Investment Game–what outcomes will the business bet on
in the next one-to-two months?
Chapter 3 - Identify the Solution and its Impact on Key Business Outcomes
Finding the right problem to solve
To build or not to build?
Creating an end-to-end view of the user and business (product/service) interaction
Estimating impact on Key Business Outcomes and derive value scores
Visualizing our priorities
using a 2 × 2 matrix
Chapter 4 - Plan for Success
What does success mean to us?
Mismatch in expectations from technology
Cost of technical trade-offs
Defining technical success criteria
Chapter 5 - Identify the
Impact Driven Product
Understanding product impact
The cost of creating an impactful product experience
Defining the Impact Driven Product
Deciding to build, buy, or not at all
The cost of a digital solution
Risks of not building something
Chapter 6 - Managing the Scope of an Impact Driven Product
Faster is not always smarter
Minimum Viable Product (mvp)
A brief time lapse on car making
So, what is the most impactful product?
Happy customers at every phase of the product
Chapter 7 - Track, Measure, and Review Customer Feedback
Why do well-made products fail?
Understanding the perceived
value of our product
What aspect of our product experience matters most?
How and when to collect feedback?
Is the consumer ready to share feedback?
Chapter 8 - Tracking Our Progress
The need for gratification
Is our product working well
for the customer?
Is our product working well for the business?
Chapter 9 - Eliminate Waste – Don't Estimate!
Why do we need estimates?
Why can estimates not be accurate?
What should be the outcome of an estimation discussion?
Chapter 10 - Eliminate Waste – Don't Build What We Can Buy
What got you here won't get you there
Feature black holes that suck up a product team's time
Chapter 11 - Eliminate Waste – Data Versus Opinions
#1 – data we need before we build the feature idea
#2 – data we need after we launch
a feature
Chapter 12 - Is Our Process Dragging Us Down?
Business and organization context
Reason #1 for process waste – striving for perfection
Reason #2 for process waste – striving for efficiency
Reason #3 for process waste –
striving to maximize throughput
Solutions to eliminating process waste
Solution #1 – don't strive for perfection, instead
set up outcome-driven timelines
Solution #2 – don't strive for efficiency, instead foster collaboration
Solution #3 – don't strive for throughput, instead restructure teams based on outcome-driven timelines
Chapter 13 - Team Empowerment
Tenets of lean software development
Another Book You May Enjoy
Lean Product Management
Disclaimer: Any content in publications that violate the sovereignty, the constitution or regulations of the PRC is not accepted or approved by CNPIEC.