Just like a virus, industry best practice is easily spread. It thrives in busy social environments and training courses, easily transmissible from host to host, even over the internet. And, just like a virus, as best practice spreads across many hosts and changing environments, it must evolve and mutate into new forms to be successful.

I’ve been closely involved in two industries over recent years; Software/tech Product Management and IT Service Management (ITSM). Watching the evolution of advice and best practice in these two spaces, I think can see an imminent evolutionary leap coming. I think that ITSM could soon evolve and mutate to embrace more of the techniques of modern software Product Management.

I’ll even make a big bold statement. If you want to get ahead in Service Management tomorrow, you should start studying and applying modern Product Management tools and techniques today.

DNA Picture - The DNA of ITSM and Product Management

Mark Cleary gave an excellent presentation at Gartner’s Infrastructure, Ops & Cloud Summit in December ’20. In his session – provocatively titled “Is ITSM Dead?” – Mark also called out the need for ITSM to align and collaborate better. Specifically he talked about bridging the gap between Product Teams and the rest of the Business. I described below how Product Teams are a fundamental basis for modern Product Management.

I’m not suggesting that anything is dead. This is about evolution and addition, not replacement.

History

ITSM and Product Management, Reading together

First, let’s have a look at how two industry practices have evolved over time.

1990s

Once upon a time, there were computers. And there were software vendors. They produced software products, specified by Product Managers, written by Developers and shipped on floppy disc or CD. The products were installed and configured on-premises by their customers or consultants. And the Developers moved to coding the next release which took maybe a year to arrive.

2000-2010s

Wider adoption of ITIL and real ITSM started to blossom. IT organisations were busy creating and managing Services that used a combination of software products, infrastructure, hardware and configuration to bring value to users. The ongoing operation was all part of the Service. Understanding cost of operation, cost of service, uptime, SLAs, support, reacting to outages is part of the service, addressing defects, applying enhancements into production.

2010s

Then… boom!, Cloud arrived and with it came Agile and later DevOps. Suddenly next-gen software vendors are churning out beautiful products into the cloud. However that same vendor was also continually operating their cloud Product after release – operating it as a Service. Not as a shipped boxed software product, but as a continually operating Service-Product. They carry a cost of operation, an SLA, rapid updates, availability, continuous delivery and more. In some cases, software vendors were adopting ITSM practices to manage their new Service Products.

2015… ish

Next the Cloud software vendors then moved ahead fast. Once they had embraced the whole new devops culture they next evolved new modern Product Management practices. Those new practices focussed on creating Service Products that are really user-valuable, holistic, continually operating, incrementally improving and offer a great user experience.

Meanwhile, inside large organisations with their own Dev teams were seeing this shift. They applied also to building internal products and services. DevOps started being widely and enthusiastically adopted by non-vendors. But ITSM remained unchanged.

2019 – today

Finally, ITSM also starts to embrace more agile principles and practices. ITIL 4 comes along. A good step forward for ITSM. A service value system, principles, practices. However, even with ITIL 4, ITSM now playing catchup to the modern Product Management industry in the techniques of how to create, operate and improve valuable Service-Products.

What Is ‘Modern Product Management’?

Now let’s look a bit at what I’m calling here ‘modern Product Management’. Specifically, that’s what we might call software or technology Product Management.

I am not referring to the old world of (waterfall) Product Definition Documents, Product Initiation Documents, Product Proposition Documents, Technical Specifications, Functional Specifications and long dark development periods leading to long and slow major release events. Those days are gone folks. Modern Product Management treats each ‘Product’ as a holistic mini business-line, and can even create value and make revenue without writing a line of code.

Modern Product Management refers to the business-minded, value-based, outcome-focussed, iterative, discovery-based creation and operation of tech products that evolve rapidly, and surprise and delight users and customers.

Get Inspired

There’s a few good sets of guidelines around what you need to do to successfully manage modern products. I’m going to refer here to one body of work here in particular: The “Inspired” set of product management recommendations. These are documented in the book “Inspired: How to Create Tech Products Customers Love, written by Marty Cagan from the Silicon Valley Product Group, The Inspired approach is followed by many cloud/tech organisations, including Google and Adobe.

The modern Product Management described in the Inspired books focusses on Product Teams, the ‘triad’ of Product Manager, User Experience and Dev Leads. It takes a modern agile approach to building cloud products, iteratively, through discovery, prototypes and customer interviews, all the way to incremental updates in production and continual enhancement through the lifecycle of the Service Product.

Nothing is Perfect

The Inspired Product Management advice is not perfect. In my opinion it has holes and it makes mistakes. I’ve seen where it succeeds and also where it fails. However, its direction is good, its principles are right, and if you adopt and adapt the Inspired model you are likely to be on a path to success.

Then again,

ITIL 4 is not perfect. It has holes and it makes mistakes. I’ve seen where it succeeds and where it fails. However, its direction is good, its principles are right, and if you adopt and adapt ITIL 4 recommendations you are likely to be on a path to success.

