6 minutes reading time (1294 words)
Featured 

The difference between a target, an output, and an outcome

targets Targets, outcomes, and outputs

In life, we measure much of any person's worth by what they achieve, after they have achieved it. In some sense, targets, outputs, and outcomes all do this. Well, then why should we know their difference? What makes matters worse, is that there are many definitions on each.

To manage operations and strategy, Org must measure its results. There are two ways to do this. The first is to define what a process must deliver. This is a prediction of an output. In orgamatics we call it an output target. An output is the result of an operation. An operation is when cyclic processes repeat a known past to create a predictable result. The second is to define the change that a strategy must induce. This is the prediction of an outcome. In orgamatics we call it an outcome target. An outcome is the effect of a strategy. A strategy is a plan to achieve an intent through project-based work. A target predicts an output or outcome. The actual results are outputs and outcomes. The variation between projected results and actual results is a measure of performance. The way in which we grasp what we get, will differ to the way in which we grasp the impact of that. Therefore, the metrics of outputs and outcomes cannot be the same. One must know the difference between these concepts since they drive performance and relevance.

To grasp these concepts, we must define them from an orgamatics perspective. Once we understand what they are, we can relate them. In the post, "How to engineer a process construct" I explain that Org only has one process. Everything relates to everything else within Org. Therefore, outputs, outcomes, and targets should also have a relationship. It is easy to practically apply these concepts if one grasps their interdependence.


How to engineer a process construct

Does one design or discover a process? To manifest, purpose must become a process. Therefore, there is purpose before process. When we create a process, we explicitly depict a purpose. It is our idea of what Org must do to get outputs. When we design outputs, we discover outcomes. This will help us to redesign our process. One will thus interchange...
https://orgtology.org/index.php/2015-06-01-09-45-25/orgtology-blog/18-engineer-a-process-construct


What is an output?

An output is what one delivers as result of a process cycle. When one forecasts that, it becomes a target. So, an output is the result of a process. One can predict an output with reasonable accuracy since it repeats a known past. There is a lot to learn from the past. Perfect knowledge on a process should give perfect knowledge on its outputs. If there is no unknown factor that will disrupt a process cycle, its output should be predictable.

An output shows ability and not completion. Processes do not begin or end, they cycle. Therefore, an output tells you what the ability of a process is at a specific point in time. The ability of a process reflects its efficiency. E.g., When a lioness teaches her cubs to hunt, she will take them to mice and grasshoppers, until they can do so with ease. As they become more able, she will take them to larger animals, such as small antelope. Later, she might teach them to take down a zebra, and who knows, eventually a buffalo. The lesson here, is that there is no difference in the core process of hunting a lizard and that of hunting a buffalo. It is the lion's ability that has increased with the latter hunt. A process that produced a lizard now produces a buffalo, without adding resources. This is the essence of efficiency.



What is an outcome?

An outcome shows the effect of what we have done. E.g., the functionality of an IT company that sells infrastructure, is what customers buy. Functionality of infrastructure is the output. Whether people use it, and whether the IT company makes money from it, is an outcome.

Efficiency drives outputs whilst effectiveness creates outcomes. Outputs show whether we are doing things in the right way. Outcomes show whether we are doing the right things.

Outputs are easy to predict. Yet, it is extremely difficult to predict outcomes. This is because an outcome is often just a perception of those who use your product or service. It is difficult to predict how people will perceive things.


What is a target?

A target is a quantifiable estimate of an output or outcome. In orgamatics we distinct outputs from outcomes since they measure different things. They have unique implications; thus, we must assess them correctly.

When we create an output target, we forecast what a process must do. This is measurable since repetitive processes produce predictable results. An output target will help us grasp the level at which we can perform. Therefore, outputs become operational targets. In so, output targets measure efficiency.

Dispose of 80% of our fully depreciated fixed assets by 30 March 2020.

Output Target

An outcome target is different. Here we aim to forecast the impact that something will have. This is difficult, since we cannot predict what the effect of a product or service is on those who use it. People are simply not that predictable. An outcome target must help us to grasp how relevant our performance must be. One can measure outcomes is against strategic targets. This is because relevance is the aim of strategy. In precis, outcome targets measure effectiveness. The test of effectiveness is relevance.

Increase our market share by 50% before the end of this strategic period.

Outcome Target

The primary difference is that Org has full control of an output target. In other words, we can achieve it through process efficiency. An outcome target is only partly under the control of Org. To achieve such target, one must strategize and often compromise. Outputs needs communication whilst outcomes need negotiation.


Practical application

To know the difference between outputs and outcomes is important. It will ensure efficiency and secure effectiveness. There are separate metrics for outputs and outcomes. Outputs create a fact, whilst outcomes negotiate a perception. Clear outputs and outcomes will enable Org to define exact targets.

Outputs begin in purpose, whilst outcomes ignite through intent. The former defines performance and the latter ensures relevance. Org will measure its performance against output targets. Once Org creates its outputs, it can test the efficiency and relevance thereof. If there is a problem with either, Org must transform or mitigate risk. In so, strategy and the ability to mitigate risk will decide the relevance of Org. From this we learn that outputs precede outcomes. Therefore, efficiency precedes effectiveness. Through this cycle, effective outcomes will ensure efficient outputs.

From outputs to outcomes value chain


This flow chart gives a simple view of how outputs and outcomes interact. The chart below gives a more complex view. A process construct creates the outputs of Org. If these outputs are both efficient and relevant, Org will continue to produce them. If not, Org must decide whether it can change the situation. If "Yes", then Org must transform. If "No", then Org must mitigate its risk. These initiatives will create a perception of relevance. In orgamatics we call this an outcome. Where outcomes are effective, we use it to boost out outputs. If they are not, we go back to the drawing board.


From outputs to outcomes process flow

An output target predicts future performance through analysing past efficiency. An outcome predicts future relevance. Jointly, they help Org to perform and stay relevant. To distinct them is key.

Empowering Excecutive Teams Worldwide

Copyright

© 2018: Derek Hendrikz

How to create output targets
Six steps to creating process flow for a process c...

Related Posts