Collective impact rests on five conditions - and shared measurement is the one that breaks. Sopact reads every partner's data against one shared framework.
Collective impact is a structured approach to social change in which organizations from different sectors commit to a common agenda and coordinate their efforts to solve a complex problem no single actor can solve alone. It rests on five conditions: a common agenda, shared measurement, mutually reinforcing activities, continuous communication, and a backbone organization to coordinate the work. The framework is well established; the condition that decides whether it works is shared measurement.
The condition partners consistently underestimate is shared measurement. Every organization arrives with its own definitions, its own tools, and its own reporting, and the common agenda quietly fractures the moment two partners count the same outcome differently. A collective impact effort with a beautiful common agenda and no shared measurement is a coalition that agrees on the goal and cannot agree on the numbers.
Key takeaways
The five conditions of collective impact were named by John Kania and Mark Kramer, and the one that fails most often in practice is shared measurement. A common agenda is a document partners can sign; shared measurement is an infrastructure they have to build. Without it, each partner reports its own numbers in its own format, the backbone stitches incompatible spreadsheets, and the collective cannot say what it achieved together.
Sopact calls the fix Continuous Shared Measurement: one data dictionary and one participant identity shared across every partner, so an outcome means the same thing whether it was collected by the workforce partner or the housing partner, and the collective roll-up is a query. The measurement practice this sits inside is on the impact measurement page, and the shared causal logic on theory of change.
The framework itself belongs to the field — Kania and Kramer introduced it in the Stanford Social Innovation Review, and the IRIS+ catalog can supply the shared metric definitions. What Sopact adds is the layer that makes shared measurement continuous rather than an annual reconciliation, with the place-based version on community impact.
You build shared measurement by agreeing one data dictionary across partners, assigning a participant identity that persists across organizations, aligning each partner's collection to the shared definitions, and reading the roll-up continuously rather than at an annual convening. The common agenda names the goal; shared measurement is what lets the collective know it.
The table names the five conditions and, for each, where it breaks and what a shared infrastructure requires — so the collective's hardest condition becomes an asset rather than its failure point.
Collective impact rests on five conditions, and shared measurement is the one that most often breaks. Read the last column: what each condition requires to hold across partners.
| Condition | What it requires | Where it breaks |
|---|---|---|
| Common agenda | A shared goal and definition of the problem | Signed but not operationalized into metrics |
| Shared measurement | One data dictionary and identity across partners | Each partner counts outcomes its own way |
| Mutually reinforcing activities | Coordinated, differentiated roles | Overlap and gaps no one can see without shared data |
| Continuous communication | Regular, evidence-based alignment | Meetings without current, comparable numbers |
| Backbone support | A team to coordinate and integrate | One layer to roll up, not five incompatible feeds |
Read the last column and shared measurement is the hinge: mutually reinforcing activities cannot be seen, continuous communication has nothing to align on, and the backbone has nothing to roll up without it. Continuous Shared Measurement — one dictionary, one identity across partners — is what lets the other four conditions hold.
When a collective's shared data is assembled once a year, partners align on a picture that is already stale and cannot course-correct together. Reading the shared roll-up as data arrives lets the collective adjust while the work is still underway. That is the premise of the Loop, Sopact's method for continuous impact intelligence: collect clean at the source, analyze the moment data arrives, improve while you can still act.
The Loop is also what makes a collective's claim defensible. Every shared figure traces back to the partner and the response it came from, so a collective outcome resolves to its source. That standard has its own chapter in traceability and transparency.
One method, three moves that never stop
Then the cycle runs again, a little sharper each cycle. Read the method: the Loop methodology →
The fastest way to make shared measurement real is to agree one definition across two partners. Each prompt below pastes into Sopact Sense's Assistant, or reasons through with your team; the arrow above each links the Academy walkthrough that shows the expected output and the tips.
Academy walkthrough → Agree a shared data dictionary
For this collective's common agenda, build a shared data dictionary every partner uses: [PASTE AGENDA + PARTNER OUTCOMES]. For each shared outcome give the definition, the unit, the allowed values, and the identity rule across organizations. Flag where two partners currently define the same outcome differently. Return a table.
Academy walkthrough → Connect partners on one identity
Design how a participant served by two partners resolves to one shared record: [PASTE PARTNER FLOWS]. Specify the identity rule, the consent handling, and how each partner's quantitative and qualitative data joins. Flag where the identity would break. Return the design.
Academy walkthrough → Trace the collective roll-up
For each figure in the collective's shared report, build a source row: the number, which partner and responses it came from, and the calculation. If a figure double-counts a participant served by two partners, flag it. Return a table: Figure / Partner / Source / De-dup.
Academy walkthrough → Align partner collection
For each partner in this collective, check whether its collection matches the shared dictionary: [PASTE DICTIONARY + PARTNER INSTRUMENTS]. Flag every field a partner collects differently and propose the fix so the shared measurement holds. Return the gaps and fixes per partner.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: what's changing in shared measurement — the collective-impact condition that decides whether the rest hold.
Collective impact is a structured approach in which cross-sector organizations commit to a common agenda and coordinate to solve a complex problem no single actor can solve alone, on five conditions: a common agenda, shared measurement, mutually reinforcing activities, continuous communication, and a backbone organization. In Sopact's framing, the condition that decides success is Continuous Shared Measurement across every partner.
A common agenda, shared measurement, mutually reinforcing activities, continuous communication, and backbone support. They were introduced by John Kania and Mark Kramer in the Stanford Social Innovation Review. Shared measurement is the condition that most often breaks, because it requires partners to build a common measurement infrastructure, not just sign a shared goal. Sopact provides that layer.
Shared measurement means every partner collects and reports outcomes against the same definitions, so the collective can say what it achieved together rather than stitching incompatible spreadsheets. Without it, the common agenda fractures at the numbers. Sopact's Continuous Shared Measurement gives partners one data dictionary and one participant identity, so an outcome means the same thing across organizations.
Most often at shared measurement: partners keep their own definitions and tools, the backbone cannot reconcile incompatible reports, and the collective cannot demonstrate joint results. A common agenda without shared measurement is a coalition that agrees on the goal and cannot agree on the numbers. Sopact makes shared measurement continuous, which is what lets the other four conditions hold.
Collective impact software supports the backbone's coordination and, crucially, the shared measurement across partners — one dictionary, one participant identity, a roll-up that de-duplicates participants served by multiple partners. Generic tools leave each partner in its own silo. Sopact keeps the collective on one shared record, so the roll-up is a query rather than an annual reconciliation.
One shared measurement layer, not five incompatible partner feeds: a common data dictionary, a participant identity that persists across organizations, and a roll-up that reads continuously. Reconciling exports by hand is where a backbone loses its capacity. Sopact gives the backbone Continuous Shared Measurement, so integration is a standing capability rather than a year-end project.
Collective impact is the cross-sector coordination model for a complex problem; community impact is the place-based change in a specific community, covered on the community impact page. They overlap when a collective operates in one place. Sopact keeps both on shared, traceable measurement, so a collective and its community outcomes draw from the same evidence.
Next: see the place-based version on the community impact page, or the measurement practice on the impact measurement page.
