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,...
Humans naturally develop patterns of thinking modeled on repetitive activities and commonly accessed knowledge. These assist us in quickly applying the same actions and knowledge in similar or familiar situations, but they also have the potential to prevent us from quickly and easily accessing or developing new ways of seeing, understanding and solving problems. These patterns of thinking are often referred to as schemas, which are organized sets of information and relationships between things, actions and thoughts that are stimulated and initiated in the human mind when we encounter some environmental stimuli. A single schema can contain a vast amount of information. For example, we have a schema for dogs which encompasses the presence of four legs, fur, sharp teeth, a tail, paws, and a number of other perceptible characteristics. When the environmental stimuli match this schema — even when there is a tenuous link or only a few of the characteristics are present — the same pattern of thought is brought into the mind. As these schemas are stimulated automatically, this can obstruct a more fitting impression of the situation or prevent us from seeing a problem in a way that will enable a new problem-solving strategy. Innovative problem solving is also known as “thinking outside of the box”.
Some designers have argued Google Glass is actually an exemplar of design thinking. The project was a grand experiment that incorporated creative risks and unconventional thinking—and a failure that is possibly more revealing than success would have been. Design thinking is simply manifested differently at a massive company like Google than it is in a classroom or studio, said Daniel Rose, an officer at a design-oriented consulting firm, in a LinkedIn discussion.
“Monday’s structured discussions create a path for the sprint week. In the morning, you’ll start at the end and agree to a long-term goal. Next, you’ll make a map of the challenge. In the afternoon, you’ll ask the experts at your company to share what they know. Finally, you’ll pick a target: an ambitious but manageable piece of the problem that you can solve in one week.”
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.
design sprint is simple and very very smart, it teaches us the meaning of meaningful work. It has a excellent process, framework and practical exercises in order to increase the likelihood of success. The fact that there are no caps in the title show simplicity, elegance and degree of detail in this book......if you are doing design sprints and want ideas or want to teach people in your organization you need this book.
It takes four days instead of five. Why? Because we realized that there are countless little hacks you can do to make the process more efficient. We moved things around, changed up the order to make the flow more logical, and we also shortened a lot of the steps involved. Incredibly, we’ve also added stuff in, only to make the whole thing take less time. I know, this sounds confusing, but it’ll make sense if you keep reading…
To be successful at creating digital products you have to reduce the risk of failure but it's almost impossible to do that. Traditionally design leads have tried planning their way out of that conundrum. Only to find that no amount of planning can guarantee an outcome. In our lives we've been guilty of this too. Our grey hairs should stand testimony to the failure of waterfall and even Agile project management methodologies.
In a world of hyper-specialization, C. Todd stands in the intersections and sees the connections that revolve around us. As an Innovation Architect at Constant Contact's InnoLoft, he facilitates product and service design sprints for a wide range of external startups and internal product teams. C. Todd is also a member of the adjunct faculty at Madrid's prestigious IE Business School where he teaches courses on Creativity, Innovation, Design-Thinking and Communication.
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.