There is currently a big push towards moving from the traditional way to innovate, special people, special places, special ideas to more open, inclusive and collaborative models based on frameworks such as design thinking and design sprints. But this is no smooth transition, especially in the larger, more traditional organisations, and usually, there is a great deal of confusion on where to begin this process.
I want to share with you a case study on the topic.
One of these larger, traditional organisations, where innovation was, at best, a buzzword, sought our help to turn it into something meaningful that would generate value within the company. They wanted employee’s ideas pushed up the pipeline to the point where they become tangible initiatives in alignment with the overall business objectives. And they wanted it fast.
The project kicked off with an alignment meeting on the core strategy and a plan to implement. We had six weeks to engage a workforce of 5,000 people, collect their ideas, design a vetting process to narrow down to the three most promising ones, which we’d then validate through a design sprint.
All ideas had to meet the following criteria:
As early adopters of Design Sprints and having already run dozens in the past, we were well equipped for the Design Sprint stage of this project. But how to get to that point?
In the end, we decided to get them started on their innovation journey with a Problem Framing workshop in which we invited the top 10 key decision-makers.
Problem Framing is a framework, based on design thinking principles and methods, used to understand, define and prioritise complex business problems and help stakeholders make better decisions, fast.
The Problem Framing framework was developed by the Design Sprint Academy, as a preliminary step in the process of running Design Sprints to ensure effective outcomes and make the investment in a Design Sprint worthwhile (read more about Day 0 in the Design Sprint 3.0).
Problem Framing is about understanding, team alignment, and defining a strategy for the future. It is a process in which the stakeholders need to pay equal attention to both the business need and the customers’ problems they are trying to solve, as that is the sweet spot where big opportunities lie.
The Problem Framing team was made up of decision-makers, typically executive level, who are keen advocates of innovative projects within the company.
Together with the client team, we drafted an internal email integrated with a Typeform questionnaire, inviting all employees to submit their ideas. In that questionnaire, were the following questions:
All replies were captured in an excel file and submitted to the problem framing team for review.
Borrowed from Gamestorming, we used the NUF test to cross-check big ideas for weak points and also to what degree they are New, Useful, and Feasible.
NEW — It wasn’t done before or is significantly different from previous approaches. Out of the box, innovative ideas will score higher.
USEFUL — It solves the problem completely, without creating any collateral damage.
FEASIBLE — If can be implemented by the organisation. Ideas requiring less effort, resources and money will score higher.
We used this tool remotely by inviting the Problem Framing team to score ideas from 1 to 10 for each criterion and then tallied the results automatically in an excel file.
We then looked at the top 30 ideas that scored the highest on the NUF test and considered them to be valid candidates for the Problem Framing Workshop.
Five weeks have passed and we are now finally ready to run a two-day in-person Problem Framing Workshop with the Problem Framing Team.
Prioritise ideas: 30>>10
A few days went by since the team managed to review and score remotely all the 90 ideas collected from the company employees. We wanted to kick off the Problem Framing workshop by making sure that everyone is up-to-date and reconnected to the workshop objectives. We started by rebooting their memory with the help of the Art Museum exercise. For that, we printed ahead all the big ideas collected from the company employees on large posters and displayed them on the walls.
We gave everyone these simple instructions:
Now that the big ideas were fresh in the team’s mind, we were ready to categorise based on similarity, topic, or problem area. The team members then took it in turns to read aloud and discuss each idea with the rest of the team. We ended up with clusters of ideas where some scored higher than others on the NUF test.
The team still needed to discuss any discrepancies or duplicate solutions in order to align on a final NUF score. After a heated debate, we were able to recalculate the NUF total for each total and the top 10 solutions became apparent. We had our winners!
Prioritise ideas: 10>>3
With our top 10 ideas confirmed, we split the team into two groups: Idea Challengers and Idea Supporters.
We asked Challengers to silently & individually come up with potential problems, blockers and Supporters with solutions, strengths and benefits. For 3 minutes, everyone brainstormed individually, one idea per post-it.
In a head-on-head rumble, points were awarded to each group.
This is how it typically goes when prioritising ideas with this exercise:
This interactive exercise helped the team to narrow down the top ten solutions to the final three. Besides giving the team the opportunity to explore the solutions in-depth, this simple debating exercise helped the team to remain highly focused on the task at hand in order to reach the crucial stage of alignment. Both sides performed their roles with the utmost enthusiasm and dedication, which further served to underpin everyone’s understanding of the solutions being discussed.
So there we were, halfway into the process. We ended the first day of Problem Framing in alignment, having whittled down thirty solutions to three well rounded and informed business challenges. Next step: to reframe them into Design Sprint Challenges and let the sprinting begin.
How to prioritise ideas with Problem Framing? (Part 2 — Reframe Problems) — coming soon
If you want a Problem Framing deep dive simply join one of our public workshops in Berlin or London. Also, if you are going to the Google Sprint Conference this year, we will be teaching Problem Framing on the first day of the conference.
A special thanks to John Vetan and @Elle Yeats-Green for their help with editing and contribution to this article.
(Article originally published on Medium - https://medium.com/design-spri...)