Black-and-white illustration: a set of balance scales. The left pan is overflowing with paperwork, clocks, code and checklists — sheer volume of output. The right pan holds a single tree growing from rooted ground, with a small team beneath it celebrating, representing outcome.

Output vs. outcome

In a recent post, I wrote personal reflections on the distinction between correlation and causation. This post is a few more personal thoughts on another related topic - outputs and outcomes. It is born out of frustration of having interacted with teams that ‘produce’ reports, ‘complete’ projects, and more generally spend Herculean effort on doing ‘things’ - yet the desired outcome is missing in action. I am hoping I am not alone in observing this.

So here we go.

We often mistake movement for meaning. Slides, reports, meetings, dashboards — all beautifully done. It’s easy to celebrate what we can count. Reports produced. Calls made. Campaigns launched.

But busyness isn’t business.

Output measures what we did. Outcome measures what changed because we did it. It needs the ability to connect the effort to, what changed because of the effort. That needs the ability to establish causality whilst not being confused with correlation.

You can produce 100 reports — but if no decision improves, that’s output. You can ship 10 features — but if no customer stays longer, that’s also output.

Outcome is where the real story starts. It’s the difference between putting the effort and getting the desired impact as a consequence. Being guided by outcomes helps us prevent wasting effort on ‘stuff’ that doesn’t matter. It also sharpens focus on stuff that does matter.

Because output fills time. Outcome builds value (in everything in life)