{
    "version" : "https://jsonfeed.org/version/1",
    "content" : "resources",
    "type" : "single",
    "title" : "10 Tips for Creating the Perfect Open Opportunity Task |Digital.gov",
    "description": "10 Tips for Creating the Perfect Open Opportunity Task",
    "home_page_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/","feed_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/resources/open-opportunities-task-creator-toolkit/10-tips-for-creating-the-perfect-open-opportunity-task/index.json","item" : [
    {"title" :"10 Tips for Creating the Perfect Open Opportunity Task","summary" : "Ten tips for creating tasks in Open Opportunities on USAJOBS.","date" : "2015-04-24T04:12:26-04:00","date_modified" : "2025-01-27T19:42:55-05:00","authors" : {"lnelson" : "Lisa Nelson"},"topics" : {
        
            "professional-development" : "Professional development"
            },"branch" : "bc-archive-content-3",
      "filename" :"10-tips-for-creating-the-perfect-open-opportunity-task.md",
      
      "filepath" :"resources/10-tips-for-creating-the-perfect-open-opportunity-task.md",
      "filepathURL" :"https://github.com/GSA/digitalgov.gov/blob/bc-archive-content-3/content/resources/10-tips-for-creating-the-perfect-open-opportunity-task.md",
      "editpathURL" :"https://github.com/GSA/digitalgov.gov/edit/bc-archive-content-3/content/resources/10-tips-for-creating-the-perfect-open-opportunity-task.md","slug" : "open-opportunities-task-creator-toolkit/10-tips-for-creating-the-perfect-open-opportunity-task","url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/resources/open-opportunities-task-creator-toolkit/10-tips-for-creating-the-perfect-open-opportunity-task/","content" :"\u003col\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eDivide and conquer\u003c/strong\u003e: 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).\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eIn 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.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eBe specific\u003c/strong\u003e: Define exactly what needs to be done and what deliverables you expect. Include links or documents that the participant will need.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe DigitalGov team \u003ca href=\"https://openopps.usajobs.gov/tasks/25\"\u003eneeded a writer\u003c/a\u003e who could contribute to a weekly blog series. The task included \u003ca href=\"https://www.usajobs.gov/tag/trends-on-tuesday/\"\u003ea link to the blog series\u003c/a\u003e so that potential participants could get familiar with existing articles.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eGive the big picture\u003c/strong\u003e: Include information on how participants\u0026rsquo; work will/may be used. This helps participants understand their work is part of a greater effort.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe National Institute of Standards and Technology (NIST) \u003ca href=\"https://openopps.usajobs.gov/tasks/24\"\u003eneeded facts sheets updated\u003c/a\u003e. For their task, they explained that the fact sheets would be posted on their website and would \u0026ldquo;help the world understand the importance of the National Network for Manufacturing Innovation at NIST.\u0026rdquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eKnow your own availability\u003c/strong\u003e: Remember that you are an active part of Open Opps: the more clarity you provide, the less \u0026ldquo;back and forth\u0026rdquo; 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.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eA title is more than words\u003c/strong\u003e: Write a catchy title (BUT also make sure it\u0026rsquo;s clear and descriptive!).\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEvery task can have a catchy title. \u0026ldquo;\u003ca href=\"http://gsablogs.gsa.gov/dsic/2013/05/07/help-us-tell-the-story-about-a-nih-rockstar-who-is-creating-modular-on-the-go-content/\"\u003eHelp Us Tell the Story of an NIH Rockstar\u003c/a\u003e\u0026rdquo; catches more attention than \u0026ldquo;Interview an Employee of NIH.\u0026rdquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFocus on skills, not job titles\u003c/strong\u003e: 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.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eFor example: \u0026ldquo;I need someone with strong data analysis skills in Excel\u0026rdquo; rather than \u0026ldquo;I need someone with experience as a Research Assistant.\u0026rdquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eDrop jargon\u003c/strong\u003e: 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.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eSet realistic timelines\u003c/strong\u003e: 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?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eEvery Open Opp is a learning opportunity.\u003c/strong\u003e 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.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe DigitalGov usability team requested help with \u003ca href=\"https://openopps.usajobs.gov/tasks/18\"\u003ewriting usability case studies\u003c/a\u003e. They clearly stated that using WordPress was part of the task, but they would accept a participant who was willing to learn WordPress basics.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eMarket your Open Opp\u003c/strong\u003e. Are there communities of practice (CoP) that might be interested in your task? Use our \u003ca href=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2015/04/Open-Opps-Marketing-Email-Template-for-CoPs.docx\"\u003eOpen Opps Marketing Email Template for CoPs\u003c/a\u003e (Word document, 14 KB, 1 page) to craft a message.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eWant to target an individual (or six?) Each task has a \u0026ldquo;share\u0026rdquo; button that produces a pre-populated email template.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ol\u003e\n"}
  ]
}