relevanssi domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/diqosbmy/public_html/clients/strive-together/wp-includes/functions.php on line 6131WordPress database error: [Table 'diqosbmy_WP6WS.6EN_ppress_plans' doesn't exist]SELECT COUNT(id) FROM 6EN_ppress_plans WHERE status = 'true'
ninja-forms-uploads domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/diqosbmy/public_html/clients/strive-together/wp-includes/functions.php on line 6131ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/diqosbmy/public_html/clients/strive-together/wp-includes/functions.php on line 6131better-wp-security domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/diqosbmy/public_html/clients/strive-together/wp-includes/functions.php on line 6131updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/diqosbmy/public_html/clients/strive-together/wp-includes/functions.php on line 6131As communities across the country engage in collective impact generally and the work of building cradle-to-career civic infrastructure specifically, one of the first issues that always comes up is stress and tension around the selection of a “backbone organization.” This is a core component of the work that Kania and Kramer lifted up in the original Stanford Social Innovation Review article<\/a>. While we could not agree more that there is a need for the concept that is described, the power struggles that often occur among the various entities that want to play this role often get in the way of progress and can derail an effort early on as historical issues of turf quickly emerge.<\/p>\n We are learning that the concept of a single backbone organization may very well be flawed. This has become clear as we worked with an array of different communities looking to navigate the often contentious discussions around where the organization should land. Most of time, the different organizations engaged in these discussions locally bring very different skills, interests and competencies to the table. Sometimes they have a unique leader who could play the central executive director or “cat herder”<\/a> role effectively. Others, they have the capacity to do the critical data analytics. Still other times, they may really be interested in moving one or two outcomes, say early childhood and early grade reading alone, not the entire continuum of outcomes.<\/p>\n This has led us to the conclusion that what is likely needed is a “backbone function,” not a “backbone organization.” This may simply sound like semantics, but it leads to a completely different way to approaching the staffing of collective impact work. This shift helps us to see that this work is not about a central power center that gets created in a traditional hierarchical paradigm, but instead is about a set of shared roles that need to be played as we look to connect the dots instead of recreate the wheel. These roles, which simply have to be played by a host of organizations since no one new organization can lead collective impact work alone, include:<\/p>\n There are certainly other roles that emerge over time and need to be played, but this is a start. And if we see that a host of organizations working in concert all can contribute to the overall backbone function any community needs to have played, it can and should reduce some of the power struggles that have emerged around this important piece of the work.<\/p>\n We have learned one additional lesson that deserves to be mentioned.\u00a0 It is helpful, especially early in this work, to have all the key staff located in the same place even if they come from different organizations. The importance of these staff sharing what they are learning on a daily basis, helps them practice the type of continuous improvement they are looking to promote across community partners. The simple reality is there will be a need for a fiscal agent and they have to sit somewhere. We recommend communities not create a new 501(c)(3) to house the staff since this work is primarily about leverage existing resources. We term wherever they land as the “anchor entity,” but whatever it is called, it need not cause conflict since it should become clear very quickly that there is joint ownership for the backbone function as a whole.<\/p>\n\n