Product Strategy - How to figure out a plan for your product?
- What is product strategy?
- How do you evaluate your current position and performance (KPIs, metrics, Kano..)
- Can you be agile and have a vision?
- How to master the art of roadmapping when you have to juggle short term gains and longer term projects?
How well are you currently doing?
Are your customers happy with your product?
• NPS – Net Promoter Score
• AARRR – Acquisition Activation Retention Revenue Referral
• LTV – Lifetime Value
Beware of vanity metrics like #downloads, views, …. easily
Why are your customers happy with your product?
What problems are you solving?
Define your “jobs to be done” Users are “hiring” apps/services to get a job done.
Here are some common jobs that have been around for a
● Get a package from A to B with confidence, certainty
● Keep everyone up to date on a project they’re
● Get me face to face with my colleague in San
How much value do customers see in your features?
Survey users and non-users in your target to map your features using the Kano framework
Which features are critical, which aren’t?
Do you need a vision?
What about being agile and finding out along the way
• “Fail fast” requires to recognize when a failure happens, which isn’t that easy
• Frequent changes of positioning are expensive
• Solving problems is what pushes tech frontiers
• Employees need purpose
“Stubborn on vision. Flexible on details.”
Vision without BS
« The product vision should describe a broad and engaging goal: a goal that guides the development effort but
leaves enough room for creativity; a goal that engages and inspires people, fosters creativity, and generates
Scrum Alliance, The Product Vision
Jim Collins Framework
Deezer is an audio company.
We fill every moment of your life with sounds.
Our product tunes in to your aspiration to feel emotions, escape,
have fun, relax, focus and learn about the world.
The sound in your ears all day long
IN THE MORNING
NEWS, MUSIC &
1 000 000 ideas vs 6 tech people
- Write all ideas down
- Set aside all that are not aligned with your vision, do not match your current audience, have a wrong
time to market, …
- Gather the remaining ones in various consistent initiatives
- Evaluate initiatives
- Focus on one or a few initiatives (bets) that you’ll be able to evaluate
- Keep your focus
Involve and get buy-in from top management & key stakeholders at every step.
Competitors aren’t necessarily the ones
providing similar solutions as yours.
- Does the initiative fit your vision?
- How valuable is it? Does it help delivering the right
“job” for your target users?
- Will it cannibalize another key feature?
- What is the cost of doing it? not doing it?
- Will you be good at delivering it? (betting on
strengths rather than weaknesses)
Your market conditions
- It the time to market right?
- How differentiating is it vs other competing
- What is the acquisition potential?
Beware of vicious circles
if (Feature.KPI < expectations)
Bad implementation is only 1 possible reason for a feature’s lack of adoption. Other reasons may
- Bad time to market
- Wrong audience
- Wrong platform
Ruthless prioritization - Know when to say no
The amount of time spent by product managers
on unplanned ‘fire-fighting’ activities
Product Focus 2016
→ Communicate the plan, and the why, all the time
Stick to the plan until it succeeds or fails, one initiative after
• A is giving us 3 million to do X
• One of our investors want X
• My cousin said her neighbor only uses Y
• The new hype is Z