The Basics of Rapid Prototyping #innovation #systems #design
I had a terrific chat last week with Dr. Joanne Jakovich of Sydney's u.lab that was curated by the lovely Ele Jansen, a Ph.D. researcher and someone with whom I had the pleasure of collaborating when we launched WSWP (Wicked Solutions for a Wicked Problem) in Los Angeles a couple of years ago.
You can read the summary on the Learn Do Share blog, but I thought Ele and Joanne steered the conversation in a really interesting direction when we started delving into more detail around group ideation and intelligence, specifically around the notions of responsibility and the enactment of ideas within an organization. I would consider Joanne's group to be at the forefront of intelligence design between large organizations.
You can listen to our entire conversation here.
An area of focus in my work that leverages responsibility and enactment, and streamlines some of the associative processes, is something more universally known as rapid prototyping.
Rapid prototyping can take on many forms, and can entail the creation of anything from a big idea to a multi-platform narrative, a product or a service, a technology or a business plan... or all. People tend to think of hackathons as synonymous with rapid prototyping, but in the model I speak of here, it's intended to be a much more informed and coordinated approach to making things.
This is a crude representation of how it works; this is really just a framework that adapts to the type of challenge and the domain in which you might be working. The experiences we create for organizational stakeholders can vary quite a lot, and can be quite complex in their functions, even if the outputs are not.
It would be great to hear about any thoughts or experiences you've had with prototyping in general, or how you think group (collective) intelligence can better accelerate ideas.