Hello Justin,
Thanks for your public request for feedback on how to improve some of the federal communities of practice. It's great to see that many of them have strong momentum.
From what I can tell from the link you shared, most of these communities are based around email discussion lists. Email lists are certainly useful and easy for people to use, however I would recommend making several other tools available for each of these communities.
1. Video Chats: There's no better way to build deep member-to-member relationships online. A community is the sum of its relationships.
2. Shared Calendar: This makes it easier for people to know about upcoming in-person and online events while reducing email traffic.
3. Weekly Email Newsletters: Letting each member share one link per week is an efficient way to distribute a large amount of information while further reducing email traffic.
4. Slack: Live written chat is a great complement to email discussion lists when certain conversation topics require many rounds of quick back-and-forth. I've built a "standup" bot where community members share what they're working on and whether they have any obstacles, just like agile software teams often do. With Slack's interface for building bots, the sky is the limit.
For the past year, I've been experimenting with integrating all of these tools. Here's an
example community for civic innovation (90 members) and the corresponding
Slack community (146 members) that it is integrated with at an app-to-app (API) level. We hosted an
online conference with video breakout rooms last week with 45 registrants and as you're well aware the unconference format is very empowering for in-person and online communities (so I'd say that your communities should each try hosting one).
Being very transparent, I'd love to help stand up some new communities for the GSA; please let me know if I can help.
Lucas Cioffi
Founder, QiqoChat
Founder, Civic Tech Code School
Charlottesville, VA