Quick guide to the Design sprint.
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at Google Ventures, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more — packaged into a battle-tested process that any team can use.
To use the links within the deck - download the presentation and open it in the browser.
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
The Design Sprint: A Fast Start to Creating Digital Products People Wantdpdnyc
In this talk, you'll learn how to plan, facilitate, and optimize the five phases of a Design Sprint: Understand, Diverge, Converge, Prototype, and Test. You’ll learn why and how Design Sprints work and how you can use Design Sprints to enhance your own design process.
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
The Design Sprint: A Fast Start to Creating Digital Products People Wantdpdnyc
In this talk, you'll learn how to plan, facilitate, and optimize the five phases of a Design Sprint: Understand, Diverge, Converge, Prototype, and Test. You’ll learn why and how Design Sprints work and how you can use Design Sprints to enhance your own design process.
A talk I gave at Google on Strategy and Product Discovery
We discussed:
Discovering Features and Products (Product Strategy)
Discovering Products and Product Lines (Product Line / Company Strategy)
Marty Cagan: Using High Fidelity Prototypes for Product Discovery
The key points:
▫️Empathy in business and how to measure it?
▫️Design thinking tools
▫️How to handle uncertainty as the project evolves?
▫️Design thinking in IT — how does it work?
▫️Tips and tricks on design thinking methodology.
Stakeholder Management for Product Managers - ProductTank ParisJean-Yves SIMON
How to manage your Stakeholders, mainly internally when you're a Product Manager working in a medium to large organization. Tips on how to be efficient and recognized within your organization.
Teresa Torres - An introduction to modern product discovery - Productized16Productized
The world of product management is changing quickly. In the past five years alone, we’ve seen the rise of The Lean Startup, design thinking, the Jobs-to-be-done framework, design sprints, OKRs, and much more. It can be hard for product teams to keep up. In this talk, you’ll learn a simple framework for how to make sense of all of these trends. You’ll learn how to mix and match methods in a way that leads to a coherent strategy that leads to better products.
Teresa is a product coach helping teams adopt user-centered, hypothesis-driven product development practices, and is the creator of Product Talk. She works with companies of all sizes on integrating user research, experimentation, and the right analytics into the product development process resulting in better product decisions.
Agile Product Development Playbook - Popular Tools and TechniquesAndy Birds
This Playbook provides an overview of some popular agile product development tools and techniques that Andy has found useful when building products. The Playbook focuses on Product Roadmaps as a keystone tool and provides a very high-level overview of other tools including; Product Vision Canvas, Product Canvas, Business Model Canvas, and Lean Canvas.
The Playbook is ideal for Product Managers, Product Owners, Business Analysts, User Experience Designers and anyone who works on an agile team or squad.
Design Thinking & Agile Innovation Workshop combining elements from Design Thinking, Customer Development, Christensen's Jobs to be Done, Osterwalder's Value Proposition Canvas, Javelin Experiment Board, Lean Startup and Paper Prototyping.
New York Bestseller Jake Knapp’s book, Sprint, explores how companies and teams can replicate Google’s sprint process to solve a problem within five days.
So how does a design sprint actually work, and how can you use a sprint to devise effective solutions in such a short period of time?
Enhance your productivity through design sprints, you’ll learn:
- What is a Design Sprint
- Design sprint case studies and success stories
- How you can run a design sprint effectively
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
December 2017 presentation covering: What is design thinking? What does it look like in practice? What are some case stories of design thinking being used in the real world? How can we use design thinking in our organization? Where can I learn more?
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
Centre for Entrepreneurship (C4E) of the University of Cyprus and Berklee Institute for Creative Entrepreneurship (ICE) present the:
Why are some designs better than others, and what can you do about it? (The workshop)
If you've ever described a poster as heavy, a website as dense, an app as clumsy or an object as whimsical, you probably already know the answer. Recent psychology research is showing that experiential metaphors are key emotional drivers that impact our perception of the world. Applying these findings to design confirms what designers have learned throughout their careers—good design is subconscious first and rational second. Michael will share stories from this research and the IDEO portfolio then share tools to help you be more consciously subconscious.
Our session at the 2016 Connect Week in Pasadena. An interactive session where we covered product design challenges, and the why, how, what of Design Sprints, originally developed by Google Ventures
A talk I gave at Google on Strategy and Product Discovery
We discussed:
Discovering Features and Products (Product Strategy)
Discovering Products and Product Lines (Product Line / Company Strategy)
Marty Cagan: Using High Fidelity Prototypes for Product Discovery
The key points:
▫️Empathy in business and how to measure it?
▫️Design thinking tools
▫️How to handle uncertainty as the project evolves?
▫️Design thinking in IT — how does it work?
▫️Tips and tricks on design thinking methodology.
Stakeholder Management for Product Managers - ProductTank ParisJean-Yves SIMON
How to manage your Stakeholders, mainly internally when you're a Product Manager working in a medium to large organization. Tips on how to be efficient and recognized within your organization.
Teresa Torres - An introduction to modern product discovery - Productized16Productized
The world of product management is changing quickly. In the past five years alone, we’ve seen the rise of The Lean Startup, design thinking, the Jobs-to-be-done framework, design sprints, OKRs, and much more. It can be hard for product teams to keep up. In this talk, you’ll learn a simple framework for how to make sense of all of these trends. You’ll learn how to mix and match methods in a way that leads to a coherent strategy that leads to better products.
Teresa is a product coach helping teams adopt user-centered, hypothesis-driven product development practices, and is the creator of Product Talk. She works with companies of all sizes on integrating user research, experimentation, and the right analytics into the product development process resulting in better product decisions.
Agile Product Development Playbook - Popular Tools and TechniquesAndy Birds
This Playbook provides an overview of some popular agile product development tools and techniques that Andy has found useful when building products. The Playbook focuses on Product Roadmaps as a keystone tool and provides a very high-level overview of other tools including; Product Vision Canvas, Product Canvas, Business Model Canvas, and Lean Canvas.
The Playbook is ideal for Product Managers, Product Owners, Business Analysts, User Experience Designers and anyone who works on an agile team or squad.
Design Thinking & Agile Innovation Workshop combining elements from Design Thinking, Customer Development, Christensen's Jobs to be Done, Osterwalder's Value Proposition Canvas, Javelin Experiment Board, Lean Startup and Paper Prototyping.
New York Bestseller Jake Knapp’s book, Sprint, explores how companies and teams can replicate Google’s sprint process to solve a problem within five days.
So how does a design sprint actually work, and how can you use a sprint to devise effective solutions in such a short period of time?
Enhance your productivity through design sprints, you’ll learn:
- What is a Design Sprint
- Design sprint case studies and success stories
- How you can run a design sprint effectively
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
December 2017 presentation covering: What is design thinking? What does it look like in practice? What are some case stories of design thinking being used in the real world? How can we use design thinking in our organization? Where can I learn more?
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
Centre for Entrepreneurship (C4E) of the University of Cyprus and Berklee Institute for Creative Entrepreneurship (ICE) present the:
Why are some designs better than others, and what can you do about it? (The workshop)
If you've ever described a poster as heavy, a website as dense, an app as clumsy or an object as whimsical, you probably already know the answer. Recent psychology research is showing that experiential metaphors are key emotional drivers that impact our perception of the world. Applying these findings to design confirms what designers have learned throughout their careers—good design is subconscious first and rational second. Michael will share stories from this research and the IDEO portfolio then share tools to help you be more consciously subconscious.
Our session at the 2016 Connect Week in Pasadena. An interactive session where we covered product design challenges, and the why, how, what of Design Sprints, originally developed by Google Ventures
A fun how to guide for running design sprints. Whether you are a seasoned design strategist or new to design, sprints are a must have technique for achieving speed when required.
Validate Your Ideas Quickly with Google Design SprintBorrys Hasian
This was presented at Compfest, an annual one-stop IT event held by students of Faculty of Computer Science, University of Indonesia. The deck is about Design Thinking and Google Design Sprint.
Intro to Lean Startup and Customer Discovery for AgilistsShashi Jain
This is a short presentation I made to the Portland Agile and Scrum group giving a light introduction to Lean Startup, Customer Discovery, and how you use them together to create a product-market fit.
I am glad I have the chance to teach how to do innovation for design and link to marketing in the university to share and sharp my skill of guiding students of innovation. Very grateful to have such experience in my life. This user experience innovation material is for small objects and quit for shot.
Five parallel design sprints. What possibly can go wrong?Den Tserkovnyi
Slides from my UXcamp Berlin presentation.
We, at StudyPortals, experiment a LOT with different design methods.
This time I talked about design sprints, a methodology introduced by Google. As a quick process to define the future of your product.
This year we challenged ourselves to run 5 design sprints at the same time, virtually occupying half of the company for a week of UX activities. How did we do it? What went wrong?
a move fast method to sharp the idea and design in five days. It has been proven to most of the startup under Google ventures. Want to know more how to build it, just contact me. :)
You Can Be a User Advocate by Devita Mira (Bukalapak)Tech in Asia ID
Devita is an UX Researcher at Bukalapak, an Indonesian based marketplace that focuses on helping Small Medium Enterprise (SME) with Internet.
This slide was shared on TIA DevTalk: "Key Ingredients of UI/UX for Development" on 27 January 2016.
TIA DevTalk is a monthly event of TIA Dev Community-- a community for all developers and/ or engineer to create collaborative things that advanced the tech community and ecosystem.
Get updates about our dev events delivered straight to your inbox by signing up here: http://bit.ly/tia-dev ! Be the first to know when new information is available!
Aha.io is a comprehensive, enterprise-level product management tool offering some of the most advanced capabilities for larger product teams. Even in their basic plan, you have access to powerful product discovery and planning tools that would satisfy mid-sized and large portfolios.
Product discovery is where Aha.io excels by offering not only the usual feedback options but also providing tools for B2B-focused orgs out there and even for researchers that otherwise would need to use other software.
Product planning and roadmapping could be performed in Aha.io on different levels. With a bit of tuning, both simple and more advanced prioritisation and planning techniques are supported. The results of your work could be easily shared both internally and externally.
Perhaps because Aha.io offers so many options their interface might appear clunky and old-fashioned. It might also require a substantial effort to set up the workspace correctly and so it should be done by experienced product ops or a seasoned PM.
Finally, there are still not so many PM tools that could support a massive product org and Aha.io probably got the closest to doing it. If you have hundreds of PMs, even more products and strong product ops - Aha.io should be the right kind of tool for you.
Jira Product Discovery is a solid first attempt by Atlassian to get into the product management software game. It offers just enough features at the moment to support small to medium discovery efforts and it will likely get better fast.
To be really useful for large and corporate customers it still needs to get improved, especially in the team management and user rights domains. I'd also love to see more in terms of creating and communicating vision and strategy for a product. Some features to more actively include users/customers in the product discovery will also be appreciated.
So if you run your product delivery in Jira and don't have any tool for product discovery - give JPD a try. It's currently free and could already add much value to your product team.
After trialling ProdPad for a few days I had a feeling it didn't change much since I used it seven years ago. It is still a clever product management tool for early-stage startups or small teams who need to figure out their initial offering. ProdPad is big on product discovery, offering folks some of the best ways to formulate and communicate their product vision and accumulate the right evidence.
Another thing that ProdPad does right is roadmapping. I think it's a good thing there's only one type of roadmap available in ProdPad (Now/Next/Later) as it teaches teams working on it to expect surprises and stay agile.
Where ProdPad users might find limitations is in the product delivery domain. The tool has limited options to visualise your development process, report on status or plan resources.
Therefore, I'd say ProdPad is a good entry-level PM tool that could be successfully used as a complementary to your product delivery software. For product managers, ProdPad offers simplicity and support to figure out the most important - your product vision and strategy.
Productboard is a sophisticated product management and operations software that could satisfy the needs of most product teams. In starting pricing tiers, it is very simple to get started with and use. In more advanced tiers, it adds features essential to bigger product teams with large product portfolios.
"Insights" and "Product portal" features of Productboard could bring your discovery efforts and collaboration with stakeholders to a new level. While the complete set of integrations ensures you can pass information in and out of the platform.
There are several question marks for me with regard to Productboard. First - their tiers. It felt that in lower tiers ("Essential" and "Pro") the product is too simplistic and would be useful only to the smallest teams working on their MVP. To support even a mid-sized product organisation with several products or a small portfolio - you will have to get either the "Scale" or "Enterprise" plan.
Craft.io is a comprehensive and solid product management tool that could accommodate both smaller (<10) and bigger (<100) product teams. Craft has all vital integrations to other crucial tools to discover and deliver winning products to the market. Craft's feedback portal makes it easier to gather insights from your stakeholders and the various "Guru" templates will help you prioritise work, create and report on product roadmaps.
Overview of a product operation process that could help you empower your product teams and build products that delight your customers while bringing value to your organisation.
Discovering the right product is a vital part of a product development process. To do that effectively best product teams use a Product Discovery process. It answers the question of what product to build. Done right it helps you build products customers would love.
How do I tell my boss i want to be a product owner - with a scriptDaniil Lanovyi
Who are those product owners? And from where are they coming from? Can I be a product owner? What should I do? Those and other questions would be answered in this presentation. Product management still hasn't any formal career path, therefore product managers are coming from all around. Interested in finding and solving market problems? Learn how can you become a product owner.
How do I tell my boss I want to be a Product Manager?Daniil Lanovyi
Who are those product managers? And from where are they coming from? Can I be a product manager? What should I do? Product management still hasn't any formal career path, therefore product managers are coming from all around. Interested in finding and solving market problems? Learn how can you become a product manager.
Book Formatting: Quality Control Checks for DesignersConfidence Ago
This presentation was made to help designers who work in publishing houses or format books for printing ensure quality.
Quality control is vital to every industry. This is why every department in a company need create a method they use in ensuring quality. This, perhaps, will not only improve the quality of products and bring errors to the barest minimum, but take it to a near perfect finish.
It is beyond a moot point that a good book will somewhat be judged by its cover, but the content of the book remains king. No matter how beautiful the cover, if the quality of writing or presentation is off, that will be a reason for readers not to come back to the book or recommend it.
So, this presentation points designers to some important things that may be missed by an editor that they could eventually discover and call the attention of the editor.
Unleash Your Inner Demon with the "Let's Summon Demons" T-Shirt. Calling all fans of dark humor and edgy fashion! The "Let's Summon Demons" t-shirt is a unique way to express yourself and turn heads.
https://dribbble.com/shots/24253051-Let-s-Summon-Demons-Shirt
Hello everyone! I am thrilled to present my latest portfolio on LinkedIn, marking the culmination of my architectural journey thus far. Over the span of five years, I've been fortunate to acquire a wealth of knowledge under the guidance of esteemed professors and industry mentors. From rigorous academic pursuits to practical engagements, each experience has contributed to my growth and refinement as an architecture student. This portfolio not only showcases my projects but also underscores my attention to detail and to innovative architecture as a profession.
Can AI do good? at 'offtheCanvas' India HCI preludeAlan Dix
Invited talk at 'offtheCanvas' IndiaHCI prelude, 29th June 2024.
https://www.alandix.com/academic/talks/offtheCanvas-IndiaHCI2024/
The world is being changed fundamentally by AI and we are constantly faced with newspaper headlines about its harmful effects. However, there is also the potential to both ameliorate theses harms and use the new abilities of AI to transform society for the good. Can you make the difference?
You could be a professional graphic designer and still make mistakes. There is always the possibility of human error. On the other hand if you’re not a designer, the chances of making some common graphic design mistakes are even higher. Because you don’t know what you don’t know. That’s where this blog comes in. To make your job easier and help you create better designs, we have put together a list of common graphic design mistakes that you need to avoid.
Between Filth and Fortune- Urban Cattle Foraging Realities by Devi S Nair, An...Mansi Shah
This study examines cattle rearing in urban and rural settings, focusing on milk production and consumption. By exploring a case in Ahmedabad, it highlights the challenges and processes in dairy farming across different environments, emphasising the need for sustainable practices and the essential role of milk in daily consumption.
1. Design Sprint
by Google Ventures
The sprint is a five-day
process for answering
critical business questions
through design, prototyping,
and testing ideas with
customers.
2. Why and Who?
Design Sprint
Why do it? Who is needed? Basic rules?
It's quick and in-expensive
way to learn about important
market problems or validate
new ideas
You create cross functional
team where every participant
feels attached to a problem
you all try to solve
It beats opinions as everybody
sees real response from the
real people
It encourages team work -
everyone could see the value
of others so as struggles they
have
A facilitator
A designer
A CEO (could be
anybody with a real
decision power)
A product manager
A user expert
An Engineer
A Marketer
Anybody else who’s
interested
5 day process
Set the stage
1 day: Unpack the problem
2 day: First sketches
3 day: Decide
4 day: Prototype
5 day: Test with real people
Main objective is to get an
actionable solution out of the
sprint
3. Unpack
the
problem
Sketch
the
solutions
Decide
on
solution
Prototype
the
solution
Test the
solution
Dig into problem
Everybody brings
all data they can
find on the
problem
Outcome
of the day
Everybody
knows everything
about the problem
Sketch as many
solutions as
possible
Draw, mind map,
note, storyboard,
crazy 8
Outcome
of the day
Tons of
solution sketches
Decide on best
solution(s)
"Best shot" or
"Battle Royal"
Outcome
of the day
One or
few best solutions
Prototype
All should
contribute
Outcome
of the day
Prototype
Test with real
people
People not from
your company
Entire team
watches and take
notes
Outcome
of the day
Knowledge
4. Unpack
the
problem
Exercises
Outcome
of the day
Everybody
knows everything
about the problem
Business opportunity: The CEO or product leader should walk
the sprint team through the business opportunity and market.
Lightning demos: Look at competitors’ products, look at non-
competitive products that solve a similar kind of problem in a
different market.
Lay it out: Print out all the important screens in your product, lay
it out, and walk through it as a user would.
Success metrics: How will you measure the success of this
design?
Existing research: whatever data you do know about your
customers.
Team interviews: go around interviewing people at the
company who have specific expertise.
Analytics: Look at any data you have.
Do
Note everything
"How might we"
format
Draw pictures
SKETCH THE
MOST
IMPORTANT USER
STORY
Source
5. Exercises
Choose part of the problem: Everybody focus on the same part
of the problem. Faster cycles.
Notes: If not already, capture all ideas in notes.
Mind map: Mix up ideas and notes to create a structured "cheat
sheet" for later UI sketches.
"Crazy 8": Everybody takes a sheet of paper, folds it in half 4
times. Draw 8 sketches on each panel.
Storyboard: Everybody sketch an actual UI. Work independently
or in groups, share anonymously.
Silent critique: Everybody looks at different storyboards and put
a sticker on every idea or part of the idea that they like. No limit
on amount of stickers.
Three-minute critique: Each person speaks about each
storyboard. First what they liked, then if something is missing.
Most popular ideas do not need explanation.
Do
Paper first
Work individually
or in groups
Sticky note
"Super Vote" if
needed
Source
Sketch
the
solutions
Outcome
of the day
Tons of
solution sketches
5 min
15 min
5 min
20 min
10 min
3 min/idea
6. Exercises
Search for conflicts: Two or more approaches to solve the
same problem. Each conflict is a gold mine.
"Best shot" or "Battle Royale": Either choose one, best solution
to test ("Best shot") or, if not possible, select few best solutions
for the "Battle royale" - test them all.
Test your assumptions: Write down all your major
assumptions and the ways you will validate them.
Whiteboard the user story: Draw final storyboard that will be a
spec for your prototype. Get one person to draw, but others
should help.
Do
Combat the group
effect
Make decisions
(don't hide behind
"Battle royal")
Source
Decide
on
solution
Outcome
of the day
One or
few best solutions
7. Exercises
Make it minimally real: Prototype does not need to be pixel
perfect. It needs to be believable.
Write real text: Forget "lorem ipsum". Use real text, made it up.
Prototyping tools vs code: Use tools that will allow you to
create a prototype in a shortest time possible.
Divide and conquer: Everybody should be able to help with
prototype creation. Divide work.
Build an asset library: Build a template slide deck. Include
anything that everyone will need — screenshots, user avatars,
logos, formatted text; whatever you think might help.
Review with an outsider: Schedule 30 minutes with someone
who is not doing design work today. The outside eyes will help
prevent you from going too far down any groupthink rabbit
holes.
Do
Keynote
(PowerPoint) are
the best
prototyping tools
Appoint an email
sheriff
Pointers, text,
browser bar and
other final
touches
Source
Prototype
the
solution
Outcome
of the day
Prototype
8. Exercises
List your key questions: The interviewer and the observers
should make a list of the key questions for the day.
Set up the observation room: Everybody who participated in
the sprint should be in the room. There’s no substitute for
watching real humans use your product, and this is a golden
opportunity to do it!
Every observer takes notes: Everybody should take notes on
things they see during the interviews: good, bad, and other.
Insist on paper note-taking — it’s best to keep laptops closed,
lest you lose your fellow observers to email..
Make a scoreboard: Clear one big whiteboard to collect the
group’s notes. Make a column for each participant and a row for
each part of the interview (e.g. background, first prototype,
second prototype, etc).
“Things that work” and “Problems to solve”: These are your
top-line findings. The CEO or decider for the project should
bless that list before you leave the room.
Do
Don’t diss the
user
Designate a court
reporter
Next sprint, it will
be easier
Source
Test the
solution
Outcome
of the day
Knowledge
9. Design Sprint
War chest
Remember Ingridients
PICK A BIG FIGHT
GET THE RIGHT PEOPLE
SCHEDULE THE USER STUDY
BEFORE YOU HAVE ANYTHING
TO TEST
Sticky notes
Drawing pens
Whiteboards
Whiteboard markers
Dot stickers
Blank copy paper
Time Timer Clock
Snacks
Sticky stuff
10. Resources that were used to create this info deck
How To Conduct Your Own Google Ventures Design
Sprint
The 6 Ingredients You Need To Run A Design Sprint
Lean more about the Design Sprint
The Design Sprint
www.test-n-tell.com