MétaCan
Menu
Back to cohort
Record W2063290014 · doi:10.1177/1098214012464426

Improving Program Results Through the Use of Predictive Operational Performance Indicators

2013· article· en· W2063290014 on OpenAlexaffabout
Maria Barrados, Julie Blain

Bibliographic record

VenueAmerican Journal of Evaluation · 2013
Typearticle
Languageen
FieldDecision Sciences
TopicEvaluation and Performance Assessment
Canadian institutionsEmployment and Social Development CanadaCarleton University
Fundersnot available
KeywordsAccountabilityContext (archaeology)Performance indicatorProgram evaluationProcess managementQuality (philosophy)Computer scienceRisk analysis (engineering)Term (time)Operations managementEnvironmental economicsBusinessEngineeringMarketingEconomicsPolitical sciencePublic administration

Abstract

fetched live from OpenAlex

In Canada, in-depth evaluations of federal programs are intended to occur every 5 years. As such, evaluation is a periodic retrospective (lag) indicator examining results achieved versus program objectives. In a Canadian context, stand-alone evaluations have proved challenging to implement, time consuming, and not well adapted to annual management accountability needs. Consequently, there are important benefits from developing parallel ongoing operational performance measurements, complementing periodic evaluations as an integrated system. With links to program evaluations, ongoing performance feedback can include predictive (lead) indicators of progress, through operational linkages to a program’s intended long-term outcomes. The present case study examines program efficiency concerns demonstrating lead indicators as an “early warning system”—targeting problem areas, producing speedier program adjustments (including accountability and efficiency improvements) and also demonstrating potential to increase quality, timeliness, and usefulness of longer term in-depth evaluations.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.058
metaresearch head score (Gemma)0.118
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.058
Threshold uncertainty score0.307

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0580.118
Meta-epidemiology (narrow)0.0020.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0100.009
Science and technology studies0.0010.001
Scholarly communication0.0070.005
Open science0.0010.003
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0020.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.186
GPT teacher head0.471
Teacher spread0.286 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations7
Published2013
Admission routes2
Has abstractyes

Explore more

Same venueAmerican Journal of EvaluationSame topicEvaluation and Performance AssessmentFrench-language works237,207