Karl Philip has been working on digital marketing and online trading since the nineteenth-arrow and-bue. What he's left with after all the experience is that there's chaos everywhere. Therefore, it is often important to get just started to get something done - do not wait.
Tips for launching projects:
- Get started quickly: Don't wait too long, just start somewhere
- View Large Image: Get agreed and get an overview
- Make the most basic and basic first: Start somewhere and work on
- Do not involve too many (but the right ones): It is important not to involve the wrong people
- Break Rules: Be Curious
- Use data: Be analytical
- Set tight deadlines: A job more efficiently when you have to deal with deadlines
- Do not underestimate young people: The best ideas often come from young people and those who are new in the industry
- Wake to fail!
- Choose a direction and implement as hell!
What's fun about these principles is that many of them are built up by Sprint.

Google Design Sprint
“Google Design Sprint is a shortcut to finding out how customers respond to your idea” – Karl Philip Lund.
Google Design Sprint is a method developed by Jake Knapp and Google Valves, by using the most efficient processes in innovation, corporate culture and design. A Google Design Sprint is going on over a whole week of work. The five days are dedicated to different parts of a development process. A worker works on specified tasks with deadlines and thus forces the process in the future.
Monday It's mainly about mapping and understanding the problem. You look at where you are, where you want to be in the x-number of years, as well as possible obstacles to reaching the goal per day. This is drawn as a map to visualize the path to the goal. Here, too, the customer travel must be included. On the same day, experts in different areas are also collected for the purpose of filling out the holes but may not be aware of themselves.
Whole Tuesday goes to work alone, but together. Here are suggestions for different solutions to the problem that have been defined. First, you do a practice called lighting demosWhere you pick up inspiration and demonstrate to the team a bit of good, existing solutions. Then you go over to drawing sketches. This is done through a four-step sketch process with guidelines to ensure that there are many concrete proposals at the end of the day.
Wednesday is going to make decisions. Tuesday's sketches are presented anonymously by the fasiliator for the sprint, and all participants vote out the best ideas, possibly parts of ideas. Based on the voices, you choose a solution that will later be prototype. So this one is drawn on a storyboard, so you get a complete picture of what the prototype is going to look like and work.
Enabled Thursday You make prototypes from the storyboard. This one acts as a façade for the solution, which makes the user think it's a real solution. The team is split up so that some work with design, some with text and others with preparation for the user tests on Friday. Using simple prototype tools, such as KeyNote, it is actually possible to create a prototype in just one day.
Last day of the sprint is Friday where you get answers from and responses from actual customers to the solution you have worked intensely with in the last four days. We use the prototype of five people, which allows us to detect the entire 85% of errors and shortcomings in the solution. At the end of the day, you're left with a valuable insight to base your strategy and decisions on.
Erik Thorvaldsen from MaxMaling went through all the days with a wish to make changes to sell more and make the website more customer-friendly. He thought the whole process was difficult, tough and challenging, but teaching. There has been no dance on roses – sales and traffic have dropped after new websites were launched. Most of these events occur in the launch of new websites. Nevertheless, the trend is positive, because although traffic is less than before, each user spends longer time on the page and the conversion rate has increased.

Innovation through Design Sprint
José Manuel Redondo Lopera from Computas is probably one of the most familiar people with Google Design Sprint in Norway. With his lecture, “Innovation through design sprint”, José went through the principles of a design sprint, as well as the important phases in advance and after. In addition, he was clear that a sprint with a “dritter problem” is not to be carried out as a basis.
Severity
With “dritter problems” José believes that some issues should not be included in a sprint process. For example, questions about where to place a Call-to-Action button or how a landing page should look. The principle of design sprint is that one should be able to explore a problem and clarify whether the final result is something one should go on with. In such a process, one often has important business decision-makers in addition to a fasiliator. When a person has dedicated resources and set aside time for often busy decision-makers, a strategic and critical issues related to the core activity and not less issues, as described above.
José also entered the pre- and post-phase of a design sprint and clarified the importance of planning in advance. Before starting the sprint it may be useful to collect information about a potential target group, to see a wish as a result of the sprint, the purpose of the process, the necessary data that is important to have in the back of the head and the persons to participate in the sprint.
Postphase
The post-phase is about evaluating the insight process has given the group and deciding what to do further. This focuses on the importance of evaluating feasibility and implementation of the results, which can be measured against the following keywords: desirability, feasibility and viability. Overall, José explains that the sprint process provides a 360 understanding of the problem, a prototype that provides valuable insight and a changed organisational culture.
Summary
There is no doubt that Google Design Sprint is a methodology that is in the wind. There is a process many people can use – either themselves or with the help of others. This way of working is too many types of challenges for many different actors. Google Design Sprint is a focused work method that, with some preparation, can produce a lot of effect in conjunction with time and resource use.
Is Google Design Sprint anything for you? It remains to be seen, but we recommend reading more about the process on your own, as well as reading the book by Jake Knapp.
By: Sander Kaasa, Frode Vik, Signe Marie Cleveland and Cathrine Andrea Knutsen
