background

What is

Design Sprint?

Design Sprint is a five-day workshop dedicated to improving the process of rapid validation of design hypotheses. The main goal of the workshop is to optimize the decision-making process, without having to build the entire solution or product. It is the first stage of MVP development that will lead you to valuable conclusions and solid results.


Product design framework consists of five phases - each lasts one day. The first stage will be to understand the design problem and context. The next stages are the cognitive part, aimed at creating and choosing the most suitable solutions. The last part is validating the solution by presenting the prototype to target users.

01

day 1.

Understanding
of the design problem
  • Introduction
  • Aim
  • User analysis
  • Interview with IT experts
  • Problem definition
02

day 2.

Exchange
of Ideas
  • Competition analysis
  • Data collection
  • Crazy 8
  • Project sketch
03

day 3.

Decision
Making
  • First Voting
  • Projects discussion
  • Second Voting
  • Creating an action plan template
04

day 4.

Product Prototype Development
  • Building a prototype of the product
05

day 5.

Testing
procedure
  • Conducting prototype tests

An ideal project

team should
consist of:

  • CEO/Product Owner - a person responsible for making decisions on the client-side
  • Project Manager
  • UI designer, UX designer - a person responsible for product design
  • Software Engineer - most suitable will be an experienced backend developer who will bring in their expertise to the project
  • Customer Service - a person who has direct contact with the client
  • Marketing Manager - lead generation expert
  • Moderator

It’s important for the team to have a person with the power to make the final decision regarding the whole project. If it’s impossible for such a person to be always present at the meetings, they should participate in the daily project summaries. Also, the person can choose another team member responsible for making final decisions.

Day 1.

Understanding
of the design problem

Aim: Defining the goal and challenge of product design. Analyze the target user. Realize the risk associated with the project.

introduction:

  • Introduction – what are we here for?
  • Agenda overview – what’s the plan and today’s aim
  • Workshop flow - explaining the workshop scheme
  • Warm-up exercise - an exercise that will allow you to introduce yourself and tell about your role in the project
  • Review of collected data, ie:
    • Google Analytics
    • Research – marketing, main focuses, etc.
    • General data ie. on customer behavior, global trends, etc.
    • Satisfaction surveys, etc.
    • Customer complaints, information from the first line of contact with the customer

aim:

Establishing the aim, hypothesis, assumptions – at this stage, we set a clear and measurable goal that we want to achieve through workshops and problem solving.

user analysis:

  • Creating the product persona
  • Designing the UX maps

interview with IT experts:

  • Expert presentation,
  • A short summary of completed tasks,
  • Feedback regarding the created persona, hypothesis, UX maps
  • Time for Q&A

problem definition:

  • Defining the problem using sticky notes with questions starting with "How can we …"
  • Grouping problems (sticky notes questions) into a collection of related topics
  • Voting on the most important topics - after voting, we add selected problems to UX maps

day summary:

Answering the key points:

  • Is the goal measurable and achievable?
  • Did everyone understand the problem?
  • What was remembered?

Day 2.

Exchange of Ideas

Aim: Work out the team's attitude towards achieving a common goal. Preparing the first sketches.

introduction:

  • Agenda overview – what’s the plan and today’s aim,

competition analysis:

  • Everyone chooses a product/service/application or website to present, and has a specific time to read and present a selected resource
  • Taking notes from the meeting and presentations
  • Addressing yesterday’s problems that were added to the UX maps

data collection:

  • Collecting data on a problem of one’s choice in the form of a mini-map, list, or any other clear to present form
  • Writing down the ideas for the solution

crazy 8:

  • The exercise is based on dividing a sheet of paper into 8 pieces and drawing 8 sketches/application screens of a product in 8 minutes

The purpose of Crazy 8 exercise is not the sketches in itself, but to stimulate the creativity and warm-up the mind.

project sketch

  • At this stage, we draw simple sketches of the real product and steps to solve the problem

day summary:

Answering the key points:

  • Is the goal measurable and achievable?
  • Did everyone understand the problem?
  • What was remembered?

Day 3.

Decision making

Aim: Choosing a project solution and deciding about its details.

introduction:

  • Agenda overview – what’s the plan and today’s aim

the first voting:

  • We vote for projects and solutions that were created the previous day
  • Each participant votes on its own for the three most interesting projects

projects discussion:

  • Getting acquainted with projects
  • Projects discussion (the creator is silent)
  • Meeting moderator writes everything down
  • The creator expresses his opinion on the discussion

the second voting:

  • Everyone votes anonymously for the project they think is the best and adds an additional explanation of their choice

creating the action plan template

  • Creating the action plan divided into steps (optimally 10-15 steps)

day summary:

Answering the key points:

  • Is the goal measurable and achievable?
  • Did everyone understand the problem?
  • What was remembered?

Day 4.

Product Prototype
Development

Aim: Dividing participants into roles and developing the solution prototype. Day 4 is dedicated to UX/UI Designers and Copywriters.

introduction:

  • Agenda overview – what’s the plan and today’s aim,

product prototype development:

If more people are involved in this stage, we assign roles:

2x Designers, 1x Project Manager, 1x Copywriter, 1x Marketing Manager, 1x Moderator

  • The creators are responsible for creating application screens
  • Copywriter creates content
  • PM pays attention to the consistency and project history
  • Marketing Manager prepares resources and makes research

We should end this stage with a fully prepared product design mock-up.

day summary:

The designers prepare clickable prototypes.

Answering the key points:

  • Is the goal measurable and achievable?
  • Did everyone understand the problem?
  • What was remembered?

Day 5.

Testing Procedure

Aim: We test the prototype on target users. Testing process on a real research group.

introduction:

  • Agenda overview – what’s the plan and today’s aim,

conducting prototype tests:

  • At this stage, we should have a clickable prototype (Lo-FI) for the research group in order to get detailed results

testing cycle:

  • Interview - around 60 min
  • Break - around 30 min
  • Cycle repetition
  • Ending and summary - around 45 min

day summary:

Answering the key points:

  • Is the goal measurable and achievable?
  • Did everyone understand the problem?
  • What was remembered?
  • Are we able to implement the solution?
  • What should we improve in the testing stage?

Design Sprint ends with a casual discussion over your favorite food & drink.

Design Sprint is a five-day workshop dedicated to improving the process of rapid validation of design hypotheses.

Design Sprint

Idego is a custom software development company able to bring your product vision into life. We give you access to the latest technologies and trends but most importantly, to a talented and dedicated team of professionals.

Get a free estimation
Need a successful project?