Outcome based product management seems to be taking off. Along with Hypothesis based development, this has turned around product development from detailed product roadmaps that we used to have to more customer and user focussed product development. However, We seem to fall under the trap of Build-Measure-Learn and not measure the right things. A lot of times, we measure lag indicators that do not help us learn faster. Lag indicators are history, they tell us what we did right and wrong post-facto after the event has happened. We need a way to understand and measure how features can go into a product roadmap as we are building it or as we are considering it. Lead measures help us with that.

1. Lead measures Vs Lag
measures
How to measure your product success

2. Key Challenge in Product Management
● How do we know which is
the right feature to build
for the user
● Hypothesis based Product
Management
Build
Learn
Measure
03
01 02

3. But what do we measure?
We measure how the users reach to the product features that
we built.
It avoids building too big a feature and helps in building small
enough features and testing often.
However...
It is too late and there is a lag in the feedback.

4. Lag Measures
A lag measure is one in which we can measure the user
response.
A common e.g. given is weight loss
Exercise &
Diet
Pick the right
combination that
worked
Measure
Weight
03
01 02

5. Lead measure
A lead measure is one in which we can measure the input
that leads to the appropriate user response.
Exercise & Diet
Measured
Weight
Components of exercise
and weight
Amt of Greens in
daily food
# of miles running
every day

6. Have you got any other examples??
Plan & execute
change program
Pick the most
successful
aspects of plan
and repeat
Track completion
of each step and
user adoption
03
01 02
Execute
Change
program plan
Measure user
adoption
Components of
change program
# of steps user takes
to take decisions
Turnaround time for
information access

7. Need more information..
Let’s Chat
prashanth.madhavan@gmail.com