Ideation is the process where you generate ideas and solutions through sessions such as Sketching, Prototyping, Brainstorming, Brainwriting, Worst Possible Idea, and a wealth of other ideation techniques. Ideation is also the third stage in the Design Thinking process. Although many people might have experienced a “brainstorming” session before,...
Once we have an understanding of the foundation we all need to run a successful design sprint, we kick off by working through the sprint’s Monday exercises — setting a proper long term goal based on our sprint challenge, determining our sprint questions, creating a map, interviewing experts, connecting our personas to the map, and selecting a target.
To help you understand Design Thinking, we have broken the process into five phases or modes, which are: 1. Empathise, 2. Define, 3. Ideate, 4. Prototype, and 5. Test. What’s special about Design Thinking is that designers’ work processes can help us systematically extract, teach, learn, and apply these human-centered techniques to solve problems in a creative and innovative way – in our designs, in our businesses, in our nations (and eventually, if things go really well, beyond), in our lives. Nevertheless, a great artist like Auguste Rodin, who created this famous sculpture called “The Thinker” and originally “Le Penseur”, would most likely have used the very same innovative processes in his artwork. In the same way, all great innovators in literature, art, music, science, engineering and business have practiced it and still practice it.
Transforming concept into business: transforming the prototype into a business stream, is not only a question of  product industrialization, it’s also a matter of distribution channels, customer relationship, resources, partnerships, profitable model, all things that often require the engagement of parent business unit within the company. This transformation process where your innovative concept creates an opportunity for your partner business unit is a delicate scale-up to handle.
As a Sprint facilitator, it is very easy to focus too much on the “How” while planning a Sprint: When is the date? What is the room situation? What are the activities and agenda for each day? Those are questions that are important but not critical. Before getting into the logistics, there are two important things to focus on to ensure the success of a Design Sprint.

In the end the design effort and research should lead to an "Fact Based or Evidence Based Business Design". The design can have many forms, ranging from a business plan to a company website, but we advise that the design should at least contain a substantiated Value Web, a substantiated Business Model Canvas and a substantiated Value Proposition Canvas.

“On Monday, you and your team defined the challenge and chose a target. On Tuesday, you’ll come up with solutions. The day starts with inspiration: a review of existing ideas to remix and improve. Then, in the afternoon, each person will sketch, following a four-step process that emphasizes critical thinking over artistry. Later in the week, the best of these sketches will form the plan for your prototype and test.” 

The company’s current focus (determined from previous Googlegeist surveys) is to be the most inclusive workplace on the planet. As Frederik says, diversity and inclusion lead to empathy and innovation. As an organization, the more inclusive you are the more innovative you are. Google is designing products for people all over the world, which makes it imperative for the company to understand and empathize with different global perspectives. How well you connect to people who are different from yourself significantly increases the diversity of ideas you have.
You’re the product person in your organization. You may have no one reporting to you. You might have 50 people in your product group. You might be responsible for the entire product. Maybe the design team doesn’t report to you, nor do the developers or marketing and sales teams. Maybe you’re in a startup without all those defined roles, and you wear a lot of hats. Maybe you’re in a large enterprise organization that has each one defined to the nth degree. Maybe you are a product design freelancer. You might work in an agency as a consultant. You probably have read a blog post about this process. Maybe you even tried one yourself. You’re very likely wondering how your unique needs will work with design sprints and are seeking more information than you can find in a few blog posts.,f_auto,fl_progressive,h_100,q_auto,w_100/
While we assume you’re familiar with the original Design Sprint, here’s a quick recap: the Design Sprint is a five-day process to solve big problems and test ideas. A dedicated team discusses a challenge, designs potential solutions, and tests them with real users. You start with something vague, and finish with real feedback and something extremely tangible in just five days.
With the skills you will learn you will be able to modify and create new Design Sprint agendas and flows that fits your needs. Often Sprint Masters need to adapt according to their needs and resources. This means making changes in the original process flow depicted in the original books or ever-changing modifications of it like Design Sprint 2.0. These hard-coded Sprint agendas need constant adjustments to perform in specific scenarios and with specific resources.
action activity Aldo Rossi analogy analysis applied approach appropriate architects architectural design architectural positions arrangement aspects associationism Bernstein bricolage building chitectural clearly Colquhoun complex composition concept constraints construction context Corbusier creative decision decision tree defined design problems design thinking devices distinction earlier elements episodes evaluation example expression facade figure formal framework functional further Hannes Meyer heuristic heuristic reasoning inquiry instance interpretation involved kind Le Corbusier logical means means-ends analysis ment Michael Graves modern normative positions organizing principles orientation particular Peter Eisenman planning Press prob problem at hand problem space problem-solving behavior procedures proposed protocol qualities Rational Architecture realm reference represent rules scheme Scott Brown seen selective inattention sense Simon social solution solver solving spatial specific strategy structure subproblems systematic technical theoretical theory tion tradition tural ture urban design wicked problems York