Every project starts with an idea… an idea that someone is excited enough to sponsor.
- But where are your ideas being generated from?
- How do they get cultivated and given time to grow?
- How do they get pitched? and How do they get heard?
- How are sponsors persuaded?
- How do they then get implemented?
- How do we amplify this cycle of innovation and implementation?
I’m fascinated by these questions in OSS for the reasons outlined in The OSS Call for Innovation.
If we look at the levels of innovation (to be honest, it’s probably more a continuum than bands / levels):
- Process Improvement
- Incremental Improvement (new integrations, feature enhancement, etc)
- Derivative Ideas (iPhone = internet + phone + music player)
- Quantum Innovation (Tablet computing, network virtualisation, cloud delivery models)
- Radical Innovations (transistors, cellular wireless networks, Claude Shannon’s Information Theory)
We have so many immensely clever people working in our industry and we’re collectively really good at the first two levels. Our typical mode of working – which could generally be considered fire-fighting (or dare I say it, Agile) – doesn’t provide the time and headspace to work on anything in the longer life-cycles of levels 3-5. These are the levels that can be more impactful, but it’s these levels where we need to carve out time specifically for innovation planning.
If you’re ever planning to conduct innovation fire-starter sessions, I really recommend reading Richard Brynteson’s, “50 Activities for Building Innovation.” As the title implies, it provides 50 (simple but powerful) exercises to help groups to generate ideas.
Please contact us if you’d like PAOSS to help facilitate your OSS idea firestarter or road-mapping sessions.