
Learn to validate your vision and ideas before big investments using a five-day agile sprint inspired by Jake Knapp, starting from the problem, building solutions, prototyping, and validating with users.
Identify a big challenge for the sprint, assemble a strong team, secure a location and supplies, and watch the video for exact requirements and attachments.
Form a seven-person sprint team with defined roles: designer, decider, finance, marketing, customer, logistics, and facilitator, to drive fast decisions and get feedback as soon as possible.
Choose diverse, committed team members for a design sprint, value constructive troublemakers and open-minded experimentation, embrace new ideas, expect no guaranteed results, and focus on solving user problems.
Prepare for the sprint by assembling supplies: whiteboards or magic charts, time timer, Sharpies, post-it notes, color markers, white paper, masking tape, and color coding to keep ideas visible.
Block the sprint day from 10:00 to 5:00 pm with six working hours, a lunch break, and a no devices policy to keep the workshop focused.
Kick off the sprint with an agenda, set a long-term goal, map the process, and interview experts to define the week's focus. End the week by reviewing feedback and learnings.
Facilitate sprint week by defining big long-term goals with sticky notes, voting with red dots to pick the focus, and drafting key questions to answer that connect to the goals.
Learn to transform expert interviews into positive how might we prompts during a sprint workshop, writing boldly on large post-its and mapping insights to uncover design problems.
Define the sprint target by mapping how might we ideas, then vote to focus on the single most important issue. Use Google Ventures to pick one or two sprint questions.
Remix and improve ideas, set a clear weekly target, and seek inspiration from past work and other industries. Each member sketches a solution on paper for later discussion.
Conduct focused lightning demos on Tuesday morning to gather information, compare approaches, and split large problems into micro steps; timebox each demo to three minutes and capture notes.
Apply five tips to create engaging lighting demos in sprints: stay open to ideas, prepare in advance, keep demos short, embrace team diversity, and avoid judging demos.
Discover the four steps of sketching in a sprint: take silent notes to own ideas, sketch quickly, run a Crazy Eights exercise, and present self-explanatory, colored sketches for rapid critique.
On Wednesday, teams make decisions as ideas take shape and the decider selects the reference sketch to anchor the prototype, while managing fatigue with hydration and healthy snacks.
On Wednesday morning, teams use anonymous sketches, an art museum layout, and heat map voting to reach a base prototype through a decider and a super vote.
Learn how to run a design sprint like an art museum by giving space to each sketch, keeping the center stage clear, and enforcing silence and order for clear collaboration.
Facilitate a dot-voting heat map by giving unlimited green and red dots to participants to mark what they like, what they really like, and what raises questions, without explanations.
The decider weighs two good prototypes, may pick one or merge parts into a winning sketch, while ensuring the decider is briefed on their options.
Explore how flawed storyboarding stalls sprint progress, emphasizing end-to-end prototype steps, diverse team collaboration, and balanced discussions to avoid burnout and deliver a clear, actionable storyboard.
Run a productive storyboard session by dividing the whiteboard into camps, sketching screens as frames, and mapping the user journey from beginning to end to guide rapid prototyping.
During the final storyboard iteration, collaborate to fill gaps, outline each scene, assign a scribe, and validate navigation from catalog to search and icons for a 15-minute prototype.
Design teams compare real versus fake prototypes to gather honest user feedback in one day, using a fast, believable prototype to elicit reactions without building a perfect product.
Learn to prototype the right way by selecting efficient prototyping tools, sketching a storyboard, and organizing makers, a writer, and an interviewer into a cohesive prototype.
Set up a sprint interview room with a big screen and a gathered team to observe; capture feedback with color-coded sticky notes and a facilitator guiding clarifications, avoiding mid-interview discussions.
Apply the five act user interview to observe authentic user reactions by welcoming participants, establishing comfort and consent to record, guiding questions, letting users act with scenarios, and debriefing afterward.
Capture and structure notes from user interviews on a shared whiteboard, organizing them into morning and afternoon sessions with categories, filters, and quick queries so debriefing stays fast and clear.
Wrap up the sprint by identifying patterns from user feedback, summarizing themes, and validating questions against the prototype, then set action items before team break up.
Wraps up a five-day sprint by mapping the process, gathering user insights, prototyping, making decisions, and using interview feedback to gain clarity about users.
Do you want to understand your clients?
Do you want to really know your clients and what they want?
DO you want to jump from idea to user testing without investing hundreds of thousands of dollars in design and implementation?
Do you want to learn how Google designs products?
Then The Design Sprint course is for you!
In this course I'll show the step by step, day by day process to build better products, just as Google, Slack, KLM and manu other do.
It is a 5 days process from Google Ventures that is ment to take a big challenge and get clarification on what the users expect. Throughout the 5 days you will understand, sketch, decide, prototype and validate your product features with your users.
This process is a combination between innovation, design thinking, business strategy, the science of client behaviour and many more.
Day 1 - Monday
set your long term goal
map your processes
ask the experts and learn from their issues
identify the problem
define your design sprint target
Day 2 - Tuesday
get inspired by lightning demo
sketch possible solutions
Day 3 - Wednesday
decide which sketch to use
storyboard your solution
Day 4 - Thursday
prototype the solution
Day 5 - Friday
user interviews
identify patterns
learn
Who do you need to participate at the Design Sprint?
you need maximum 7 people, more than that will be hard to manage and doesn't provide additional value.
Decider
Finance Expert
Marketing Expert
Customer Expert
Tech/logistics Expert
Design Expert