Read the full post here: https://www.diginsights.com/blog/innovation-sprints-why-walk-when-you-can-run/
Every company now wants to be a tech company or at least feel like a tech company. As a result, the idea of agile innovation and innovation sprints has moved into even the most conservative legacy companies. Actually, it’s often those companies that are most enthusiastic about bringing a bit of tech energy to their workplaces.
But how do you do it well? Where can you successfully run and where do you need to walk? The below process is CPG-focused, but can be adapted to a range of industries.
- A small group of no more than 10 people
- A mix of backgrounds (marketing, finance, procurement, manufacturing, insights, etc.)
- A commitment of one week.
- Dedication – sprint participants have to ignore other work for the week.
- An illustrator and copywriter in the project team. They are there to ensure that you leave the sprint with illustrated, written ideas.
We recommend an innovation pipeline sprint to develop ideas…
- Your agency partner or facilitator (you have one…right??) should review the relevant existing information and uncover everything you have in terms of jobs to be done.
- If you don’t have this information, you need to either do new research before the sprint begins or the project team needs to do some participatory exercises that help them to determine what the jobs to be done might be.
- Day one is about identifying and organizing the jobs to be done and deciding which will be a focus. The team needs to identify and remain focused on addressing real needs throughout the process.
- Day two we recommend starting with some shopping. Individuals are tasked with a job to be done and shop for existing products that address that job. As an example, a job to be done might be “healthy breakfast that does not leave me hungry an hour later”. What’s available now that addresses that job? Go broad and get everything that might “do” that job.
- The afternoon of day two involves uncovering patterns. In what way does each product the team bought address the job to be done? What are the characteristics that allow it to address this job? What are the pain points associated with each product? This gives us two lists – a characteristics list and a pain points list. From here we can move to brainstorming. What products can we develop that would maintain the key characteristics while also eliminating a pain point? Pairing characteristics and pain points frees people to think in new ways and not just rehash the ideas they brainstormed last year.
- This process repeats for the other key jobs to be done that were developed in day one. The goal is to leave with 100-200 product ideas that address a range of jobs and pain points.
Read the rest of the post here: https://www.diginsights.com/blog/innovation-sprints-why-walk-when-you-can-run/