Product Management: Design Sprint Flashcards
6 Stages of the Desing Sprint
- Understand
Create a shared understanding of the problem space, the user, the competition, and why it all matters. Align as a team on a focus moving forward for the rest of the sprint - Define
Start by focusing on where you want to end. By setting goals you can work backward to understand what needs to happen in order to get there. - Sketch
Ideate. Start diverging and exploring lots of different solutions. - Decide
Bring it all back together and decide on one idea to take through prototyping and validation - Prototype
Map out and build a prototype of your idea - Validate
Check to make sure that your idea is solving a real user need… and that it can be built!
Challenge Statement
[ACTION] + [OUTPUT] + FOR [USER] + TO [PROBLEM] + BY [TIMEFRAME]
UNDERSTAND: 3 common methods used to create a shared understanding and 3 common methods used for recording
Creating Shared understanding
- Lightning talks
- Interviews
- Competitive Analysis
Recording Understanding
- HMW
- Affinity Maps
- Rose, buds, thorns
Lightning Talk
A lightning talk is a short presentation, usually about 20 minutes, focused on a specific topic.
common topics include:
user-research: what do we know about the users, their goals, and problems
Business: Why does this problem matter to our company
Technology: What current capabilities do we have?
Interviews
Interviews
Interviews allow you to gain perspectives from a number of different vantage points. There are lots of types of interviews you can set up including:
User interviews
Build empathy for users
Get a deeper understanding of user needs and pain points
Stakeholder interviews
Dive deeper into some of the reasoning, rationale, and context of why this specific problem is important to solve. Topics can include any previous efforts to solve this or a similar problem
Expert interviews
Provide specialized insights around a specific problem, population, or technology
Competitive Analysis
Competitive Analysis
Get a better understanding of the competition and other solutions that exist in the problem space by:
Doing research, including checking out websites and press materials
Reading reviews
Using the product and recording your experience
DEFINE: 3 common methods used to create focus
- Success Metrics and Signals
- Design principles
- Future Press Release
Future Press Release
- Write a press release for the product which includes elements of the following components
Name of the product (although this doesn’t have to be final and can change)
Who is the target user?
What problem does your product solve?
How does your product solve this problem?
Why your team built this
Why should users care?
How do users react to your product?
What sets this product apart from others?
How can users get the product?
- Write a future Tweet for a future press release?
- Write a newspaper headline for a future press release?
DECIDE: 3 Common methods used to decide on ideas
1 Assumptions & Questions
2. Decision Matrix
3 Thinking hats
6 Thinking hats
Blue hat - process (align on goals and order of hats)
White hat - data
Green hat - creativity
Yellow hat - benefits
Black hat - judgment
Red hat - intuition
Blue hat - process (summary of discussion)
PROTOTYPE: Storyboarding
Storyboard maps out the problem facing your user and the journey they go through with your product to solve it
A storyboard is composed of frames that depict events along the user journey
Each frame should have a caption that explains what is happening and why
The first frame should explain how the user found themselves in this scenario and what is the problem they are trying to solve
The storyboard will become the blueprint for the prototype
Things to consider when planning a user study
Who is your target user? How many interviews will you have? What do you want to find out? Background information about the user Specific questions around your idea Tasks to complete with a prototype How much time you will need to complete each interview
General flow of a user study
- Overview/Background
- Signing the NDA
- General Questions About User
- Specific Questions About the product
- Specific Tasks
- User Feedback
- Thank you Message
What are P features?
P0 a launch blocking feature. The product will not launch without it
P1 a nice to have feature at launch, but not required. If not present at launch it should be a fast follow
P2 a desirable feature
P3, P4 unlikely to be built
PRD
Product Requirements Doc that specifies why we’re building a product, how the product will work, and how the product’s success will be measured.