# Brigade to Brigade Communication - Oct. 20 2018 - Brigade Congress

**URL:** <https://discourse.codeforamerica.org/t/brigade-to-brigade-communication-oct-20-2018-brigade-congress/309>\
**Category:** Partnerships\
**Tags:** brigadecongress-2018\
**Created:** [October 20, 2018, 6:23pm UTC](https://discourse.codeforamerica.org/t/brigade-to-brigade-communication-oct-20-2018-brigade-congress/309 "2018-10-20T18:23:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JBStephens](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/jbstephens/32/75_2.png) [@JBStephens](https://discourse.codeforamerica.org/u/JBStephens)\
**Post date:** [October 20, 2018, 6:23pm UTC](https://discourse.codeforamerica.org/t/brigade-to-brigade-communication-oct-20-2018-brigade-congress/309/1 "2018-10-20T18:23:11Z")

</div>

**Brigade-to-Brigade Communication and Support**

**2018 Brigade Congress - Saturday, October 20**  
John Stephens, Code for Durham

Effective sharing of information and expertise helps every Brigade stay connected, efficient, and informed about a wide range of civic tech projects. An assessment of communication methods (online and otherwise) is the starting point. PURPOSE: identify effective ways for Brigades to communicate, collaborate, and support one another.

**STARTING OFF – INDIVIDUAL REFLECTIONS**

1. What are 2-3 best ways that your brigade has communicated with other brigades?

2. What do you see as communication glitches or barriers to brigade-brigade interaction?

3. One idea for action to improve brigade-brigade communication?

**GROUP DISCUSSION**

Review of communication avenues (about 15 minutes): Pros and Cons; Ideas for improvement

Slack

Discourse

GitHub

Webinars

CFA HQ staff as catalysts and intermediaries – e.g. This Week in Civic Tech

Google Docs (often done by CFA HQ staff)

Face-to-face gatherings (Brigade Congress, Brigade Day at CFA Summit, other meetings)

More bilateral, short-term exchanges – email, text, phone

Other

**Open Discussion and/or Smaller Groups - Action items for**

- Improving existing communication and support mechanisms
- Ideas for new methods of communication/support
- Who is willing to work on changes, improvements?

Worksheet

**Brigade-to-Brigade Communication and Support**

Name (Optional):

Brigade (or other Organization):

What are 2-3 best ways that your brigade has communicated with other brigades?

What do you see as communication glitches or barriers to brigade-brigade interaction?

One idea for action to improve brigade-brigade communication?

Other comment?

Can return in person or to: John B. Stephens (Code for Durham) [stephens@sog.unc.edu](mailto:stephens@sog.unc.edu)

**Brigade-to-Brigade Communication**

| | **Pros** | **Cons** | **Ways to Improve** |
| --- | --- | --- | --- |
| Slack | | | |
| Discourse | | | |
| GitHub | | | |
| | | | |
| | **Pros** | **Cons** | **Ways to Improve** |
| Webinars | | | |
| CFA HQ staff catalysts and intermediaries | | | |
| Google Docs | | | |
| | | | |

| | **Pros** | **Cons** | **Ways to Improve** |
| --- | --- | --- | --- |
| Bilateral, short-term exchanges – (email, text, phone) | | | |
| Face-to-face gatherings | | | |

Brigade Congress,

Brigade Day at CFA Summit

Other meetings||||  
|Other?||||

---

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [July 1, 2023, 6:53am UTC](https://discourse.codeforamerica.org/t/brigade-to-brigade-communication-oct-20-2018-brigade-congress/309/2 "2023-07-01T06:53:57Z")

</div>