input < output < outcome < impact
2026-05-17
In most cases, the value grows in exactly this order. It's one of those ideas we know but don't follow strictly. Yet it's one of the rules we should all try hard to follow. Below, I explain each step.
The money you spend, your time, the resources you put in, and so on. For example, Elon Musk gets 24 hours in a day, and so do we.
output
What comes out of the effort or resources you put in. Say we spent an hour and wrote 200 lines of code. The input is 1 hour, the output is 200 lines of code.
outcome
The result that comes from the input and the output. We wrote 200 lines of code in an hour. But the code itself doesn't matter. It might fix something or make something new possible. That's the outcome.
impact
We judge the impact by the scale and importance of everything above. We solved a problem with 200 lines of code in an hour. There's a big difference between a problem one person hits once and a problem a million people hit every day. The impact of the second one is huge.
Another example:
- A doctor spent an hour with a patient (input). The doctor's experience is part of the input too.
- The doctor wrote the patient a prescription (output).
- The patient took the medicine and got better (outcome).
- The patient never got sick with it again, or the medicine caused another, more serious problem (impact).
By the way, most of these are input: our knowledge, the team we work in, the people around us, the videos we watch, the books we read, sports, and so on. There's a phrase in English: "garbage in, garbage out." As much as possible, we should think about the impact from the very first step.
People who think about impact have always been valued, but now, when producing code is getting so cheap, they matter even more. That's why, when we're asked to do a new task, we get curious and ask: why are we doing it, who is it for, how will it help, and what impact will it have on the business and the users?