INEVO

Google Design Sprint

Google Design Sprint will help you in the future. Together, we are rewinding time and getting insight into how the target group interacts with a product or service.

How do you distinguish a good idea from a bad idea? We believe Google Design Sprint is the solution.

To put new ideas into practice because it takes time and resources, and the uncertainty about whether this is what users need and want to have come crawling.

Google Design Sprint will help you in the future. Together, we are rewinding time and getting insight into how the target group interacts with a potential product or service. In this way you limit the risk and avoid making decisions that oblige you to develop the idea without testing whether it is good.

What is Google Design Sprint?

Google Design Sprint is a method developed by Jake Knob in Google Ventures to answer big questions quickly - all by using a 5-day process.

The approach is based on traditional and known models of strategy, design and innovation. Over a year, the method has been optimised to become the recognised tool it is today.

Structured tasks solve problems through brainstorming, sketches, prototypes and eventually user testing.

Once the sprint week is over, you will be left with very valuable insight and information about problems and are ready to take action.

Already convinced? Contact us here- What?

Fits to a range of areas

It's worth mentioning that even if design is part of the name of the method, it is not just design problem it can solve.

Google Design Sprint enables you to solve challenges related to marketing, service and product development, strategy, as well as design and more obvious creative problems. You can also test whether ideas are worth investing in or not, which is beneficial to market insight and user wishes.

What does a Google Design Sprint process look like?

As we have mentioned earlier, a design sprint is a 5 day process. This naturally falls on Monday to Friday. Each of the days is dedicated to a separate area-- then you're left with a process that looks like this:

Mondayunderstand

Structured discussions on Monday lay the basis for the whole sprint. Here we create a map that explains the user journey with optimistic long-term goals and critical points on the way there. We bring in experts who share their experiences and formulate questions about how we can solve the challenges that arise. And then finally, let's pick an ambitious, but manageable focus point we're going to solve in the sprint. Tuesday - I'm sorry. sketch

Because brainstorming can often limit creativity, we work on Tuesday individually to find the best solutions for the problem we pointed out on Monday. We start by getting inspiration from existing solutions, and taking the best parts to sketches for our problem. Everyone sketches their ideas - they don't require drawing skills, they're about visualizing ideas in a rough way.

Wednesday - I'm sorry. decide

After Tuesday we have a good bunch of ideas to work on -- but we can't prototype all the suggestions. So on Wednesday we go through and discuss all the sketches. Then choose those we think have the greatest chance of achieving the long-term goal. The last half of Wednesday's session is to create a storyboard of sketches that will be prototyped the next day.

Thursday - I'm sorry. Prototype

Thursday will help create a realistic façade to be tested on Friday. The prototype shall have “golodilocks quality” – it shall function just enough that the user thinks it is real. With this focus, we can develop a prototype in just one day.

Friday - I'm sorry. Test!

The Sprint starts with a big challenge and over the week we've outlined promising solutions, chosen the best and created a realistic prototype. The last step in the impressive productive week is to test the prototype of 5 actual users by observing when they interact with it.

Research shows that 5 test subjects are enough to see patterns in real consumer behaviourSo let's say that this is the same thing as that. After the user test, we have a valuable insight into what is needed to realise the idea and to move forward a strategy.

Why INEVO?

INEVO has a large professional environment, composed of experts in a number of disciplines - including: design and development- advertising, social media and contentsSo let's say that this is the same thing as that. This makes us have the understanding and competence your Design Sprint needs, regardless of which area it falls under.

We deliver this:

We offer 2-3 sprinters from INEVO and all the equipment needed to complete the process. In advance of the sprint we have a meeting where we look at the challenges you have, put together the team to sprint and schedule the time of the sprint in good time so that everyone can clear their calendar. Together we complete the Design Sprint workshop in 5 full days. One week later we meet to discuss the outcome of the sprint and what action should be taken.

Questions and answers

Frequently Asked Questions

Why should you do Google Design Sprint?

Most products and services fail because there is no desire or need in the market. Google Design Sprint allows us to map this in just 5 days, before you can invest substantially with resources in a project. In a sprint, the clear framework of time limits is forcing decisions. In this way, participants do not fall in love with the ideas and look blind at them, but rather have to make faster decisions based on intuition and team knowledge.

What is the outcome of a Google Design Sprint?

You solve a problem in just 5 days and thus save a lot of time. During the days you will also get a unique insight into project processes, what works and not by user testing, see how other jobs, as well as strengthening the collaboration of the sprint team.

What do you need for a Google Design Sprint?

You need a challenge you need to answer quickly, a multidisciplinary team of 4-7 people with knowledge of the problem, dedicated time to the sprint (5 days from 3 p.m. 10-17), as well as a large meeting room reserved for the 5 days.

Who should be on the team?

The wider range of features the team has in total, the better. The Executive Director must be involved, as the h*n is the decision maker who has the latest words. One tip is to include a key person from each of the company's main fields, such as HR, IT, sales, design, etc.

What happens next?

Whether your idea turned out to be a success or not, you've come a good path and have a valuable insight into the challenge you started with. Maybe you have to run a few days of the sprint again in the following week, or maybe you can start developing the product/solution. Based on Friday's user testing, you are equipped to decide what is right for the way ahead.