Emerging Technologies in CPE
Rethinking Product Development
Prepared by:
Engr. Stephanie Grace V. Cortes
Sources:
https://www.thepowermba.com/en/blog/lean-startup-methodology
https://www.interaction-design.org/literature/topics/design-thinking
https://www.productplan.com/glossary/jobs-to-be-done-framework/
Rethinking Product Development
Rethinking product development:
• Lean Startup
• Design Thinking
• Jobs to be Done
Lean Startup Methodology
First coined by Eric Ries in his book The Lean Startup, the
methodology is inspired by the principles of Toyota’s famous lean
manufacturing model; reducing waste and optimizing resource
allocation.
Ries realized that the majority of startups fail because they invest too
much time, energy, and money into an idea that doesn’t work.
Lean Startup Methodology
“Break down your plan into a hypothesis and run experiments to
discover if they’re true or not”
Through a process of validated learning, you can carefully test your
assumptions through a product prototype and analyze solid, empirical
data obtained from customer feedback.
Lean Startup Methodology
Lean Startup
Methodology
Step #1 – Business Model
Canvas
Lean Startup Methodology
Step #2 – Formulating a Hypothesis
In descending order of importance, they are:
• Desirability - attractiveness of your proposal
• Viability - understanding that not only are you solving a problem
customers have but that it’s worth finding a solution for
• Feasibility - ability to deliver your project
Lean Startup Methodology
Step #3 – Minimum Viable Product (MVP)
Definition of MVP is:
“The version of a new product which allows a team to collect the
maximum amount of validated learning with the least effort.”
But, through the development of an MVP startups can measure, learn,
and validate their hypotheses by hitting the market as soon as possible,
with ‘something’ that enables you to have real interactions with clients.
Lean Startup Methodology
Step #4 – Learning
The final step of the lean startup methodology is, of course, learning.
How can you insert customer feedback back into the Build Measure
Learn Cycle to ultimately ensure product-market fit?
Design Thinking Methodology
Design thinking is a non-linear, iterative process that teams use to
understand users, challenge assumptions, redefine problems and create
innovative solutions to prototype and test.
Design Thinking Methodology
Design Thinking Methodology
Stage 1: Empathize—Research Your Users' Needs
Here, you should gain an empathetic understanding of the problem
you’re trying to solve, typically through user research. Empathy is
crucial to a human.
Design Thinking Methodology
Stage 2: Define—State Your Users' Needs and Problems
It’s time to accumulate the information gathered during the Empathize
stage. You then analyze your observations and synthesize them to
define the core problems you and your team have identified. These
definitions are called problem statements.
Design Thinking Methodology
Stage 3: Ideate—Challenge Assumptions and Create Ideas
The solid background of knowledge from the first two phases means
you can start to “think outside the box”, look for alternative ways to
view the problem and identify innovative solutions to the problem
statement you’ve created. Brainstorming is particularly useful here.
Design Thinking Methodology
Stage 4: Prototype—Start to Create Solutions
This is an experimental phase. The aim is to identify the best possible
solution for each problem found.
Design Thinking Methodology
Stage 5: Test—Try Your Solutions Out
Although this is the final phase, design thinking is iterative: Teams
often use the results to redefine one or more further problems. So, you
can return to previous stages to make further iterations, alterations and
refinements – to find or rule out alternative solutions.
Jobs-To-Be-Done Framework
The jobs-to-be-done framework is an approach to developing
products based on understanding both the customer’s specific goal, or
“job,” and the thought processes that would lead that customer to
“hire” a product to complete the job.
When using this framework, a product team attempts to discover what
its users are actually trying to accomplish or achieve when they buy a
product or service.
Jobs-To-Be-Done Framework
How Does the Jobs-to-be-Done Theory Apply to Product
Development?
This framework takes the next step to explore customers’ true
motivations for buying. In the often-used example, the surface-level
explanation is, “I need a drill.” Probing a little deeper, we discover the
customer actually needs a well-drilled hole.
Jobs-To-Be-Done Framework
Product managers can use the jobs-to-be-done framework in two ways:
1. To get a better understanding of what their market wants or needs
2. To create a fascinating customer experience
Jobs-To-Be-Done Framework
As the book The Innovator’s Toolkit explains, a job-to-be done is
neither a product nor a solution itself; rather, it is the higher purpose
for which a customer would buy a product and solution.
Jobs-To-Be-Done Framework
Pros of jobs-to-be-done
1. It can help you better align what you’re building with what your
users really want.
2. It can keep you from building “a faster horse” that nobody wants.
Cons of jobs-to-be-done
1. It can lead your user research to become too abstract and high-level.
2. Some product teams believe it can lead to unimaginative design and
user experience.
Emerging Technologies in CPE
THE END