(see what I did there?)

Right, thats the background all done. Let’s now look at the evidence to support my bold statement.

Evidence Point Number 1 : The ITIL 4 Principles.

Uncannily similar to modern Product Management.

Firstly,  ITSM. Love it or loath it, there’s that towering body of ITSM recommendation known as ITIL. The new ITIL 4 materials first started to see the light of day in 2018/19 but – I feel – didn’t really get momentum until 2020. With these new guidelines for a more modern ITSM comes something significant: The ITIL 4 Guiding Principles.

  • Focus on value.
  • Start where you are.
  • Progress iteratively with feedback.
  • Collaborate and promote visibility.
  • Think and work holistically.
  • Keep it simple and practical.
  • Optimise and automate.

If you are reading these as a software Product Manager, the above should mostly resonate and have you nodding and saying ‘well yes, that’s what we do – or try to do – as PMs. These concepts exist and already apply in the world of software products and modern Product Management.

I’m a gentle fan of ITIL. I think. these principles are outstanding. For another blog, another time, I could argue that these could be applied further, certainly beyond IT, possibly beyond Service Management, into the world of anyone, anywhere that needs to get any work done. Even at a personal (non work) level. But that’s for another time.

My main point here: ITIL 4 introduced Principles that brought it very close to the approach already existing in modern Product Management.

Evidence Point 2.1 Modern Product Management Concepts.

Also relevant to Service Management.

Let’s look some of the key concepts in the Inspired product management model produced by the Silicon Valley product group.

Here are the Inspired “Key Concepts”. I’ve added some extra description, and the italic highlights where you could connect directly into ITIL:-

  • Holistic Product (all parts of functionality, value, monetisation, cost, users, user experience etc)
  • Continuous Discovery and Delivery (iterative and continual feedback)
  • Product Discovery – what is the value, is it viable, can we do this
  • Prototypes – Little steps, and very often, iterating rapidly.
  • Delivery – scaling performance, reliability, fault tolerance etc. Very reliant on Automation.
  • Product/Market Fit – understanding your target customers and meeting their needs
  • Product Vision – the longer term objectives, purpose and ambition – why the product(s) exist.

Evidence Point 2.2. Principles in modern Product Management.

They sound a lot like ITIL 4.

And here, digging deeper, are some of the Inspired Principles of Product Discovery. Any of this sound familiar to ITIL 4 people?

  • Establish compelling value
  • Progress iteratively, with failed ideas expected as part of the process
  • User experience is harder and more critical to success than engineering
  • Functionality, design and technology are intertwined

The use of “Principles” themselves is a core tenet of the SVPG approach. It’s described and emphasised throughout the Inspired work. And there are Principles in ITIL 4. It’s not just that they are similar; the very existence of any Principles in ITIL seems to be further evidence of convergence of ITSM into the same place as Product Management. Yet I see no sign of Principles in ITSM for each Service (Service-Product).

Evidence Point 3. Modern Product Management Tools and Techniques

They fit into ITSM. Can we even use Product Management to plug any gaps in ITSM?

This is a whole book in itself. I’m not doing that. Here’s a few bullets and one with a bit more explanation. All of these could potentially be used today by Service Managers to focus on building, operating and improving great IT Services:

  • Roadmaps, Lean Canvas, A-and-B testing, Customer Letter, Value Discovery, Prototypes, User Experience, Technical/Financial/Market Viability.
  • Also IT services could all have Vision, Strategy. And IT organisations of course can have their own Principles.
  • Then, OKRs. You’ll maybe have seen my blog article about OKRs. OKRs are a concept used in modern Product Management, described as a valuable PM tool in the Inspired book. And – my opinion – ITSM and ITIL 4 seems to lack a clear time-defined, measurable yet aspirational outcome goal model for measuring improvement success.

Solution? Adopt and adapt from PM. Use OKRs in ITSM.

Now You Try

Here’s a super-simple exercise for IT Leaders, or Service Management Leaders. Try this ➖

  1. Create a spreadsheet with 8 columns: Our Service-Products | A ServiceProduct Manager | A User Experience Lead | A Product Team | A Roadmap | Some OKRs | Some Prototypes | Regular Customer Interviews.
Table to summarise your Service-Product maturity
It Might Look Like The Above
  1. List some or all of your primary IT Services in the first column. Let’s call these your Service-Products.
  2. Fill in a Y or an N in each cell of each column for each of the Service Products. If you have the item, put in a Y. If you don’t put in a N.

Mostly ‘N’? You could start using existing modern Product Management concepts and methodologies to better manage and improve your Services as Products.

Mostly ‘Y’? There is nothing I can add. Great job!

That’s All For Now

OK… so that’s that. This was a hard one to write. I feel like I’m stepping into the space of some deep subject matter experts here. Makes me a bit dizzy.

As ever, I’m happy to be wrong. Tell me about it. Am I?

Image by 🎄Merry Christmas 🎄 from Pixabay

Image by Sasin Tipchai from Pixabay


0 Comments

Leave a Reply