Skip to content
Civic Tech DCThe project playbook

Navigating Project Challenges

OpenDataGov project

Civic Tech DC projects are built by people generously volunteering their time, often alongside full-time life commitments. Unlike traditional workplaces, project teams don’t have formal reporting structures or guaranteed availability.

Challenges are a normal part of volunteer-led work, but how your team responds to them matters. Addressing issues early, communicating openly, and being realistic about what people can contribute can help prevent small frustrations from becoming larger problems.

This guide covers some common challenges project teams may encounter and offers practical ways to work through them.

Volunteer participation fluctuates. Someone might attend three Project Nights in a row and then disappear for a month. Others may be enthusiastic about joining but never make their first contribution.

What you can do:

Check in without creating pressure: A friendly Slack message to check in on how someone is doing can go a long way. Give them the flexibility to step away when needed without feeling guilty.

Make it easy to return: Keep project documentation and tasks up to date so contributors can pick things back up without having to catch up on weeks of conversations.

Avoid depending on one person: Document important decisions and make sure more than one person understands key parts of the project.

2. When Contributors Disagree on Project Direction

Section titled “2. When Contributors Disagree on Project Direction”

A developer might want to rebuild a tool using a different framework, while a community partner wants to focus on making the existing version easier to use. Disagreement itself isn’t necessarily a problem, as it can lead to better decisions, but always give people space to explain their reasoning.

What you can do:

Return to the problem. Ask who the project is intended to serve and whether the proposed direction addresses their needs. Separate preferences from requirements. A particular approach may be someone’s preference rather than something the project actually needs.

Make decisions transparent. Explain how a decision was reached, particularly when not everyone’s preferred approach is chosen. Clarify decision-making responsibilities.

Know when to involve organizers. If a disagreement becomes personal, repeatedly disrupts work, or cannot be resolved within the team, reach out to Civic Tech DC organizers.

Disagreements about technical choices or project priorities are different from harassment, discrimination, or other violations of our Code of Conduct. Those concerns should be brought to the organizers.

3. When Your Project Keeps Growing in Scope

Section titled “3. When Your Project Keeps Growing in Scope”

It’s exciting when a project grows beyond its original goals. Take CIB Mango Tree, for example, which has expanded into developing a suite of tools for its library! New ideas are always coming up, but taking on too much at once can make it stressful and harder to finish.

What you can do:

  • Revisit your original goals: Does this new feature help solve the problem you set out to address, or is it just something that would be nice to have?
  • Save ideas for later: Keep a running list of features you’d like to explore without feeling like you need to build everything right away.
  • Talk about tradeoffs: If you add something new, what else might need to wait?

Volunteer projects depend on people’s enthusiasm, but enthusiasm alone cannot sustain a project indefinitely. Burnout can emerge when a few contributors take on most of the work or people feel pressured to meet expectations they never formally agreed to.

What you can do:

Normalize taking breaks. Contributors should feel comfortable stepping away or reducing their involvement without having to justify themselves.

Set realistic expectations. A project that meets twice a month moves much more slowly than a team in a giant business. And that is okay!

Celebrate progress beyond launches. Completing a user interview, documenting a process, or helping someone make their first contribution are all meaningful milestones.

HAVE FUN! Remember, a project is more than just volunteering; it is about bringing the community together.

Example: When a Project Starts Losing Momentum

Section titled “Example: When a Project Starts Losing Momentum”

This is a hypothetical scenario.

A civic tech project starts with eight interested volunteers. The team meets regularly, sets up a repository, and begins building a prototype. A few months later, only two contributors are attending consistently. The project lead has taken on most of the unfinished work, and the community partner is still waiting for an update.

The team could recruit more volunteers or find someone else to take over. But to figure out the next best steps, the team:

  1. Check in with contributors: Reach out to see who’s still interested and whether anyone needs help getting involved again.
  2. Reassess the scope: Identify one smaller outcome the remaining contributors could realistically finish instead of trying to complete the entire prototype.
  3. Talk with the community partner: Explain where things stand and ask whether a smaller deliverable would still be useful.
  4. Share responsibilities: See if someone else can help coordinate meetings or manage tasks. If no one has capacity, reach out to Civic Tech DC organizers for support.
  5. Agree on next steps: Focus on the smaller deliverable for the next month, then decide together whether to continue, recruit more help, or pause.

What can we learn? The problem wasn’t that volunteers stopped showing up but that the project’s original expectations no longer matched the time people had available. By checking in, the team has a better chance of moving forward.

A project might achieve its original purpose, lose its community partner, or reach a point where no one has the capacity to maintain it. Pausing or closing a project isn’t a failure. What matters is making that decision thoughtfully and preserving useful work where possible. If your team is considering whether to continue, transfer, or close a project, see our Passing the Torch guide.