Evaluation of the Strong Cities, Strong Communities (SC2) Teams Pilot: Final Report. 3.2.1 Communication Within the SC2 Team


Communication within the SC2 teams typically followed a hub-and-spoke structure, with the SC2 team lead serving as the hub. SC2 team leads communicated frequently with individual team members, either through organized team meetings or as the need arose. Every site had team meetings, but the frequency and formality of meetings varied by site. Among the six SC2 teams, three had weekly calls or emails, one had quarterly in-person meetings, and two rarely met as a group, instead preferring a more informal flow of calls or emails. In cities where SC2 team members met regularly, some members said the meetings helped them stay engaged and focused on city priorities, and fostered an atmosphere of teamwork. However, other team members found the team meetings to be perfunctory, doing little to enhance their work or the SC2 experience.

Over time, formal team communication became less frequent in most cities, for two main reasons. First, as team members gained a clearer understanding of their roles and how to successfully operationalize their work, broader team input became less necessary in most cities. Second, some team members, particularly part-time remote members who were playing minor roles on the teams, became less engaged in the pilot overall.

In places where regular, collaborative team meetings occurred frequently in the beginning of the pilot and gradually became less frequent, a few team members said they missed the meetings and wanted more regular team contact. SC2 team leads also expressed interest in more in-person meetings with their respective teams, as well as with other SC2 team leads and with the Council.

View full report


"rpt_SC2FinalReport.pdf" (pdf, 2.78Mb)

Note: Documents in PDF format require the Adobe Acrobat Reader®. If you experience problems with PDF documents, please download the latest version of the Reader®