Focus on outcome, not input

How do we ensure we’re focusing on the right things for real success? You might want to have allok at the “IOOI”-pattern.

IOOI stands for Input, Output, Outcome, and Impact. It’s a simple yet powerful tool to understand the cause-and-effect chain of your projects. Let’s break it down using a common scenario: adding a new feature to your software.

Input: This is the classic “time spent” metric. We track developer hours, meetings held, and resources allocated. As managers, it’s familiar territory. We can monitor office hours and feel a sense of control. But hold on –

Input doesn’t equal output. Just because developers are busy doesn’t guarantee productive outcomes. We need to move beyond “busy bee” syndrome.

Output: Here, we see the tangible results – the lines of code written, the new feature built. It’s a step forward, but again, there’s more to the story.

Outcome: Did the feature actually make it into production? Is it usable and functional? This is where output translates into real progress for the software and its users.

Impact: Now we reach the heart of the matter. Did the feature improve our Return on Investment (ROI)? Are customers happy? This is the ultimate impact we strive for.

Traditionally, managers might get stuck on the “Input” stage, focusing on hours worked. But the IOOI framework encourages us to shift our perspective. By focusing on Outcomes and Impact, we ensure our efforts are aligned with the project’s true goals.