34. Introduction to Logic Models
By the end you'll be able to
- Define the six standard components of a logic model and the order they appear in.
- Explain why reverse-engineering from impact back to inputs produces stronger design than starting with activities.
- Recognize the "activity trap" and the warning signs of a weak causal chain.
- Articulate to a reviewer why a one-page logic model is a feasibility test, not a decoration.
A logic model is the blueprint that proves your program will actually work. It is a one-page visual map that traces a straight line from the resources you invest, through the activities you run, to the changes you intend to produce in participants and conditions. In this lesson you learn why logic models exist, what reviewers look for when they scan them, and why the absence of a clean causal chain is the single biggest reason that otherwise-good proposals score poorly on feasibility and methodology.
You will also confront the activity trap, the pattern where organizations can describe what they do in vivid detail but cannot explain why it works. Proposals that list workshops, screenings, and outreach events without connecting them to specific outcomes leave reviewers guessing. A logic model forces clarity. If you cannot diagram it on one page, you probably cannot deliver it in the field, and a sharp reviewer will catch the gap.
By the end you should be able to define the six standard components (inputs, activities, outputs, short-term outcomes, intermediate outcomes, long-term outcomes), explain how they connect, and articulate why reverse-engineering from impact back to inputs produces stronger program design than starting with a list of activities you already enjoy running.
Common mistakes
These are the traps learners hit most often on this topic. Knowing them in advance is half the fix.
Treating the logic model as a graphic, not an argument.
A pretty diagram with weak causal links scores no better than no diagram at all. Reviewers read for logic first and look at design second.
Skipping the reverse-engineering step.
Building the model left-to-right from existing activities tends to lock in whatever the organization already does. Building it right-to-left from the impact you want forces real design choices.
Practice problems
Try each on paper first. Click Show solution only after you've made a real attempt.
- Problem 1A program officer asks for "a quick logic model" for a youth mentoring program. Sketch the six columns in plain text with one example entry per column.
Show solution
Inputs: two mentor coordinators, curriculum, $90k. Activities: weekly one-on-one mentor sessions for 60 youth across an academic year. Outputs: 2,160 mentor contact hours delivered, 60 youth enrolled. Short-term outcomes: increased self-reported school engagement and goal-setting skills. Intermediate outcomes: improved attendance and assignment completion in the mentored cohort. Long-term outcomes: higher on-time grade promotion and high school graduation rates.
Practice quiz
- Question 1Which sequence correctly orders the six standard components of a logic model?
- Question 2What is the "activity trap" the lesson warns against?
- Reflection 3In one or two sentences, explain why a reviewer treats a missing or weak logic model as a feasibility concern, not just a formatting issue.
Lesson 34 recap
A logic model is a one-page visual proof that your program can produce the change you promise, and it is the foundation that the rest of Week 4 builds on.
Coming next: Lesson 35 — Inputs - The Resources
Next, we drill into the first column, inputs, and learn to inventory the resources a program actually consumes (not just the ones the grant will pay for).
Saved in your browser only — no account, no server.