12 minutes
A service delivered and a life changed Learn why a system built to count what it does drifts toward reporting outputs as outcomes, and how to tell them apart.
What you’ll be able to do Distinguish outputs from outcomes in your own reporting and identify one measure that is currently standing in for the other. Compare the responses to this question and explain your choice: What is the most accurate reading? Document a next step for A service delivered and a life changed: Take one report you produce and mark each measure as an output or an outcome. Why the drift happens A service system has to account for what it does, and what it does is countable: assessments completed, plans written, hours delivered, visits made. These counts are honest, and they are also within the system's control, which makes them attractive to report. Outcomes are neither. Whether a person has friends, work they value, a home they chose, and days that feel like theirs depends on many things beyond any one service. So systems report what they can count and, over time, begin to treat it as though it were the thing that mattered.
The result is a specific kind of blindness. A plan can have every goal reviewed and every visit logged while the person's life stays exactly where it was. Nothing in the file will reveal this, because the file records the service's activity, and the activity occurred.
Output or outcome? Twelve hours of community support delivered this month.
Choose a category Output Outcome He has two friends he sees without staff present.
Choose a category Output Outcome The annual plan was completed on time.
Choose a category Output Outcome She chose her apartment and can name why.
Choose a category Output Outcome All required visits occurred.
Choose a category Output Outcome He has held the same job for a year and wants to keep it.
Choose a category Output Outcome Check matches Reset Ask the second question What you can change You control whether a report of activity is accepted as a report of quality. Asking what changed in the person's life, every time, is what keeps the two apart.
What to watch for Do not treat a complete file as evidence of a good life. It is evidence of a complete file.
Your next step At the next quality review, ask for one outcome in the person's words for every output on the page.
A completed plan is an output. Whether the person's life moved in a direction they wanted is the outcome, and only they can say.
Carry this forward An output is something the service did; an outcome is something that changed in the person's life. The first is easy to count and the second is the reason the first exists.
Systems drift toward outputs because outputs are inside their control and outcomes are not, and because a count of visits looks like evidence.
A plan full of completed goals can sit beside a life that has not changed, and the file will not show it.
A sort separating outputs from outcomes, a scenario decision and a knowledge check.
Take one report you produce and mark each measure as an output or an outcome.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Course overview Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
