Logic Model (Program Evaluation)¶
A program representation linking resources and activities to outputs, outcomes, and intended impact through explicit assumptions.
Core Idea¶
A logic model in program evaluation is an explicit representation of how a program is expected to turn resources into activities, direct outputs, short- and longer-term outcomes, and broader impact. It records the program’s theory and assumptions in a form that connects implementation with intended change. The widely used W. K. Kellogg Foundation guide organizes the basic model as resources/inputs, activities, outputs, outcomes, and impact, while also emphasizing assumptions and external factors.
The arrows are hypotheses, not proof. A logic model says what must happen, in what plausible sequence, and what could be measured if the program works as intended. Evaluators use it to choose implementation indicators, outcome questions, and places where causal links might fail.
Scope of Application¶
Logic models are used in public health, education, community development, nonprofit programs, public administration, and grantmaking. They can describe a small intervention, a multi-part initiative, or a policy implementation system. Different models may emphasize activities, outcomes, or underlying theory, but the program-to-result linkage remains.
They are especially useful during design, stakeholder alignment, evaluation planning, and revision. A mature model can attach indicators, data sources, timing, and responsibility to each role. Complex systems may require branching feedback and multiple actor pathways; a single left-to-right row can be inadequate, but it can still serve as a summary if assumptions and dependencies remain visible.
Clarity¶
The structure prevents a common category error: counting services as if they were social change. “Twenty workshops delivered” is an output. “Participants use the taught practice” is an outcome. “Population-level harm declines” is a longer-term impact. Moving between these levels requires assumptions about reach, quality, adoption, context, and persistence.
Manages Complexity¶
A program can involve many staff, services, populations, and intended effects. The logic model compresses them into a shared causal-and-operational map. Teams can locate disagreements, avoid collecting indicators unrelated to decisions, and distinguish implementation failure from theory failure. Funders and communities can inspect what is being promised.
Abstract Reasoning¶
The representation supports conditional reasoning. If an activity was not delivered, failure of a downstream outcome does not by itself refute the change hypothesis; implementation broke first. If outputs were delivered but proximal outcomes did not change, the activity-to-outcome link or its assumptions deserve scrutiny. If proximal outcomes changed but impact did not, later links or external factors may dominate.
Knowledge Transfer¶
The role vocabulary transfers literally across program domains. A school attendance intervention and a vaccination outreach program both distinguish resources, activities, outputs, outcomes, and impact, though their content differs. Teams can reuse elicitation questions and validation procedures.
The broader transferable skeleton is Problem Representation or Causal Chain. Outside program evaluation, these parents may organize mechanisms and goals. Calling any product roadmap a logic model is warranted only if it explicitly connects actions to measured outputs and downstream outcomes through assumptions.
Relationships to Other Abstractions¶
Current abstraction Logic Model (Program Evaluation) Domain-specific
Parents (1) — more general patterns this builds on
-
Logic Model (Program Evaluation) is a kind of Problem Representation Prime
Logic Model specializes Problem Representation by organizing a program’s need, intervention, and intended results.
Hierarchy path (1) — routes to 1 parentless root
- Logic Model (Program Evaluation) → Problem Representation → Representation → Abstraction
Neighborhood in Abstraction Space¶
Logic Model (Program Evaluation) sits in a sparse region of the domain-specific corpus (88th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Results-Based Management — 0.80
- Sequence Diagram — 0.80
- RDA: Resource Description and Access — 0.79
- Entrepreneurship — 0.79
- Autocausative Verb — 0.79
Computed from structural-signature embeddings · 2026-09-08