top of page



Get the answers you need for your product in one week

A design sprint is an industry proven process created by Google Ventures that helps you answer critical business questions through design, prototyping, and testing ideas with customers.


It incorporates business strategy, innovation, behavior science, and design thinking into an easy to use framework that any team can take advantage of.

The benefits of design sprints

One week. Incredible results.

save time.png

Save time & money

Don't waste resources on a product or

feature no one wants

stop endless.png

Stop endless debate

Let the evidence guide your team

learn quickly.png

Learn quickly & effectively

Shortcut the process to get the

answers you need

meaningful decisions.png

Make meaningful decisions

Gain confident in the choices you

make to grow your product

gather value.png

Gather valuable evidence

Reduce your risk with data to guide

your product growth

clear path.png

A clear path forward

Know what you need to do next

DAY 01

Understand & Define

What are the user needs, business needs, and technology capacities? What is the key strategy and focus? Where do we provide the most value?

  • 360 Lightning Talk

  • Competitive Overview

  • User Interview

  • Stakeholder Map

  • Summarize learning and first ideas

  • User Journeys

  • Design Principles

  • First Tweet

What we'll define:

  • The opportunity and theories the team has around the problem and solution

  • What perspective and perceptions our customers have about the problem

DAY 02

Diverge & Decide

How might we create a solution that would solve for what we know today?

  • Sketch 8 ideas

  • Sketch 1 idea

  • Sketch 1 Storyboard

  • Zen Voting

  • Team Review

  • Thinking Hats

What we'll decide:

  • What solution ideas does the team have?

  • What ideas will help us learn the most?

DAY 03


Create a prototype that makes our idea real and interactive so we can get feedback from real users.

  • Mock

  • Demo

  • User Interviews

  • Video

  • Physical Prototype

What we'll decide:

  • What is the right method for our testing?

  • What is the right level of fidelity for learning and building confidence?

DAY 04


Test the ideas with users, business stakeholders, and technical experts.

  • User Testing

  • Stakeholder Validation

  • Technical Feasibility Validation

What we'll learn:

  • What gaps or leaps of faith are we asking users to take in the proposed journey?

  • Where can we clarify through flow, expectations, and messaging?

DAY 05

Next Steps Report

Organizing feedback, identifying patterns, and using insights to shape the next steps for gaining clarity and confidence.

  • Mock

  • Demo

  • User Interviews

  • Video

  • Physical Prototype

What we'll learn:

  • What insights can be incorporated back into the team?

  • What do we want to continue testing or test more deeply?


We had a lot of ideas. Ideas all over the place. And once we started working with Agory team and their methodology, that really helped us start with the discussion around the business and the market as opposed to going straight to the technology and requirements.

Pete Cassani

Co-Founder, The Peasants

bottom of page