Evaluation of the Strong Cities, Strong Communities (SC2) Teams Pilot: Final Report. 3.2.3 SC2 Team Communication Between Team Members and Cities

08/25/2014

At the outset of the engagements, SC2 team leads tended to serve as the primary liaison between team members and city representatives. Most cities had a main point of contact to represent the city—either appointed by the mayor or, in some cases, the mayor him/herself—and that person and the SC2 team lead communicated frequently and informally. There were also formal communication structures in most cities, such as weekly, monthly, or quarterly meetings to check in on progress and align goals.

Over time, many individual team members developed relationships with city staff who were engaged in work being conducted by SC2 teams. These members began communicating directly with their city counterparts rather than routing through the SC2 team and city leads. In one city, this informal communication was aided by the fact that both the SC2 team lead and all full-time team members were given desks in city hall, making them readily accessible to city  government. Team member-city staff relationship building was facilitated in two other cities by more formal mechanisms—in one city staff and the entire SC2 team met quarterly to discuss their partnered work; in the other team members held weekly office hours, hoping to streamline communication with city staff.

While many one-on-one relationships were formed, local political circumstances and city staff turnover limited one-on-one working relationships between team members and city government officials other than the city’s executive in at least two communities.

 

View full report

Preview
Download

"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®