Google Design Sprint is a framework for creating ideas, solving product/service problems and aligning teams' vision about it. It set clear goals that you achieve within just five days with design thinking methodology.
This method limits the effect of authority, repeated, and "can't be done" so much that I am surprised that it has not replaced all the meetings typical of corporate and non-corporate work methods.
What I love about Google Design Sprint
There are five great things, that I personally love about it:
- Quiet brainstorming
- Diverse competences in one team
- Fast decisions
- Time limitations
- Tests with users
So, without further ado, let's jump right into the first one!
Quiet brainstorming is a king
Quiet brainstorming squeezes you to A4 paper area, text and simple drawings — that makes you think a lot. This actually tests your idea already, making weaker ideas vanish.
In my opinion an anonymity of up to 80% is a great value. It's difficult to guess someone's style of writing or drawing, that creates a feeling of freedom that can stun and turn the emotions and creativity out of any danger.
It's easier to disagree with the CEO without giving a sticker dot on the project than interrupting his flaming speech.
Projects can be seen by the whole team and even the whole company — it influences the feeling of control and co-creation and gives you the opportunity to get considerably broader feedback.
Team really together and in one direction
It's great to see people with diverse competences, focused on one task and one sense of well-being that allows for an engagement that not only motivates but energizes the mind.
Team knows and feels sense of work that is going to be evaluated with users very soon.
It's nice to know that the labour-consuming work on pixel perfection or code clutter makes sense in the eyes of potential customers.
Decider is here
Quiet brainstorming is rated with stickers, each of a team has a certain amount — it builds the voice of the people — the technical, design and marketing and other but still the decider is taking final decision.
I really understand subtle distinction between product owner and UX team.
The team isn't responsible for money, strategy and risks and it's really important to make the product owner feel in control.
Google design sprint gives product owner or client all control over what will be selected and verified with customers, and a bit of dare to try something less conservative... It's sprint so we will know fast.
Time Timer — pretty accessory of Google Design Sprint
Time counter invented for school kids is actually great for creative work — lets everyone see how much time is for every task.
This visual clock really stops mess and gives possibility to work on topic in a structured way. Also, helps to solve more in less time and keeps every area of project covered with just a little help from facilitator.
Meeting with people
Testing the project during the 5th day is a journey into another world...
I have seen many things that I have designed in the hands of real users. Patterns and good practices do not always work, because each mix is unique and it's hard to predict effects.
However, experience of user-testing transferred to many system developers is something quite different. I've noticed that this is the way to appreciate the work of designers and motivate for additional and sometimes tedious development.
Google Design Sprint is a great method of coming up fast with business-oriented ideas. It consumes less time and less effort than traditional product or service-oriented meetings.
During the sprint you go through all the phases needed to create a bullet-proof idea:
You can apply the design sprint process every time when you search for a new business idea or you want to pivot your product or service towards something new.
If you have any questions about Google Design Sprint, or you want to participate with your team in our workshops, contact us!