After leading a complex effort to crowdsource ideas to solve a problem facing your agency, the last thing you want to hear is that the innovative solutions you received don’t actually help remedy the issue.
More than 20 federal innovators recently took part in a workshop offered to avoid such a scenario. The Department of Homeland Security’s Meredith Lee, who also serves as the volunteer lead for the Federal Ideation Community of Practice (ICOP), led the participants through various exercises to help agencies learn to identify and define the problems they face; a key part of the process of any ideation exercise and/or challenge competition.
With interest in federal ideation increasing and the recent launch of Challenge.gov, a free federal public prize competition crowdsourcing tool, the workshop was a timely reminder of the work needed to plan a successful challenge. (Hint: It starts with an accurate problem statement!)
Lee noted that often a problem is assumed before needed research is done about the people it affects, and then long processes (such as a public prize competition) are carried out, all the while asking the wrong question.
Three important takeaways of the workshop include:
1. Empathy is key
Understanding the people who are affected by the problem is the most important part of the process of creating an actionable, accurate problem statement. Before making assumptions about what might solve an issue, take the time to explore the thoughts, values, and opinions of the users. If you can, interview them personally.
The participants in the workshop were given a mock scenario, improving the “lunch experience”, and asked to interview each other to gain insight about the other person’s view of lunch.
Emphasis was placed on listening rather than leading, and using phrases like “tell me more” and “why.”
The results were telling and varied. The “important” part of a lunch break was reported in many forms:
- Escaping the office
- A chance to get needed exercise
- Food itself was most relevant
- Catch up on work
It became obvious that improving the “lunch experience” would not easily be summed up with a singular action.
2. Think about user point-of-view
Use the feelings, emotions, thoughts, beliefs, actions, behaviors, and quotes you collected while empathizing with users to form insights and create point-of-view statements. Having a grasp of the point of view will assist you in forming the problem statement and the “ask” for your crowdsourcing competition.
Lee recommended using a simple formula to create user point-of-view statements:
“[insert user] needs a way to [insert need] in order to/because [insert insights].”
3. State the problem before the ask
When you prepare to run the challenge, make sure the potential solvers know the problem itself (which you painstakingly identified previously) before asking them to do something; it’ll help both you and the potential solvers stay focused and produce more pointed solutions.
For example, instead of opening your competition description with, “We want ideas for new methods to harvest honey,” state the problem behind it, and then ask for ideas:
“Recent weather conditions have caused this year’s crop of honey to be thicker than usual, and as a result, the current systems to harvest honey from the combs are not cost-effective, which drives up the price to the consumer. We are looking for ideas for new methods to harvest this unusually thick honey.”
With this method, the potential solver has a much better idea of what he/she is trying to accomplish.
For more information on challenges and crowdsourcing, see the Crowdsourcing Toolkit for Federal Agencies or email firstname.lastname@example.org to join the Challenges and Prizes Community of Practice listserv. To join the Federal Ideation Community of Practice, which focuses on internal agency ideation, email email@example.com.
Have feedback or questions? Send us an email at firstname.lastname@example.org