Design sprint
•Download as PPTX, PDF•
2 likes•309 views
A Design sprint is a time-constrained, five-phase process that uses design thinking to reduce the risk when bringing a new product, service or a feature to the market.
Report
Share
Report
Share
Recommended
POSSIBLE product design sprint
The document describes a Product Design Sprint, which is a 5-phase exercise that uses design thinking to reduce risks in bringing products to market. The 5 phases are: Day 1) understand the design problem through research; Day 2) diverge and develop solutions; Day 3) decide on the best ideas; Day 4) prototype a quick solution; Day 5) validate the prototype with users outside the company. The goal of the Sprint is to quickly build something when a lot is unknown in order to find product/market fit and reduce risks before fully developing or releasing a product.
Design sprint slideshare
A design sprint is simply a structured brainstorm based on design thinking, agile development and gamestorming.
Design Sprint
The document discusses the design sprint process, which involves prototyping, validating, and learning over the course of a week to address an idea. On Monday, the team unpacks the problem by creating user stories and scoping it. On Tuesday, they sketch and take notes to generate ideas. Wednesday involves deciding on a path by critiquing ideas. On Thursday, the team focuses on prototyping the minimal viable product. Finally, on Friday, they validate the prototype by observing users and gathering feedback to learn what works and what needs improvement.
How to Run a Design Sprint
So you've ready the Sprint book (or heard about Google Design Sprints) but you're trying to figure out how to actually do that? We'll give you a quick overview along with our tips (note this is much better in person, so reach out if you'd like us to come give a talk).
Insight : Design Sprint - Google Business Group Bandung
Discover more to learn detail with google design sprint, great tools to maximize and validate your idea with lack of creativity and enhancing collaboration.
Mobile Day - Design sprint
The document describes a design sprint workshop for improving the way international travelers exchange local and foreign currency. It discusses the design sprint process, which includes understanding user needs through research and interviews, defining the problem, diverging through brainstorming, converging on ideas through voting and prioritization, prototyping top concepts, and validating solutions. The workshop participants will experience a design sprint by designing an Android app for exchanging currency, with deliverables of sketches and user flows. The sprint follows typical stages - understand, define, diverge, converge, prototype, and validate - to collaboratively and quickly design user-centered solutions.
Product Design Sprint
This document outlines the steps of a Product Design Sprint (PDS) methodology for developing new product ideas. The PDS involves gathering a cross-functional team, understanding user needs, rapidly generating concepts, deciding on a solution to prototype, testing prototypes with users, and iterating the design based on feedback. Key aspects of the PDS include constraining the problem scope, diverging and converging on ideas, creating low-fidelity prototypes, and running multiple short cycles of prototyping and user testing to quickly refine the design. The goal of the PDS is to compress the design process through rapid iteration and validation with end users.
Design sprint info deck
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.
Recommended
POSSIBLE product design sprint
The document describes a Product Design Sprint, which is a 5-phase exercise that uses design thinking to reduce risks in bringing products to market. The 5 phases are: Day 1) understand the design problem through research; Day 2) diverge and develop solutions; Day 3) decide on the best ideas; Day 4) prototype a quick solution; Day 5) validate the prototype with users outside the company. The goal of the Sprint is to quickly build something when a lot is unknown in order to find product/market fit and reduce risks before fully developing or releasing a product.
Design sprint slideshare
A design sprint is simply a structured brainstorm based on design thinking, agile development and gamestorming.
Design Sprint
The document discusses the design sprint process, which involves prototyping, validating, and learning over the course of a week to address an idea. On Monday, the team unpacks the problem by creating user stories and scoping it. On Tuesday, they sketch and take notes to generate ideas. Wednesday involves deciding on a path by critiquing ideas. On Thursday, the team focuses on prototyping the minimal viable product. Finally, on Friday, they validate the prototype by observing users and gathering feedback to learn what works and what needs improvement.
How to Run a Design Sprint
So you've ready the Sprint book (or heard about Google Design Sprints) but you're trying to figure out how to actually do that? We'll give you a quick overview along with our tips (note this is much better in person, so reach out if you'd like us to come give a talk).
Insight : Design Sprint - Google Business Group Bandung
Discover more to learn detail with google design sprint, great tools to maximize and validate your idea with lack of creativity and enhancing collaboration.
Mobile Day - Design sprint
The document describes a design sprint workshop for improving the way international travelers exchange local and foreign currency. It discusses the design sprint process, which includes understanding user needs through research and interviews, defining the problem, diverging through brainstorming, converging on ideas through voting and prioritization, prototyping top concepts, and validating solutions. The workshop participants will experience a design sprint by designing an Android app for exchanging currency, with deliverables of sketches and user flows. The sprint follows typical stages - understand, define, diverge, converge, prototype, and validate - to collaboratively and quickly design user-centered solutions.
Product Design Sprint
This document outlines the steps of a Product Design Sprint (PDS) methodology for developing new product ideas. The PDS involves gathering a cross-functional team, understanding user needs, rapidly generating concepts, deciding on a solution to prototype, testing prototypes with users, and iterating the design based on feedback. Key aspects of the PDS include constraining the problem scope, diverging and converging on ideas, creating low-fidelity prototypes, and running multiple short cycles of prototyping and user testing to quickly refine the design. The goal of the PDS is to compress the design process through rapid iteration and validation with end users.
Design sprint info deck
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.
Intro to design sprint
The 5-day Design Sprint process provides teams a structured approach to answering critical business questions. In the first day, teams map out the challenge by defining a long-term goal and target audience. On the second day, teams sketch rapid ideas and variations. The third day has teams vote on the best ideas to prototype. A prototype is created on the fourth day for user testing on the fifth day. This process gives teams a fast way to learn from users without fully building and launching a product.
Preparing for 1st Design Sprint
It used to take companies weeks to brainstorm, write specs, publish RFPs, and get started on projects. With a design sprint, it’s possible to accomplish all that—plus sketching, prototyping, and validating big ideas—in just 5 days.
Sound too good to be true? We partnered with InVision to help teams learn how exactly to run their own design sprint. Follow these tips and by the end of your sprint, you’ll have live, targeted customer validation so you know exactly what to prioritize in your product roadmap.
Design 'super' sprint
The document describes the design sprint process, which involves mapping challenges, sketching solutions, deciding on solutions to prototype, storyboarding the selected solution, prototyping it, and testing the prototype. The process is intended to help teams quickly generate, refine, and test ideas to address challenges in a focused, time-boxed format over the course of a few days.
Google Design sprint
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.
2-Hour Design Sprint Agenda
We presented this as part of our UXSTRAT 2018 workshop as a way to introduce Design Sprints to your organization.
Google Design Spint Fundamental Guide
A complete guide including learnings on how to give Google Design Sprints. Learnings based on several executed Google Design Sprints.
The Design Sprint: A Fast Start to Creating Digital Products People Want
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.
Design sprint
A design sprint is a 5-phase framework that helps teams answer critical business questions through rapid prototyping and user testing. The phases are: Map (understand the problem), Sketch (generate ideas), Decide (select the best concept), Prototype (build something testable), and Test (get user feedback). This process helps spark innovation, encourage user-centered design, align teams, and launch products faster. A key benefit is that it provides validated direction and user input to inform product development. Design sprints are best for when a team needs clarity on a new opportunity or is stuck on an issue.
Demystifying the Design Sprint
A Design Sprint is a five-day framework that uses design thinking principles to identify the right problem to solve, generate ideas to solve that problem, and test solutions. The five days consist of understand, diverge, converge, build, and test phases to discover answers fast through prototyping and user feedback. This process aims to increase the chances of creating something people want by gathering evidence-based insights rather than opinions.
Insight & Solving Design Problem with Design Sprint Method
On this presentation contains some insight from google design sprint. Try to do some design sprint for your projects or products, it's cool really. You can share this presentation to anyone you like.
This slide was presented in Google Business Group Meet up at Dicoding Space, Bandung.
Design sprint - What is it and how it works
The Design Sprint is a technique developed in Google Ventures to answer critical business questions in five days. You will understand the process of the technique and learn how it works.
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
The document compares Design Sprint 1.0 and 3.0, which are processes for solving problems and launching new products. Design Sprint 1.0 is a 5-phase process useful for startups to reduce risks when launching new products, while Design Sprint 3.0 is a 6-phase process for enterprises to solve complex business and customer problems. The key differences are that 3.0 includes an additional problem framing phase, involves stakeholders earlier, and aims to gain alignment on core business opportunities.
Product Design Sprint
A design sprint is a five-day process for taking a product or feature from design through prototyping and testing. It involves five steps: understand, diverge, decide, prototype, and validate. The goal is to get early feedback on ideas by conducting user research, rapidly generating concepts, building quick prototypes, and testing them with real users to learn what works and what doesn't work.
Infographic: How do you know if a Design Sprint is right for you?
The most common goal of a Design Sprint is to assess an opportunity and reduce the risk of failure. That sounds great in the abstract, but what does this really mean in practice? When and for what challenges one use a Design Sprint? This infographic walks you through a process to determine if a Design Sprint is appropriate for your organization or challenge.
Innovations Accelerated - Design Sprint
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
Design Sprint Methods
The document describes methods for conducting a design sprint, which is a framework for teams to solve design problems in 2-5 days. It discusses the typical stages of a design sprint: understand the problem, define strategies, diverge ideas, decide on ideas, prototype the selected ideas, and validate them with users. It provides examples of specific methods that can be used at each stage, such as conducting user interviews and lightning talks in the understand stage, creating user journeys and defining design principles in the define stage, and testing prototypes with users in the validate stage. The document is intended to help teams plan and facilitate effective design sprints.
Design Sprint Workshop UXLx 2017
The document describes the Design Sprint process, which is a time-boxed framework for solving problems through understanding, diverging, building, and testing solutions over the course of a sprint. It provides examples of exercises used in each phase, such as empathy mapping to understand users, storyboarding and prototyping to generate and refine ideas, and assumption mapping to test prototypes and gather feedback. The goal is to increase the chances of creating solutions that people want by involving the team in collaborative problem solving and rapid iteration.
Design Sprint for Creative Teams
Slides from a 3-hour workshop that's intended to teach the principles of Design Sprints. It is NOT a complete design sprint. Certain exercises have been highlighted while others skipped in the interest of expediency.
Design Sprint Workshop
Southwest Airlines has hired the design team to improve the passenger experience at Boston Logan Airport from arrival to departure. On the first day, the team conducted assumption storming and empathy mapping to understand passenger pain points. They defined the problem as making passengers happy during their pre-flight experience. On day two, the team generated ideas through job stories and six-ups. On day three, they converged on ideas through sketching and $100 testing. Day four involved prototyping the selected idea. On the final day, the team tested their prototype with passengers and analyzed the results.
Design Sprint Case in Trend Micro
The document describes the process of a Design Sprint, which is a 5-day process for validating new product ideas. It involves gathering user insights, generating ideas, building prototypes, and testing with users. The document then shares an example of running a Design Sprint at Trend Micro to explore solutions for 4 predefined challenges within the constraints of being a mobile solution and having limited development resources and experts' time. It outlines the activities for each day, including defining challenges, brainstorming solutions, prototyping the top idea, and testing with users.
Running Effective Design Sprints
Delivered during 500 Startups' Design Quicky event on the 20th of February 2016 in Bangalore, India.
UX Kitchen Pitch Phase - Covid 19 Challenge
This document outlines an agenda for a UX Kitchen webinar on designing solutions for COVID-19. It includes sections for team introductions, defining the problem statement, presenting the solution statement, summarizing research findings, demonstrating solution prototypes, describing the target audience and impact, and reviewing implementation plans and timelines. Attendees are encouraged to book pitch mentorship sessions and submit slide decks by the deadline. The webinar will feature 5-minute pitches from teams walking through their problem-solving process and proposed solutions.
More Related Content
What's hot
Intro to design sprint
The 5-day Design Sprint process provides teams a structured approach to answering critical business questions. In the first day, teams map out the challenge by defining a long-term goal and target audience. On the second day, teams sketch rapid ideas and variations. The third day has teams vote on the best ideas to prototype. A prototype is created on the fourth day for user testing on the fifth day. This process gives teams a fast way to learn from users without fully building and launching a product.
Preparing for 1st Design Sprint
It used to take companies weeks to brainstorm, write specs, publish RFPs, and get started on projects. With a design sprint, it’s possible to accomplish all that—plus sketching, prototyping, and validating big ideas—in just 5 days.
Sound too good to be true? We partnered with InVision to help teams learn how exactly to run their own design sprint. Follow these tips and by the end of your sprint, you’ll have live, targeted customer validation so you know exactly what to prioritize in your product roadmap.
Design 'super' sprint
The document describes the design sprint process, which involves mapping challenges, sketching solutions, deciding on solutions to prototype, storyboarding the selected solution, prototyping it, and testing the prototype. The process is intended to help teams quickly generate, refine, and test ideas to address challenges in a focused, time-boxed format over the course of a few days.
Google Design sprint
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.
2-Hour Design Sprint Agenda
We presented this as part of our UXSTRAT 2018 workshop as a way to introduce Design Sprints to your organization.
Google Design Spint Fundamental Guide
A complete guide including learnings on how to give Google Design Sprints. Learnings based on several executed Google Design Sprints.
The Design Sprint: A Fast Start to Creating Digital Products People Want
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.
Design sprint
A design sprint is a 5-phase framework that helps teams answer critical business questions through rapid prototyping and user testing. The phases are: Map (understand the problem), Sketch (generate ideas), Decide (select the best concept), Prototype (build something testable), and Test (get user feedback). This process helps spark innovation, encourage user-centered design, align teams, and launch products faster. A key benefit is that it provides validated direction and user input to inform product development. Design sprints are best for when a team needs clarity on a new opportunity or is stuck on an issue.
Demystifying the Design Sprint
A Design Sprint is a five-day framework that uses design thinking principles to identify the right problem to solve, generate ideas to solve that problem, and test solutions. The five days consist of understand, diverge, converge, build, and test phases to discover answers fast through prototyping and user feedback. This process aims to increase the chances of creating something people want by gathering evidence-based insights rather than opinions.
Insight & Solving Design Problem with Design Sprint Method
On this presentation contains some insight from google design sprint. Try to do some design sprint for your projects or products, it's cool really. You can share this presentation to anyone you like.
This slide was presented in Google Business Group Meet up at Dicoding Space, Bandung.
Design sprint - What is it and how it works
The Design Sprint is a technique developed in Google Ventures to answer critical business questions in five days. You will understand the process of the technique and learn how it works.
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
The document compares Design Sprint 1.0 and 3.0, which are processes for solving problems and launching new products. Design Sprint 1.0 is a 5-phase process useful for startups to reduce risks when launching new products, while Design Sprint 3.0 is a 6-phase process for enterprises to solve complex business and customer problems. The key differences are that 3.0 includes an additional problem framing phase, involves stakeholders earlier, and aims to gain alignment on core business opportunities.
Product Design Sprint
A design sprint is a five-day process for taking a product or feature from design through prototyping and testing. It involves five steps: understand, diverge, decide, prototype, and validate. The goal is to get early feedback on ideas by conducting user research, rapidly generating concepts, building quick prototypes, and testing them with real users to learn what works and what doesn't work.
Infographic: How do you know if a Design Sprint is right for you?
The most common goal of a Design Sprint is to assess an opportunity and reduce the risk of failure. That sounds great in the abstract, but what does this really mean in practice? When and for what challenges one use a Design Sprint? This infographic walks you through a process to determine if a Design Sprint is appropriate for your organization or challenge.
Innovations Accelerated - Design Sprint
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
Design Sprint Methods
The document describes methods for conducting a design sprint, which is a framework for teams to solve design problems in 2-5 days. It discusses the typical stages of a design sprint: understand the problem, define strategies, diverge ideas, decide on ideas, prototype the selected ideas, and validate them with users. It provides examples of specific methods that can be used at each stage, such as conducting user interviews and lightning talks in the understand stage, creating user journeys and defining design principles in the define stage, and testing prototypes with users in the validate stage. The document is intended to help teams plan and facilitate effective design sprints.
Design Sprint Workshop UXLx 2017
The document describes the Design Sprint process, which is a time-boxed framework for solving problems through understanding, diverging, building, and testing solutions over the course of a sprint. It provides examples of exercises used in each phase, such as empathy mapping to understand users, storyboarding and prototyping to generate and refine ideas, and assumption mapping to test prototypes and gather feedback. The goal is to increase the chances of creating solutions that people want by involving the team in collaborative problem solving and rapid iteration.
Design Sprint for Creative Teams
Slides from a 3-hour workshop that's intended to teach the principles of Design Sprints. It is NOT a complete design sprint. Certain exercises have been highlighted while others skipped in the interest of expediency.
Design Sprint Workshop
Southwest Airlines has hired the design team to improve the passenger experience at Boston Logan Airport from arrival to departure. On the first day, the team conducted assumption storming and empathy mapping to understand passenger pain points. They defined the problem as making passengers happy during their pre-flight experience. On day two, the team generated ideas through job stories and six-ups. On day three, they converged on ideas through sketching and $100 testing. Day four involved prototyping the selected idea. On the final day, the team tested their prototype with passengers and analyzed the results.
Design Sprint Case in Trend Micro
The document describes the process of a Design Sprint, which is a 5-day process for validating new product ideas. It involves gathering user insights, generating ideas, building prototypes, and testing with users. The document then shares an example of running a Design Sprint at Trend Micro to explore solutions for 4 predefined challenges within the constraints of being a mobile solution and having limited development resources and experts' time. It outlines the activities for each day, including defining challenges, brainstorming solutions, prototyping the top idea, and testing with users.
What's hot (20)
The Design Sprint: A Fast Start to Creating Digital Products People Want
The Design Sprint: A Fast Start to Creating Digital Products People Want
Insight & Solving Design Problem with Design Sprint Method
Insight & Solving Design Problem with Design Sprint Method
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
Infographic: How do you know if a Design Sprint is right for you?
Infographic: How do you know if a Design Sprint is right for you?
Similar to Design sprint
Running Effective Design Sprints
Delivered during 500 Startups' Design Quicky event on the 20th of February 2016 in Bangalore, India.
UX Kitchen Pitch Phase - Covid 19 Challenge
This document outlines an agenda for a UX Kitchen webinar on designing solutions for COVID-19. It includes sections for team introductions, defining the problem statement, presenting the solution statement, summarizing research findings, demonstrating solution prototypes, describing the target audience and impact, and reviewing implementation plans and timelines. Attendees are encouraged to book pitch mentorship sessions and submit slide decks by the deadline. The webinar will feature 5-minute pitches from teams walking through their problem-solving process and proposed solutions.
Ways for UX Design Iterations: Innovate Faster & Better
Any stage of the design process, even post the product release is scrutinized for any improvements. The iterative design process is of great help in such a scenario. It's important to keep in mind, though, that iterative design will be more cost-effective the earlier it is used in a product's lifespan.
Guide to Design Sprint
A design sprint is a five-phase framework that helps answer critical business questions through rapid prototyping and user testing. Sprints let your team reach clearly defined goals and deliverables and gain key learnings, quickly. The process helps spark innovation, encourage user-centered thinking, align your team under a shared vision, and get you to product launch faster.
Execute Idea
The document describes the Design Sprint methodology, which aims to build and test prototypes in just five days to quickly validate hypotheses about customer needs and preferences. It involves six phases: Understand to create a shared knowledge base; Define success metrics and principles; Sketch a range of ideas individually; Decide on a direction to prototype; Prototype the concept; and Validate the prototype with users. Various methods are provided for each phase, such as affinity mapping, card sorting, crazy 8's, dot voting, and usability studies. The timeline allocates one day for each phase with the goal of compressing months of work into a single week to shortcut debate and quickly learn.
Design thinking
Design thinking is a creative problem-solving process that involves empathizing with users, defining problems from a human-centered perspective, generating creative ideas, building prototypes, and rigorously testing solutions. It is an iterative process comprised of five stages - empathize, define, ideate, prototype, and test - that allow designers to gain an understanding of users and their needs in order to design effective solutions. The stages do not always occur sequentially and can be repeated as understanding improves. Overall, design thinking provides a systematic approach to innovation focused on the needs of users.
趨勢科技案例分享 - 與專家一起共舞 Design Sprint
On 2019/03/27, I talked about one of my experience about how to facilitate a Design Sprint Workshop in Trend Micro.
Design studio: A team alignment secret weapon - Modev MVP Conference
Design studio: A team alignment secret weapon - Modev MVP Conference
We all want the best user experience, but often other priorities get in the way: “Bob from Marketing wants it to…”, “The developers don’t like that approach...”, “That feature is a ‘nice to have’”.
What if you had a tool that can help folks sharpen their UX skills, get them prioritizing the users and their goals, and align everyone on a common vision that revolves around a great user experience?
This hands-on tutorial will walk you through a design studio and how it can be a great tool to align product owners, developers and UX teams on an approach that balances user and business needs. We’ll also show you how to conduct a “mini design studio” before an agile sprint.
You’ll gain hands-on experience with different aspects of running a design studio through individual and group exercises throughout the tutorial.
John Whalen (CEO at Brilliant Experience):
John Whalen has a PhD in Cognitive Science with over 15 years of User-Centered Design experience. He currently leads Brilliant Experience – a consultancy that supports intra- and entrepreneurs to ensure the success of mission-critical innovation projects by using our unique blend of user-centered design, psychology, design thinking and lean startup techniques.
John’s specialty is to provide businesses with competitive advantages using a mix of user research insights and expert knowledge of human vision, attention and memory. He has experience (and great stories to tell from) working with Fortune 500 clients in the ecommerce, financial, healthcare and government verticals. John’s currently focusing on helping large enterprises integrate brain science into agile, design thinking, and UCD projects.
How to run a remote design sprint
Design sprints can accelerate decision-making and development of your product or service. Remote design sprints are largely untried but we have found that it is still possible to conduct one virtually, using the right tools.
This guide outlines all of the steps involved in setting up and running a remote design sprint, detailing what is involved or required for each step as well as tips for optimising your sprint.
Ideation webinar
This document summarizes the key points from a session on the ideation phase of a design challenge focused on Covid-19. It outlines the main activities of the ideation phase, including developing value propositions with insight statements and "How Might We" questions, solution brainstorming, creating a user journey map, developing a communication strategy, and sketching and prototyping ideas. It also lists deliverables for each activity and provides example resources and collaboration tools.
Design Thinking: Ideation Techniques
Ideation is at the heart of the Design Thinking process. Ideation sessions help you to challenge assumptions, think outside the box, and explore uncharted territory. In the ideation phase, you explore and come up with as many ideas as possible.
In this presentation guide, you will learn and develop skills in six types of ideation techniques that can be used in the Design Thinking cycle. They include:
1. Brainstorming
2. 2 x 2 Matrix
3. Dot Voting
4. 6-3-5 Method (Brainwriting)
5. Special Brainstorming (Negative Brainstorming, Figuring Storming, and Bodystorming)
6. NABC (Need, Approach, Benefit and Competition)
This guide provides a means to introduce ideation techniques to your workshop participants other than the traditional brainstorming method. It helps to make your ideation sessions fun and exciting.
LEARNING OBJECTIVES
1. Gain knowledge on the various ideation techniques that can be used in the design thinking cycle.
2. Develop skills in the application of ideation techniques.
3. Understand the expert tips and key learnings of ideation techniques.
CONTENTS
1. Brainstorming
2. 2 x 2 Matrix
3. Dot Voting
4. 6-3-5 Method
5. Special Brainstorming
6. NABC
To download this complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations
Design for Covid-19 Challenge Webinar 2: Ideation Phase
This is our second webinar from Design for Covid-19 Challenge. Our focus for this webinar is on the Ideation Phase. It provides participants with frame works and tools on how to create a solution.
Design Process
The document outlines the steps of the engineering design process which includes identifying needs or problems, researching potential solutions, developing possible solutions, selecting the best solution, constructing prototypes, testing and evolving the design, communicating the solution, and redesigning if needed. Some key steps involve examining current solutions to the problem, brainstorming ideas, creating tests for prototypes, and documenting results for manufacturing. The overall process is meant to develop consistent, high quality and safe engineered products and systems.
The Guide to Agile UX Design Sprint Playbook
Alex Gamble is a product designer at Price Waterhouse Coopers New Zealand. He has helped a variety of businesses, from small start-ups to big corporates, develop user-centred products. Alex’s goal is to bring forward a lean product revolution.
FINAL PROJECT STATUS and DESIGN THINKING PROCESS.pptx
FINAL ACTIVITIES STATUS / DESIGN THINKING PROCESS
Design thinking for delivery effectiveness v3.0
The presentation discusses how design thinking can improve delivery effectiveness and efficiency. It outlines the typical design thinking model and how various roles can use it. It also discusses perceptions of design thinking and challenges teams face in adopting it. The document provides details on how design thinking focuses on the user, business value, market relevance, and improvement opportunities. It provides guidance on identifying user personas, understanding needs, ideating solutions, and validating ideas through quick prototypes and user testing.
3 Day Structure
The document outlines a 3-day structure for a product design sprint. Day 1 focuses on understanding the problem through lightning talks, affinity mapping, and sketching ideas. Day 2 has teams decide on a solution through sketch presentations and storyboarding a prototype. Day 3 involves prototyping, user testing, and validating the proposed solutions through feedback. The sprint uses divergent and convergent thinking techniques to move from exploring the design space to agreeing on solutions to test.
Wearables - Design Sprint Playbook
The document provides an overview of how to run a design sprint to develop experiences for wearable devices like Glass and Android Wear. It describes the 5 stages of a design sprint: understand, diverge, decide, prototype, and validate. In the understand stage, participants learn design principles, define a design challenge, and create user personas. In diverge, participants individually brainstorm ideas and then collaborate as a team. They map out ideas based on value and difficulty. The overall goal is to generate innovative ideas for the user personas within a short time-bound process.
Agile and Design: creating and implementing products (in Italy) is possible
The wiseman says: "A company specialized in IT consultancy cannot make products."
If you decide to break this taboo, the road is only one: understanding how that product can be realized and working hard to make it.
This is the story of Indyco, a tool born merging an agile dev team and a lean design team. Teams that didn't know each other before. And they made Indyco real in 6 months.
We will share the simple but powerful principles that lead us up to the go-live.
Now we are measuring and collecting data for next step.
These slides have been presented at Better Software 2014.
Agile and Design: creating and implementing products (in Italy) is possible
This document discusses agile product development and design processes for startups. It outlines a methodology using scrum, minimum viable products (MVPs), and frequent user testing. A design sprint process is proposed involving analysis, sketching, prototyping, and fixing iterations. Close collaboration between designers and developers is emphasized to iteratively design, develop, and test the MVP within budget and timeline constraints. The goal is to rapidly iterate the product to address user needs and collect strategic data to guide further development.
Similar to Design sprint (20)
Ways for UX Design Iterations: Innovate Faster & Better
Ways for UX Design Iterations: Innovate Faster & Better
Design studio: A team alignment secret weapon - Modev MVP Conference
Design studio: A team alignment secret weapon - Modev MVP Conference
Design for Covid-19 Challenge Webinar 2: Ideation Phase
Design for Covid-19 Challenge Webinar 2: Ideation Phase
FINAL PROJECT STATUS and DESIGN THINKING PROCESS.pptx
FINAL PROJECT STATUS and DESIGN THINKING PROCESS.pptx
Agile and Design: creating and implementing products (in Italy) is possible
Agile and Design: creating and implementing products (in Italy) is possible
Agile and Design: creating and implementing products (in Italy) is possible
Agile and Design: creating and implementing products (in Italy) is possible
More from Jyaasa Technologies
Incident management with jira
Incident management in Jira focuses on short-term solutions to unplanned interruptions in systems or services. The Jira Service Desk template includes an incident workflow that guides users to log, diagnose, and resolve incidents. This process involves service members reporting issues, the service desk logging and categorizing incidents, prioritizing response, escalating if needed, resolving the underlying problem, verifying the fix, and closing the incident. Postmortem reports and incident response reports provide documentation and analysis after significant incidents.
Extreme programming practices ( xp )
Extreme programming, founded by Kent Beck one of the original signatories of Agile Manifesto is a lightweight agile methodology of agile software development and engineering .
The myth of 'real javascript developer'
The document repeats the same line "Jyaasa : We Design, Build and Develop Products" 20 times without providing any other context or information. It does not have a clear topic or message that can be summarized in 3 sentences or less.
Microservices
Microservices is an architectural style that structures an application as a collection of
loosely coupled services, which implement business capabilities.
Facade pattern in rails
The document discusses the facade pattern in Ruby on Rails applications. It describes the facade pattern as providing a unified interface to isolate complexity and hide subsystem interfaces. It then gives an example of using a facade pattern to simplify a chat room controller in Rails that was preparing a lot of data. A ChatRoomsFacade class is created that initializes the necessary data, allowing the controller to be simplified by just initializing the facade. The facade pattern hides complexity and provides a single interface, simplifying controllers in Rails especially for larger projects.
Scrum ceromonies
Scrum is an iterative and incremental agile software development framework for managing product development.
An introduction to bitcoin
a type of digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, operating independently of a central bank.
Tor network
Tor is free software that enables anonymous communication. It conceals a user's location and usage through a network of over 7,000 relays. Tor implements onion routing, which encrypts data including destination IP addresses and passes encrypted data through multiple relays, each decrypting a single layer to reveal only the next relay. This allows anonymously browsing the internet, protecting privacy and security such as from government surveillance disclosed by Edward Snowden.
Collective ownership in agile teams
What is collective code ownership in agile teams? what are its advantages? .What are the common pitfalls of it ?.
What would be the ways to implement into software development teams. If you would like to talk more on the topic feel free to email kapil@jyaasa.com
Push notification
This document discusses using Pusher for push notifications. Pusher allows sending push notifications from a backend server to user interfaces like mobile and desktop apps. It avoids problems with polling by using websockets for real-time notifications. The document explains how to set up Pusher by creating an account and app, and integrating it into server-side code using various languages like Ruby, and client-side code using JavaScript or React Native.
The Design Thinking Process
The document outlines the 5 key stages in the design thinking process: empathize, define, ideate, prototype, and test. It describes each stage in detail. Empathize involves understanding users through observation and interviews. Define brings clarity to the problem based on user needs. Ideate focuses on generating many creative solutions through brainstorming. Prototype creates artifacts to test possibilities. Test gets feedback from users to refine solutions and further learn about the user. The overall process is presented as human-centered, iterative, and solution-focused.
User story
This document discusses user stories, which are short descriptions of a desired new feature written from the perspective of users or customers. User stories should keep it simple and focus on who wants the feature, what they want to accomplish, and why. They are important because they provide precise yet spare information that is useful for planning and understandable to both technical and non-technical people.
Data Flow Diagram
A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and outputs. As its name indicates its focus is on the flow of information, where data comes from, where it goes and how it gets stored.
OKRs and Actions Overview
Objectives and Key Results (OKR) is a popular technique for setting and communicating goals and results in organizations. Its main goal is to connect company, team and personal objectives to measurable results, making people move together in right direction.
Vue.js
The document discusses using Vue.js to reduce complexity in web development. It introduces some key concepts in Vue.js like data binding with v-model, conditional rendering with v-if, listing data with v-for, handling events with v-on, and conditional rendering with v-if and v-show. It also provides examples of how to install Vue.js via npm, bower or CDN, and basic usage with el, data, methods. Towards the end, it mentions running a demo customer management app using Vue and Rails.
Active record in rails 5
The document discusses Active Record attributes in Rails 5. It explains that Active Record's detected attribute types can be overridden with the attribute method. The attribute method can also define a default value and specify if an attribute is an array or range. Attributes do not require a matching database column. Examples demonstrate overriding an attribute type from decimal to integer, setting default values, and defining array attributes.
Design Patern::Adaptor pattern
The adapter pattern is a software design pattern that allows the interface of an existing class to be used as another interface.
Association in rails
The document discusses various types of associations in Rails including belongs_to, has_one, has_many, has_many :through, has_one :through, has_and_belongs_to_many, and polymorphic associations. It provides examples of how to declare each association type in the model and how to set up the corresponding database migrations. It also covers choosing between different association types and using self-joins for models that associate with themselves.
Web design layout pattern
The document discusses visual hierarchy and layout patterns in web design. It describes the F-pattern and Z-pattern layouts. The F-pattern follows the shape of the letter F as users first scan horizontally across the top of the page from left to right. The Z-pattern aims to anticipate the user's needs by presenting key information like branding, calls-to-action, and structure up front. Both patterns aim to create a natural reading flow that guides users efficiently through content.
Command Pattern in Ruby
The command pattern is a behavioral design pattern in which an object is used to encapsulate all information needed to perform an action or trigger an event at a later time.
More from Jyaasa Technologies (20)
Recently uploaded
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Recently uploaded (20)
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
Design sprint
- 1. Design Sprint Stages of Design Sprint
- 3. Overview Design Sprint What? Why Stages of Design Sprint
- 4. Design Sprint : What is Design Sprint? ➢ Process that uses design thinking to reduce the risk when bringing a new product, service or a feature to the market
- 5. Design Sprint : When to use Design Sprint? ➢ Launching a new product or service ➢ Extending existing experience to new platform ➢ Injection of UI/UX design ➢ Adding new features to existing product
- 6. Stages of Design Sprint 1. Understand 2. Define 3. Diverge 4. Decide 5. Prototype 6. Validate
- 7. Stages of Design Sprint : Understand ➢ Clarity on the product, user’s needs (the market) and technical possibilities ➢ Three main things to keep in mind: ○ Business Goal ○ Engineers ○ Market (Perspective User)
- 8. Stages of Design Sprint : Define ➢ Finding a strategy and analyzing what is the best path to arrive at the solution ➢ Define product goal or features
- 9. Stages of Design Sprint : Diverge ➢ Everyone can think using their creativity for how to solve the problem ➢ The solution could be many ➢ Create solutions to design challenges ➢ Examples: Crazy 8’s , Sketch 8 ideas in 5minutes
- 10. Stages of Design Sprint : Decide ➢ Filtering down of multiple solutions created in diverge stage and choose the best one or combination of ideas ➢ Process: ○ Keep ideas open to everyone so that further discussion is made and then vote ○ Choose one solution
- 11. Stages of Design Sprint : Prototype ➢ Create and build mockups that you can actually test with the users ➢ Could be done with: ○ Paper Prototype ○ Physical Prototype
- 12. Stages of Design Sprint : Validate ➢ Take the users ➢ Let them play with the prototype ➢ Listen to them
- 13. Design Sprint : Advantage ➢ Opportunity for everyone to participate in decision making process ➢ Time constraint boosts creativity and forces you to make product decisions quickly ➢ Brings team members in a single page
- 14. THANK YOU!ANY QUERIES? LET’S DISCUSS