Divide and conquer: Keep projects simple—if you have a big project, consider dividing it into smaller tasks. You can also offer several tasks at the same time (rather than sequentially).
- In order to create the Federal Crowdsource Mobile Testing Program, the Mobile team posted a 20 percent task to help plan and create the program. Once the program was up and running, the team created two additional opportunities: one to manage the program and a second to run individual test cycles. Multiple test cycles can be advertised on Open Opps at the same time.
Be specific: Define exactly what needs to be done and what deliverables you expect. Include links or documents that the participant will need.
Give the big picture: Include information on how participants’ work will/may be used. This helps participants understand their work is part of a greater effort.
- The National Institute of Standards and Technology (NIST) needed facts sheets updated. For their task, they explained that the fact sheets would be posted on their website and would “help the world understand the importance of the National Network for Manufacturing Innovation at NIST.”
Know your own availability: Remember that you are an active part of Open Opps: the more clarity you provide, the less “back and forth” you will need to do in the future with participants. If you are submitting a 20-percenter task, ensure that you are able to invest time supporting participants for the duration of your project.
A title is more than words: Write a catchy title (BUT also make sure it’s clear and descriptive!).
- Every task can have a catchy title. “Help Us Tell the Story of an NIH Rockstar” catches more attention than “Interview an Employee of NIH.”
Focus on skills, not job titles: Participants may skip over opportunities if they do not identify with a particular job title. A skill list will self-populate as you create your task. Use that skill list to guide your task description.
- For example: “I need someone with strong data analysis skills in Excel” rather than “I need someone with experience as a Research Assistant.”
Drop jargon: Write your tasks in plain language. Use full office names rather than acronyms. Avoid using office-specific slang. Define complicated terms or include links to relevant resources that will help participants understand the task.
Set realistic timelines: Participants may not be familiar with your office or agency. Does your task require background knowledge that may take a variable amount of time for the participant to research, depending on learning styles?
Every Open Opp is a learning opportunity. Many tasks do not require participants to be experts in a given field. If you are looking for somebody who is willing to learn a new skill, clearly state that.
- The DigitalGov usability team requested help with writing usability case studies. They clearly stated that using WordPress was part of the task, but they would accept a participant who was willing to learn WordPress basics.
Market your Open Opp. Are there communities of practice (CoP) that might be interested in your task? Use our Open Opps Marketing Email Template for CoPs (1 page, 14 kb, MS Word .docx) to craft a message.
- Want to target an individual (or six?) Each task has a “share” button that produces a pre-populated email template.