- re-invent with Design Thinking - quickly test with Design Sprint - implement incrementaly with Agile

1. Methodology
to develop a GOOD product: 3 phases, 3 methodologies
• most projects fails due to a Wrong product
• how develop a Good one?
Key points:
9/10 products fail because we build the WRONG product (Ash Maurya, Running Lean)
Most learning happens when you make the Real Customer test your product
So find ways to make your Customer test
As much as possible
As soon as possible

2. Methodology
to develop a GOOD product: 3 phases, 3 methodologies
• All product/project phases are important
• From the vision framing, the product framing to its implementation
Key points:
• Generate Vision with Design Thinking
• Quickly test your ideas with Design Sprint
• Implement incrementally with Agile

3. Methodology
to develop a GOOD product: 3 phases, 3 methodologies
to develop a good product (and maybe disruptive!)
• Get a good understanding of your customer insights (get its ‘blind spots’)
• Quickly tests your ideas with a minimum of investment
• Finally implement incrementally the product to constantly pivot when necessary
Key points: Design Thinking, Design Sprint and Agile are complementary and are covering all the product development
life cycle. In each step, find ways to test your ideas getting real users feedback.

4. Methodology
to develop a GOOD product: 3 phases, 3 methodologies
Define the Vision & the Business Model
with Design Thinking

5. Methodology
with Design Thinking, generate Vision ideas
We want to explore
• ‘Blind Spots’ on Client Experience
• and Disruptive Technologies
Key points:

6. Methodology
with Design Thinking, generate Vision ideas
From insights & blind spots,
• review your Business Value Proposition
• define your “North Star”
Key points:

7. Methodology
with Design Thinking, generate Vision ideas
More practically, you can articulate your agenda using
• 5 canvas
• And the simulation exercise: ‘What if Uber was managing your company?’
Key points:

8. Methodology
with Design Thinking, generate Vision ideas
To convince the jury with your pitch, follow the following principles:
• Compelling to catch
• Descriptive to convince
• What’s next?
Key points: pitching is about marketing. At this stage, you don’t need to be complete. You need to be clear about the
problem you want to solve and give some information (not all!) about how you think to do it.

9. Methodology
with Design Thinking, generate Vision ideas
Other tools/canvas you can use to better understand your client & frame your Value proposition
Key points:

10. Methodology
with Design Thinking, generate Vision ideas
Other tools/canvas you can use to better understand your client & frame your Value proposition
Key points:

11. Methodology
with Design Thinking, generate Vision ideas
Other tools/canvas you can use to better understand your client & frame your Value proposition
Key points:

12. Methodology
to develop a GOOD product: 3 phases, 3 methodologies
Quickly test your ideas
to decide which product to develop
with Design Sprint

13. Methodology
with Design Sprint, quickly test your ideas
“How to solve big problems and test new ideas in just 5 days”
by Jake Knapp (GoogleVentures)
Key points: within the group of 5 to 10 people, ensure you will have the Decider (Sponsor, CEO, …) at least at the key
moments (e.g. Wednesday)

14. Methodology
with Design Sprint, quickly test your ideas
Design Sprint applies the Design Sprint Double Diamond principle
Key points:

15. Methodology
with Design Sprint, quickly test your ideas
how you can adapt Jake Knapp’s principle of Design Sprint to your context
• Example of a real case where the file is passing through many steps, many departments, many hands
• The consequence is today, nobody knows where it is …
Key points:
“At anytime we want to know where the file is, who we can call to
proactively communicate in case of any delays”
User promise
Your mission : given the User promise, you have 5 days to
o propose a first step toward the User promise (a MVP v0)
o check if your idea is a good one … or not & pivot
Your means: almost nothing!
o A few hours with key process stakeholders
o No IT budget or really limited one
Do you accept the mission …

