Chapter 4: Program Outcomes and Logic Models

This chapter details the Program Logic Model (PLM) to connect service outputs to strategic outcomes. It defines the three-tier outcome hierarchy, distinguishes outputs from outcomes, and uses a case study to show how PLMs guide resource allocation and performance measurement.

Learning Objectives

By the end of this chapter, you'll be able to:

Explain the three-tier outcome hierarchy (direct, intermediate, strategic)
Distinguish between outputs and outcomes at each level
Construct a Program Logic Model from service outputs to strategic outcomes
Identify contribution relationships between outcomes
Use PLM for resource allocation and performance measurement planning

Key Concepts

ArchiMate ConnectionProgram Logic Model (PLM)OutcomesQuality checkOutputExampleachieveDirect OutcomesResults, not activitiesIntermediate OutcomesChange from baselineStrategic Outcomes

Self-Assessment

0/6 completed

Before moving to the next chapter, ensure you can:

Explain the difference between outputs and outcomes with examplesDescribe the three-tier outcome hierarchy and relationships between levelsBuild a PLM using the five-step processIdentify common PLM patterns and when they applyUse PLM for resource allocation and performance measurement decisionsArticulate PLM limitations and appropriate use

Reflection Questions

Apply these concepts to your own context:

1. Think about a program you know well. Can you trace its outputs through direct and intermediate outcomes to strategic outcomes? Where is the chain strong? Where is it weak?

2. If you had to cut 10% from a program's budget, how would PLM help you decide where to cut? What additional information would you need beyond the PLM?

3. Consider a program that seems to have high activity but unclear impact. What might PLM analysis reveal about why impact isn't clear?