Everyone is becoming very outcome focussed, have you noticed?
2020 was the year of managers talking more about ‘focus on outcomes, less on activity’. It was very relevant in a suddenly-WFH world where managers had no choice but to let go and apply real trust in staff that they could no longer physically oversee in the doing of busy work tasks.
What mattered (and still matters) in a COVID/WFH world was that the end goals – the objectives – are achieved, not the time that people arrived at their desk, or how long they spend doing individual ‘work’ tasks.
And the definition of those goals – the objectives – are increasingly about achieving an Outcome. It’s not about the doing, it’s about the impact of the doing. The reason for the doing itself.
Meanwhile, in the ITSM and IT Operations world, 2020 was a year of growing discussion also about productivity, IT experience, XLAs (eXperience Level Agreements) and much debate on the deficiencies in the old Service Level Agreement model, one which is usually metric not outcome based.
Gartner say XLAs can “drive better IT experiences by leveraging elements of digital experience monitoring (DEM), sentiment analysis and traditional service-level metrics“. (Gartner Hype Cycle for ITSM 2020)
And Gartner has also defined a mini suite grouping called IT Operations “Experience Management” which is made up of a combination of ITSM, ITAM, SAM and ITFM tools. All focussed on IT activities that affect the Experience of the individual.
Experience Outcomes
Experience. And Outcome. As recipients of a product or a service, we all experience the outcome of activity.
Outcomes are huge in the Product Management world. Whether building a Service or a Product – and, to me, these are the same thing – “good [product] teams know they’re responsible for results or outcome, not output“. Marty Cagan https://svpg.com/focus-on-value/
Whether in Service Management or Product Management , we do what we do to achieve an outcome. You can think of an Outcome as… a destination. You journey towards an outcome, with activity, and eventually reach that destination. The outcome has been achieved.
Yet why do so many operational metrics and performance measures simply ignore the outcome and focus only on measuring the activity? This may be because it is so easy to fall back to metrics-only. They can be referred to historically – ‘how many X activities did we do last year’ – and applied into the future ‘therefore we just need to do last year+10% to be 10% better than we were before’. I’ve been guilty of this approach in the past. It’s easy.
But this mindset is also limited. It disenfranchises individuals and teams, blocks creativity and hinders innovation.
An Outcomes Story
I’d like tell a simple story to show the difference that Outcome based, team planning can have over purely performance-metric driven services or products.
Your Service
Imagine, you offer a service or product that transports people from one country, across the sea, to another.
One day you sign a contract to transport a new customer across the sea from country A to country B. You’ve got a rowing boat and 10 strong rowers. You know from previous voyages (historical metrics) that 10 rowers, each pulling on their oar 1000 times (in sync) will average 10 miles in 5 hours. Country B is 9 miles away.
Your Metrics
You set a solid operational performance metric : each rower is judged ‘doing their job well’ if they pull their oars 1000 times. Once this hit 1000 strokes they’d hit their target.
Service Level Agreement : we will row you at a rate of 10,000 strokes a day. As long as there are not external events that may impact that progress. (So SLA doesnt apply on days that are too rough, or when the tide is flowing the wrong way).
Your Performance
Your rowers have huge muscles. 80% of the time they arrive within SLA. 10% of the time they arrive late. 10% of the time they arrive early and keep rowing round in circles in the harbour until they hit 1000.
Your Outcome-Focussed Competitor
But then a new competitor arrives. They also have a boat and a team of 10 rowers. But they work on an outcome based planning model. The crew meet with the customer, they talk about what outcome is needed. They learn that he wants to go to country B to go shopping to buy Christmas presents for his children.
The Outcome
So – surprise – the team understand that the outcome the customer wants to pay for is not rowing, or even arriving in country B. The outcome is a happy customer able to buy the presents he wants, which leads to the outcome of happy children opening lovely presents on Christmas day.
After all, that’s their job, their success is based on their effort achieving that outcome. Initially they build a contract based on a return ticket, with added parcel-carrying capacity, but also some of the crew research enhancements to rowing and they discover that they could build an engine, so the boat can go faster back and forth across the sea between countries, without as much rowing. In all weather. Faster.
The Transformation
Customers love this new service. That brings more business, more boats. The crew are promoted across multiple new boats. the next thing you know that competitor is running a fleet of boats that have capacity not only to get customers easily across the sea for Chrismas shooping, but now – for a subscription – can regularly bring the sellers and their products to the customer, so the customer doesn’t need to travel at all.
That competitor is going to clean up and your metric-based rowing boat service is going to fail.
Back to Reality
OK, well that might be a slightly … uh… clumsy analogy, but hopefully it paints a mindset difference. By focussing the whole team on the outcome not the activity we delight customers and we encourage creativity and innovation. Everyone benefits,
Now, there are many ways we can go from here. many directions. Possibly, if you are reading this, you might be thinking: well, yeah, but you can’t really measure outcomes. We all measure metrics because they are measurable.
What Next?
And yet I would argue that there is a way to do this. The magic formula that I’ll be starting to cover in the next post in this mini series. I’m calling that one : One Change in 2021: Adopt OKRs for ITSM Acceleration (or maybe, How You CAN Achieve Outcomes, and Prove that you HAVE Achieved Them).
What Do You Think?
What do you think? Have you seen success in a shift from metric to outcome based planning and measurement? Or have you seen failure? Throw your thoughts down there, in the comments, or back on linkedin, or twitter.
Image by analogicus from Pixabay
1 Comment
Do This in 2021: Adopt OKRs for Service and Product Success | Aitchison Insights · 20 January 2021 at 10:44 am
[…] is following on from the previous article: Focus on Outcomes for Execution and Innovation. That described how focussing on achieving outcomes over measuring activity can lead to success and […]