16. Methodology
with Design Sprint, quickly test your ideas
how you can adapt Jake Knapp’s principle of Design Sprint to your context
• we did the job!
• with only 2 * 4 hours, 1 day to move the paper sketch to a balsamic sketch & 1 week of test
Key points:
Make the group
o propose a first step toward the User promise (a MVP v0)
o check if the first ideas are good … or not & pivot
MVP V0 : a first step towards the user promise
1 Build a backlog of
User Stories
3 Challenge your Story Board:
Is the process sustainable?
2 Build your User Journey
With a Story Board4 Challenge your Story Board:
Is the User Interface user friendly?
6
5 Test with real users:
Is your Story a Good Story?
“At anytime we want to know where the file is, who we can call to proactively
communicate in case of any delays”
User promise

17. Methodology
with Design Sprint, quickly test your ideas
• Build your User Journey with a Story Board
• In 3 steps, prioritize your backlog into MVP V0, MVP V1 & general backlog
Key points: to keep the timing and keep the group focused on the objective, pay attention to have a good facilitator. If you
don’t master yourself the meeting facilitation techniques, my advise is to look for one. And remember, your best friend
remains the post-it!

18. Methodology
with Design Sprint, quickly test your ideas
Is your journey sustainable? drafting & running the process, make the ideas more concrete for the group
• Each role is listing the data he wants to monitor
• The group has to tell when & who will input those data
Key points:
Create Process step 1 Event 1
Input
✓ Data A
✓ Data B
✓ Data C
✓ Data D
Input
role 1
Key events
role 2
Key
roles
Input
Consult
Consult Consult
ConsultConsult
✓ Data 1
✓ Data 2
✓ Data 2
Input
✓ Data 1
✓ Data 2
✓ Data 3
Questions:
Now the process is more concrete, is it sustainable? For each role?
…

19. Methodology
with Design Sprint, quickly test your ideas
Is the User Interface friendly? drafting & running the GUI, make the ideas more concrete for the group ideas
• Each role is drafting the “look & feel” of the required screens
• If you can, ask a UX designer to give you a hand
Key points: warning! Doing this paper sketching, the group will certainly express other User Stories. Pay attention to point
them out and to ask the group to properly prioritize them (v0? v1? backlog?)
In session, the UX designer sketches in live on paper
Question:
Now it is even more concrete, are you still comfortable with your User Journey proposal?

20. Methodology
with Design Sprint, quickly test your ideas
Is your Story a GOOD story? Make real users test your prototype
• Based on the real test, run 5 interviews to get the users feedback
• More than 5 is not required as the others should confirm the previous feedbacks
Key points: of course, if you can take advantage of a more ‘clickable’ version, feel free to do it but it has to be ‘light’
Run your test with real users & get their feedbacks:
• Scope: limited scope but relevant
• Duration: from 1 day to 2 weeks
Move your paper sketch to a “Balsamiq Mockup”
Question:
Now it is even more concrete, are you still comfortable with your User Journey proposal?

21. Methodology
to develop a GOOD product: 3 phases, 3 methodologies
Develop your product incrementally
with Agile (Scrum, Kanban, …)

22. Methodology
Develop your product incrementally with Agile
• Each increment should be usable!
• Each release should be usable!
Key points: thanks to Henrik Kniberg for his example of the car! A common error applying Agile coming from Waterfall is
to implement a product component by component … but with iteration ;-) Like that you have the impression to be Agile
… but you are not.

23. Methodology
Develop your product incrementally with Agile
Visualize & refine the key Releases with a Story map
Key points: the difficulty of the Product Backlog is about keeping the rationale of the prioritization all along the product life
cycle. And the rationale is … the Story! So always keep the Product backlog with the Story Map … or replace it with the
Story Map?

24. Methodology
Develop your product incrementally with Agile
• A really simple & efficient way to get users requirements
• User Story template: As role [X], I want to do [Y] so that [Z]
Key points: they are many good ways to structure the requirements, so don’t spend too much time in discussion. But a
minimum, as you noticed the user story is ‘issued from a CONVERSATION between Customer, PO & the team …

25. Methodology
Develop your product incrementally with Agile
For more detail about Agile methodologies like
Scrum, Kanban, …
See other presentations