This toolkit documents the process that The Opportunity Project team at the Department of Commerce and other federal agencies have used to facilitate collaborative, user-centered technology development sprints. Anyone interested in transforming federal data into digital tools for the American people can adopt this process, adapt it for your own sprint, and share your feedback to help improve it.
Civic tech organizations, coding boot camps, and more have adopted The Opportunity Project process. We hope that teachers, community organizations, and state, local, and other government leaders will use it and share feedback to help improve it.
The Opportunity Project aims to solve real-world problems facing individuals and communities. The first step in the process is to identify a problem that your team will work to solve with a data and technology solution. In order to make a solution that really improves lives, it's important to start by working with people experiencing that problem directly to be sure that you're really addressing felt needs. Then find a data set with information that could help to solve that problem, and start building your tool.
Connect with community groups, local leaders, federal agencies, or non-profits who are mission-driven and close to the ground to identify a meaningful challenge to focus on.
Identify an opportunity for federal or local data to make an impact, for example a problem where making data more accessible would solve a problem.
Remember to consult with stakeholders and future users of your tool before you build anything. See more information on conducting user research in Step 3.
Collaboration is an essential part of The Opportunity Project process. Recruit a team with diverse skills and perspectives so that you can build the best solution for your problem statement. Bring in community leaders, service providers, or people with lived experience who can act as user advocates for your end users, government agencies who can provide guidance with data sets, and a cross-functional technology team with designers and developers to build a high quality digital tool.
Include a tech team: data scientists, developers, designers, business thinkers, or anyone else who could help to build the solution.
Reach out to government policy and data experts who may be able to help shape your problem statement or design of your product.
Include User Advocates who work directly on issues related to your challenge, and who work closely with your end-users -- or even better, people who experience the problem directly.
Identify team members who can lead user research, like people who have experience with user-centered design. Everyone should try to ensure the project stays focused on the user and their needs.
Tip: think early about who will maintain the tool once it's built and who will make sure it gets into the hands of end-users. You may want to identify someone on the team who is responsible for determining how to make your solution sustainable.
Link end-users with federal agencies and tech teams and ensure that problem statements and tools meet real needs in the target community
Help to focus TOP on critical challenges facing members of the public
Lead the development of digital solutions, and envision how data and technology can solve problems
Collaborate directly with end users throughout the entire process to identify user needs, agree on a use case for your product that will best serve a real problem for the target audience, and ask for ongoing user feedback while you're developing the product. By building alongside your end-users, you can create a product that will better serve their needs. At the beginning of the process, try to answer questions like "How do people experience the problem?" "Do they have any tools to help them currently?" "What are the gaps that exist in their current tools?" and "What tools do users wish they had?"
Conduct interviews with user advocates, or work with user advocates to set up conversations with your end-users to better learn about their needs, constraints, and preferences for digital tools. If you're working with a user advocate that does community outreach, learn how they connect with their audience and any challenges they run into.
Consider other methods, like facilitating a design workshop at the start of the sprint to bring user advocates into one room to brainstorm together.
Create a detailed use-case to narrow down a broad problem statement to a specific user-driven issue to tackle.
Use the user-scenarios as examples of user-generated data. You may want to work with user advocates and end users to create similar scenarios that provide a detailed picture of the problem you're tackling.
See more user scenarios
Once you have defined the problem from the end user's perspective, dig into data to find information that could help to solve the problem. To help you find and use federal and local government data, we pulled together some of the best and most relevant open data sets about economic opportunity, such as job locations, transportation, affordable housing, health care facilities, and schools.
Determine what data could address the end-user needs you identified in your user research. For example, if your user research showed you that youth experiencing homelessness need to access information on shelters and job opportunities through Wi-Fi on their phones, you may want to build a web app and use local government data on library locations, public Wi-Fi hotspots, and shelters.
Identify key characteristics of the data sets you need, such as the level of granularity (e.g., you may need neighborhood or address level information, rather than city level, for the data to be useful) or frequency. For example, when building a product to help individuals search for jobs, very frequently updated data would be the most useful.
Connect with a federal or local government agency who can act as a data steward for your project. Many data sets are owned by agencies who understand the data in detail and will be able to answer relevant questions.
Use the resources listed below as a starting point to find your data sets.
Pro tip for techies: Cut down on data discovery time by using existing tools, wrappers, and tutorials. Check out the list provided in the resources list below. Have questions or feedback about the data? Let us know on GitHub.
Browse federal and local data sets with neighborhood-level information on economic opportunities and local resources, and download a metadata file with more information on the year and format of the data, as well as a short, plain-language description of the data set's content.
Federal Data: Find information for the whole nation on poverty, employment, school equity, transit safety, and much more.
Local Data: Find neighborhood level information on things like homelessness, parks, crime, and healthy corner stores
Topic | Description |
---|---|
311 | 311 service requests |
City services | |
Code enforcement | Environmental code violations |
Crime | Public safety data sets |
Parcels and addresses | Arrests |
Permits | Housing permits |
Propertise with permits obtained for work exceeding $50,000 | |
Preschool/daycare | Child family health and wellbeing data sets |
Privately owned assets | Restaurants |
Publicly owned land | Culture and arts data sets |
Park locations | |
Vacant buildings | |
Schools | 2010-2013 school data |
Transit | Transportation data sets |
Zoning | Zoning boundaries |
Topic | Description |
---|---|
311 | 311 service requests |
Addresses | Address points for all city addresses |
Community Survey | Summary results from 2012-2015 community survey |
Parcels | Parcels with assessor data |
Permits | All city permits |
Topic | Description |
---|---|
311 | Submitted issues |
Code enforcement | Blight violation locations |
Crime | Public safety data sets |
Parcels and addresses | Property and parcels |
Permits | Permits |
Preschool/daycare | Childcare locations (licensed or registered providers) |
Privately owned assets | Churches |
Full-line grocery stores | |
Hospitals | |
Recreation centers | |
Publicly owned land | Parks |
Public libraries | |
Vacant lot sales | |
Schools | School locations |
Schools with average commute | |
Transit | Bike lanes |
Bus routes | |
Smart bus routes | |
Zoning | Detroit zoning |
Topic | Description |
---|---|
311 | Service cases |
Code enforcement | Violations and investigations |
Crime | IMPD Citizen Complaints |
Permits | Building permits |
Topic | Description |
---|---|
311 | 311 Call for service requests |
Code enforcement | Code violations |
Crime | 2014 Crime data |
Parcels and addresses | Solid waste management |
Permits | 2014 building permits |
Preschool | Daycare regulations |
Privately owned assets | Resturants |
Publicly owned land | Vacants |
Schools | School locations and attributes |
Transit | Bike KC Survey results |
KCATA bus stops | |
Zoning | Zoning code information |
Topic | Description |
---|---|
311 | Rate of 311 call resolution |
Code enforcement | Hearings |
Inspections | |
Crime | Crimes |
Homelessness | Point in Time count |
Parcels and addresses | Calls for service |
Permits | Building permits |
Preschool/daycare | Building preschool/daycare |
Privately owned assets | Grocery stores |
Restaurants | |
Publicly owned land | Land use of nolas blight/nola-land |
Schools | HS graduation rates |
Letter grade of schools 2009-present | |
Location of K-12 schools | |
Special Events | Mardi Gras Parade Routes - Daily Routes (2016) |
Transit | Travel time to work |
Zoning | Zoning districts |
Topic | Description |
---|---|
311 | 311 service requests |
Code enforcement | Code violations |
Exterior violation cleanups | |
Licences and Inspections data (business licenses) | |
Properties with ownership information | |
Crime | Crime incidents |
Public safety data sets | |
Health and environment | Health Centers |
Healthy Corner Stores | |
Parcels and addresses | Property Parcels |
Snow emergency routes | |
Stormwater Billing Parcels | |
Street lane closures | |
Transportation Parcels | |
Permits | Real estate/land records |
Residential parking permits | |
Preschool/daycare | Childcare locations |
Privately owned assets | Healthy corner store locations |
Publicly owned land | City buildings |
City owned vacant property | |
Parks and Rec Out of School Programs | |
Parks and recreation | |
Parks and recreation assets | |
Schools | Education data sets |
Transit | Bike data |
Transportation data sets | |
Zoning | Planning and zoning data sets |
Zoning base districts | |
Zoning overlay districts |
Topic | Description |
---|---|
311 | Information requests |
Crime | Crime incidents |
Crime incidents map | |
Fire calls for service (responses) | |
Health and environment | Climate and health data |
Community resiliency indicator system | |
Health Care failities | |
Homelessness | 2011 Point in Time count |
Parcels and addresses | Affordable housing bonus program zoning districts and eligible parcels |
Neighborhood groups map | |
Property information | |
Permits | Registered businesses |
Stree use permits | |
Privately owned assets | Mobile food schedule |
Restaurant scores | |
Publicly owned land | Parks and open space |
Schools | SF Private Schools |
SF Public Schools | |
School crossing guards | |
Transit | Bikeway Network |
Public bicycle parking | |
Transit stop and schedule | |
Zoning | Enterprise zones |
Zoning districts |
Topic | Description |
---|---|
311 | Service requests last 30 days |
Crime/Public Safety | Crime homepage |
Incidents last 30 days | |
Health services | HIV/AIDS clinic |
Primary care facilities | |
Homelessness | Service facilities |
Shelter locations | |
Parcels and addresses | Snow removal route |
Permits | Construction permits |
Preschool/daycare | Child care locations |
Privately owned assets | Supermarket locations |
Publicly owned land | DC Parks |
National parks | |
Recreational facilities | |
Schools | Education data page |
Public schools | |
Transit | Circulator routes |
Main page | |
Signed bike routes | |
Wireless/broadband access | HUB Zones |
Wireless hotspots | |
Zoning | Planning landuse and zoning |
Supermarket tax credit zones | |
Zoning index |
See more local data sets
Search nearly 200,000 data sets from federal agencies. View the Opportunity Project collection of data sets at data.gov/opportunity.
The Opportunity Project commuity on Slack is a great place to ask questions about finding, accessing, or using data sets.
Data.world created compilation of data sets for teams in The Opportunity Project with space to share feedback on data and collaborate with others using the data. This makes it easy for educators, data scientists, everyday citizens, and students, to discuss, analyze, query, visualize, and easily share their findings.
The U.S. Census Bureau created a series of tools that make it easier to combine and use government data. You can find The Opportunity Project module on the CitySDK website.
Stack Overflow is also a great public forum to ask questions about federal and local data sets.
Once you identify a problem to tackle, the end users your tool will serve, and the data you will use, you can start building! Work collaboratively to build a digital product, including many voices as possible in the design process and seeking feedback as you design and build. Build iteratively, showcasing early versions and revising your design plans based on feedback. Remember that you don't have to build the perfect or "final" solution in 12 weeks! During this phase, we recommend the whole group communicate frequently and come together remotely or in person every 2-3 weeks to demo their works in progress, ask questions, and share feedback.
Build according to the user research. Use the data you found during data exploration.
Share the concepts, wireframes, and prototypes early and often. Revise your design and plans based on the feedback you receive.
Conduct user testing or feedback sessions to improve the product and ensure that the people who need it are aware it exists.
Develop a plan for tracking success of your tool, such as tracking number of sessions, users, or downloads via tools such as Google.
Think about how you will connect end users with your product once the tool is released: What will your team need to build into the product to as many people as possible can use it? What types of organizations do you need to work with to help connect your tool with the people it's designed to serve?
Think about how you will maintain the tool over time, or what partners you need to help you sustain and continuously update and improve the tool.
If you're interested in replicating the Opportunity Project sprint process, here is a sample week-by-week timeline. Feel free to adjust your project plan and milestones based on what works for your team.
Week 1
Choose a general problem statement to focus on.
Week 2
Connect with others to form a diverse team. Establish ways to communicate -- such a listserv, online slack channel, or in-person meetups – so that everyone can collaborate and share progress.
Week 3
Conduct user research and identify a user-driven use case for your product.
Week 4
Identify information that could help to solve the problems you identified in your user research, and then find federal and local data sets with the information you need.
Week 5
Start to sketch out a product. Share sketches, wireframes or a concept pitch to get early feedback from end users, subject matter experts, government employees, and others. Early demos of Minimum Viable Products are part of the lean start-up methodology and lead to faster value delivered to users.
Week 6-7
Continue building based on feedback received from your demo, and continue to explore data and seek ongoing input from user advocates and end users.
Week 8
Conduct another demo and share a more mature and improved version of the product you're building. Seek more feedback, particularly from end users of the tool.
Week 9-10
Keep building, and hold interactive user testing sessions. Plan how you will share the final product with end users and other stakeholders.
Week 11-12
Get everyone involved in the process together to launch the final prototypes or Minimum Viable Products (MVPs).
Beyond the sprint: Continue to improve the tools, share the product with the target end users, and measure your impact.
At the end of your sprint, or when you're ready to launch a prototype or "MVP" of your product, get the word out and make sure people know about the product you built so that they can use it! Share your product with everyone who will be interested. Stakeholders might include:
o People who you designed the tool for — the end users.
o Organizations who can help share or scale the tool.
o Other teams in The Opportunity Project community.
o Local government or other organizations that collect and maintain the data you used.
There are many ways to spread the world, like social media, in person events, outreach through user advocates, and more. The Opportunity Project launches multiple tools at once, through coordinated events that incorporate in-person, online, and social media channels. Coordinating with user advocates is a great way to share your product with the intended end users through their outreach platforms. For example, if you worked with a veteran service provider to build a tool for veterans, you may be able to share your tool directly through their online presence or organization.
Consider hosting an event to showcase your product
Use press and social media to spread the word! Use #OpportunityProject.
Create a plan with user advocates to share your product with end-users in the community
Share your code! We highly encourage you to make your projects open source and free for use by the public. A local tool in Baltimore, MD can be used in Austin, Texas, just by using different data sources!
Your launch is just the beginning! After you launch your product and work with user advocates and other groups to deploy it to the target end users, keep building and seeking ongoing feedback to continuously improve your product. After the sprint, be sure you have a plan for how this product will live on after it is built. Will you maintain it? Do you need another organization to help sustain it? Will you hand off the code to another group for sustainability? Look to user advocates and local organizations who may be helpful partners in sustaining the tool.
Make use of the tools you put in place to track impact, like Google Analytics, to measure success of the tool. Gather numbers on users, downloads, or other metrics, and stories from users on how they are using the product. Share what you learn with The Opportunity Project community on Slack.
Share feedback on the data you used, or data you needed but couldn't find - this is critical to improving data quality and accessibility for you and other data consumers! Help us to improve by providing feedback on your experience using this toolkit.
Keep building and improving.
Ask technical team members for a commitment to routine maintenance and improvements to the product. Talk to user advocates and other stakeholders about organizations that might want to help with sustainability.
Measure your impact: Collect information on things like page views and number of users through Google Analytics, outcomes and how your tool is helping individuals and communities.
Share information on your experience using this toolkit with the whole Opportunity Project community on Slack. Use the #datafeedback channel to share feedback on things like data availability, access, quality, or formats with data stewards.
Help us improve this content.