
Explore Google's five-day design sprint to rapidly develop a prototype and test it with users, using mapping, sketching, and brainstorming to decide on a single MVP-driven solution.
Identify the right moments to run a design sprint by applying it to new product ideas, big features, hackathons, team offsites, and cross‑company collaborations, all within a five‑day framework.
Design sprint roles mirror agile scrum: a decider (product owner), a scrum master facilitator, and a team of developers, designers, qa engineers, and managers.
Examine pros and cons of design sprint, including gathering insights, framing the problem for a customer segment, and delivering a tested prototype within a week to assess product market fit.
Adopt a product manager perspective by running a five-day design sprint with stakeholders in one room, delivering a universal, agreed MVP and minimizing context switching.
Decide the design sprint topic, gather research and numbers to brief the team, and prepare a PowerPoint with competitor analysis and sticky notes.
Align participants on the day one problem, goals, agenda, and hybrid rules, then review research and competitors with swot to frame a first user story using the heart framework.
Apply the H.E.A.R.T framework to evaluate user experience with five metrics—happiness, engagement, adoption, retention, and task success—using a goal-signal-metrics matrix to measure impact.
Day two focuses on ideation, where diverse teams brainstorm numerous solutions using techniques like crazy eights and translate top ideas into user journey storyboards.
Vote on leading storyboards, apply sanity checks against problem and vision, then narrow to one prototype storyboard; document assumptions and design principles, refine with experts, and organize teams for development.
Decide who builds the prototype—interactive, mock-up, or MVP—then demo it within the five-day sprint to test assumptions, validate problem solving, and remember it's not an MVP.
On day five, the final day of the design sprint, researchers observe testers using the prototype, gather feedback with open-ended questions, and consolidate findings on sticky notes before presenting.
Decide the next steps for your verified prototype within the design sprint by creating an epic, ordering a second sprint, or pursuing additional exploration, using PR templates for backlog-ready notes.
Run your own design sprint to prototype a product in five days, selecting projects like elderly-friendly smartphones, smart trash cans, or automated birthday wishes, with collaborative teams.
Learn to run a design sprint to create a great product prototype in five days, understand its benefits, drawbacks, and roles, and contribute to others’ work via the Discord community.
Use the SWAT technique (strengths, weaknesses, opportunities, threats) to populate four boxes, guiding product decisions, focus, and brainstorming across the lifecycle.
Design and validate product hypotheses using a minimum viable product that's scoped to test ideas, gather user feedback, and measure metrics with stakeholders.
Explore the spectrum of MVP types, from demo and Wizard of Oz MVP to dummy and ROV, and weigh the effort and data for landing page, poll, and crowdfunding MVPs.
Create a clear PRD task document to communicate goals to developers, linking designs, defining epic and tasks, and detailing requirements, testing, and failure handling.
Hi, I'm Dr Bart, Senior Product Manager at Microsoft, working in the Skype team and I'd like to be your Design Sprint/Product Management teacher!
Every great product starts with an idea. However, you don't know whether you found something that will ultimately be successful. How to make sure you can quickly validate any Product pitch?
Enter, Google designed framework: Design Sprint! This is a methodology that will help you in deciding, building, and testing a Product Prototype in just 5 days! This will work for any new Product, feature, or simply Product increment. Using this framework you will be able to get something tangible and testable in a very short amount of time.
With this, you will be able to save time and resources by not pursuing bad ideas or quickly obtaining data that you are on the right track to developing something great! You will be able to make a very educated call with the full support of all key stakeholders, that you will hopefully invite to this very special sprint.
With this course you will learn:
What a Design Sprint is
How to prepare for it
How to correctly run it
Who should participate
What are the pros and cons of this framework
What each of the Design Sprint days will bring
How to do to get the best out of each of those days
How to spark creativity in the participants
What is a HEART (H.E.A.R.T.) framework
...and many more!
With this course, you will easily be able to run a very successful, dynamic, and engaging design sprint!
Looking forward to seeing you in class :)