Inputs, outputs, and outcomes
September 12, 2022How do you measure the effectiveness of your team's or project's work?
How do you measure the effectiveness of your team or project?
Broadly speaking, there are three categories of things we can measure with regard to a human endeavour (and non-human endeavours as well): Inputs, outputs, and outcomes.
The trouble is that the easiest ones to measure (inputs and outputs) are the least interesting or valuable.
Examples of inputs:
- Hours worked
- Money spent
- Meetings attended
- Raw materials consumed
With the strange exception of the first, it’s usually pretty widely accepted that measuring inputs is of very low value, because it’s so far removed from the business goals. We can spend millions of dollars, or invest countless person years into a project, but if the project never works, it’s all waste.
Examples of outputs:
- Lines of code produced
- Features created
- Bugs fixed
- Server up time
- Units shipped
- Reports generated
Measuring outputs is pretty universally better than measuring inputs. All else equal, if person A produces 5 units in 8 hours, and person B produces 10 units, the greater number of units is probably better.
Of course, many, if not most or all, of these have their own drawbacks. Measuring lines of code is a famously bad measure of effectiveness, because it’s so easily gamed. Truth be told, practically all of these can be gamed.
So that leaves us with measuring outcomes. Outcomes are the actual business goals achieved.
How do you measure the outcomes of the work your team or project produces?
How can we measure risk?
First, why do you want to measure risk?
What are the common agile metrics people use?
This may seem like a perfectly reasonable question on its face. But is it? I see two problems here.
Adventures in DevOps 129: The Future of Intelligent Monitoring and Alerting with Ava Naeini
Ava Naeini shares her patent-pending tool that uses ML to determin the health and performance of distributed systems.