MétaCan
Menu
Back to cohort
Record W3011548789 · doi:10.1002/ev.20398

Finding the Impact: Methods for Assessing the Contribution of Collective Impact to Systems and Population Change in a Multi‐Site Study

2020· article· en· W3011548789 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueNew Directions for Evaluation · 2020
Typearticle
Languageen
FieldDecision Sciences
TopicEvaluation and Performance Assessment
Canadian institutionsImpact
Fundersnot available
KeywordsScale (ratio)Context (archaeology)InterimPopulationWork (physics)SPARK (programming language)Management scienceComputer sciencePolitical scienceSociologyEngineering

Abstract

fetched live from OpenAlex

Abstract John Kania and Mark Kramer put forward “Collective Impact” in 2011 as a framework for organizing multi‐sector collaborative efforts to achieve change at scale. The collective impact theory of change posits that by establishing and implementing its five conditions, groups can achieve meaningful systems changes to create long‐term gains in social and environmental conditions. While significant scale uptake has occurred, questions have remained about the degree to which collective impact, as an approach, actually works to achieve change at scale. In 2017, ORS Impact and Spark Policy Institute embarked on an evaluation effort to understand the degree to which the collective impact approach contributed to population‐level change across many sites. We sought to answer this question with as much rigor as possible, without attempting to simplify the complexity of the context, the variability of implementation of collective impact, or the many interim changes needed to see the impact at scale. This chapter shares the essential methods our research team used. We do not seek to share the findings; instead, we hope that others can learn from and use these methods to continue to strengthen the sector's understanding of when, how, and why different collaborative efforts work or do not. In addition to describing the key methods, the authors will reflect on considerations, lessons learned, and recommendations to other evaluators who might seek to answer similar questions or use similar tools and methods.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.018
metaresearch head score (Gemma)0.010
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.429
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0180.010
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.562
GPT teacher head0.672
Teacher spread0.109 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it