I'm planning some fast-paced introduction workshops to the design cycle, and how it can be used to tackle seemingly huge issues in a speedy, inspirational, creative way.
The problem is that everyone comes believing that collaboration is where innovation comes from, and that just isn't the case. Not always, anyway.
One of the challenges we sometimes see is that, in a group brainstorming exercise such as 100 Ideas Now, teams generate lots of good ideas, but then, through consensus, hone them down into relatively tame and 'safe' ideas. It's no surprise that we sometimes wonder whether any of those ideas actually get implemented back at home, outside the workshop experience. (As a side note, I'm delighted to say that I do, in fact, often hear about major timetable innovations or changed school dining experiences months after the initial workshop, but it feels inconsistent...)
We already make sure that those brainstorming activities start as individual activities, a discipline that most workshop participants find incredibly hard to stick to - they want to debate, pitch, share their ideas. Sharing is good after all, isn't it?
Even the honing exercises start individually, before becoming a consensus.
Google Ventures' Jake Knapp talks about his challenge in finding 'alone time' to generate ideas and prototype them quickly, without the need to pitch and explain himself too early on. What he does is a design sprint, by any other name, but it is one he undertakes largely alone.
This idea of using design sprints in school innovation is something I dive into in greater detail in my book, How To Come Up With Great Ideas. It's a technique rarely used in big industry or schools, but those who do see how it might be used immediately get excited by the potential.
What is the project you might be doing at the moment that would benefit, not from a five year strategy, but from a sprint of a few weeks?