From Vanity Metrics to Effective Product Culture
Watch the talk: https://businessofsoftware.org/talks/
Ditch your timeline roadmap - it’s setting you up for failure!
The further out you plan, the more you put on there, that timeline sits at the top, always marching forward, no matter what you put on the roadmap, everything always includes a due date and a time estimate.
As a result, you end up with a big pile of features, a big pile of due dates, all based on this big pile of assumptions.
You assume you know how much work and how long each feature is going to take.
You assume that nothing else is going to disrupt your timeline.
You’re also assuming that nothing else is going to come in to mess up your timeline - no changes in the market, no new competitors, no fresh ideas coming from customers, no need for iteration.
You assume that each feature will work as soon as launched.
You assume that each of these features actually deserves to exist!
What could possibly go wrong?
Well, you end up creating all these made up release dates,
which force your developers on stressful marches to launch on time,
and you give your sales and customers expectations you often can’t meet,
while usually being blind to great opportunities in the market,
and downright building the wrong things.
And this leads to you, being a sad product manager.
Vicious cycle
Big buffers, slow work
Blame culture
Tighter controls, less freedom
Quality suffers, problems go unsolved
And it creates a vicious cycle that can be hard to get out of.
Here's what you can do...
14. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
You assume you know how
much work and how long
each feature is going to
take.
Assumption #1
Time
Feature A
Feature B
Feature C
15. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
You assume that nothing else is
going to disrupt your timeline.
Assumption #2
Time
16. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
You assume that each
feature will work
as soon as it is
launched.
Assumption #3
✔
✔
✔
17. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
You assume that each of
these features actually
deserves to exist!
Assumption #4
✔
✔
✔
18. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
Made up release dates
Development due date marches
Mismanaged expectations
Missed market opportunities
Building the wrong thing
Sad product managers
What could possibly go wrong?
50. Product vision template
FOR (target customer)
WHO (statement of need or opportunity)
THE (product name) IS A (product category)
THAT (key benefit, reason to buy)
UNLIKE (primary competitive alternative)
OUR PRODUCT (statement of primary differentiation)
Find this free template at: www.prodpad.com/vision-template
65. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
Likely months away,
but aligns with vision
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Current development
work in progress
- experiment 1
- experiment 2
- experiment 3
Current prototyping
work in progress
- experiment 1
- experiment 2
- experiment 3
- experiment 4
Top confidence for next
work opening
Experimenting on a Lean Roadmap
Now Next Later
Lower confidence for
next work opening
66. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
Likely months away,
but aligns with vision
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Current development
work in progress
- experiment 1
- experiment 2
- experiment 3
Current prototyping
work in progress
- experiment 1
- experiment 2
- experiment 3
- experiment 4
Top confidence for next
work opening
Experimenting on a Lean Roadmap
Now Next Later
Lower confidence for
next work opening
67. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
Likely months away,
but aligns with vision
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Current development
work in progress
- experiment 1
- experiment 2
- experiment 3
Current prototyping
work in progress
- experiment 1
- experiment 2
- experiment 3
- experiment 4
Top confidence for next
work opening
Experimenting on a Lean Roadmap
Now Next Later
Lower confidence for
next work opening
70. @simplybastow // janna@prodpad.com // bit.ly/innovation-team-sport
Objective
Objective
Objective
Objective
Completed
(validation roadmap)
Result:
Testing results now
Result:
Increase by $200!
Result:
No change in #...
Result:
Decrease by 10%!
Top priority for next
work opening
Likely months away,
but aligns with vision
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Now Next Later
Immediate problem to
be solved, currently in
development
Immediate problem to
be solved, currently
being prototyped
Validating on a Lean Roadmap
87. Want to ditch your timeline roadmap? Get the guide!
www.prodpad.com/ditch-timelines
janna@prodpad.com // @simplybastow // slides: bit.ly/lean-roadmapping-okrs
88. Get in the
Sandbox!
Try ProdPad’s free Sandbox,
a pre-loaded account that
shows you what a typical
lean roadmap and OKR set-up
looks like.
Get in and play around!
prodpad.com/sandbox
89. Thanks!
Reach out if you have
questions or if I can help
with anything at all
@simplybastow // janna@prodpad.com
Always open for a chat about product!
Get the slides: bit.ly/lean-roadmapping-okrs