Skip to content
The Official 5-Day Design Sprint
  • Pages
    • The Official 5-Day Design Sprint
    • Set the stage
      • Sprint basics
      • Big challenge
      • Sprint team
      • Email Summary
    • Monday: Map
      • 1. Introductions
      • 2. Explain the sprint
      • 3. Long-term goal
      • 4. Sprint questions
      • 5. Map
      • 6. Lunch
      • 7. Ask the experts
      • 8. Target
    • Tuesday: Sketch
      • 1. Lightning demos
      • 2. Divide or swarm
      • 3. Sketch
        • Example
        • All Crazy 8's
        • All Solutions
      • 4. Begin recruiting
    • Wednesday: Decide
      • 1. Sticky decision
      • 2. Rumble
      • 3. Storyboard
    • Thursday: Prototype
      • icon picker
        1. Pick the right tools
      • 2. Divide and conquer
      • 3. Build the prototype
      • 4. Do a trial run
      • 5. Prepare for tomorrow
    • Friday: Test
      • 1. Interviews
      • 2. Take Notes
      • 3. Make a plan
The Official 5-Day Design Sprint
/
/
1. Pick the right tools
Share
Explore

1. Pick the right tools

Here's a cheat sheet for choosing the right tools.
Don’t use your everyday tools. Like in any sprint, your normal tools may not be right for building a realistic prototype in one day. You need tools that are easy for anyone to use (not just designers or engineers) and encourage you to make something that looks realistic (but avoid making it perfect).

App prototypes (and other digital products)

👉 Our pick:
Figma
⁠
— There are many (many!) great tools for prototyping digital products, but Figma is best for remote Design Sprints because it allows teams to work in parallel on the same document.
⁠
image.png
⁠
⁠
A few other Figma features we like:
It’s approachable for non-designers (especially if a designer creates a template)
During
Friday: Test
⁠
, you can simply use
Figma’s Prototype feature
⁠
to give your customers access (no extra tools required)
It works well on all devices and operating systems

Database and workflow prototypes

👉 Our pick:
Coda
⁠
— If your prototype needs to store data or run workflows, Coda is a great option. It starts as a simple document that can evolve to be as powerful as an app (like this doc!). Play around with a few of the features - they may come in handy as you are prototyping:
Forms to collect data
Tables to store data
Buttons and automations to run actions
Packs to connect with other tools like sending a text message in Twilio or syncing in a user’s Google Calendar.
Publishing to turn your doc into a website

Marketing prototypes

If you don’t know what to prototype, prototype the marketing. It’s a handy shortcut that allows you to test the concept, features, and value of your product or service without actually prototyping the product or service. (In
the book
⁠
, we call this the Brochure Façade, and we’ve used it in more than half of our Design Sprints. Even when the sprint wasn’t about capital-M “Marketing.”)
👉 Our pick:
Squarespace
⁠
— If you haven’t used Squarespace, warning, you might end up with five new websites you never knew you needed. It’s just that easy to get started. And once you’ve selected a template, your team can work in parallel on different pages of the website.
⁠

Which tools will you use to prototype?

Take a few notes here...

⁠
Next:
2. Divide and conquer
⁠
⁠
Gallery
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.