Skip to content
SQDC_001

SQDC for Enterprise IT – Cost, Next Steps

This article is part of the SQDC for Enterprise IT series
Summary:

First in a series of posts on presenting a summarized view of Corporate IT using SQDC-style KPIs - a Lean Management-inspired way of speaking in a language your Manufacturing Operations teams will understand.

SQDC 006
Click to enlarge …

Cost

At once the most and least understood, the Cost section is what everybody focuses on (specifically: cost reduction!) but also what controls our ability to do more project and support work with the resources in Enterprise IT.

The sample graph show 13 months – we are including the previous December just to get a decent picture for the first part of the year. Along the top, we show monthly budget performance (green = savings, red = over budget).

Note the big red “miss” in January that stands out so well; the graph design nicely focuses the attention on exceptional events / situations, ad the conversation need only hit the high points.

The second graph (bar chart underneath) is a picture of the IT Budget Forecast; the red bits in the months at the end of the year shows budget cuts already made since the first of the year. If your process is sophisticated enough to incorporate a rolling 18 months forecast, this won’t be an annual picture – we like to show last three months Actuals and next 9 months Forecast.

Why so Terse?

As I review these with some IT veterans, I hear the feedback – these are amazingly terse pictures, potentially glossing over some important details. This is very much by design – in my experience, IT folks tend to get into too much (or the wrong) detail, and are not as sensitive to that glazed look in the eyes of the audience. The idea here is to provide a quick overview at how we are doing – details can be made available if people are interested, but if the overview is sufficient – we move on.

Next Steps

We’re still working to figure out how to incorporate these metrics in a “live” manner on our intranet pages – the challenge is not technical, but behavioral (daily snapshots do much better posted on bulletin boards – especially in a manufacturing environment). The communication culture of the organization is the real determinant of the best way to make this stuff public and accessible.

If you like the reporting style and would like to use it for your organization, let me know – I can create templates for the graphs shown.

20 April, 2013

Comments (0)

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Articles
knowledge management

The Knowledge Management Revolution You Didn’t See Coming: 3 Skills Your Team Needs Now

AI hasn't solved the decades-old knowledge management problem. It's just changed which skills matter. Learn why capturing organizational knowledge is still the hardest challenge, and discover the three critical capabilities your team needs to succeed in the AI era.

Read more
Complexity Buzzword

Navigating Buzzword Overload: Complexity

Complexity means different things to different people in different conversations. Are we trying to simplify a process? Complexity is bad. Understand a supply chain? Complexity is good. Don't buzzword your initiatives with "complexity" until you get a wee bit more specific.

Read more

You Can’t Run IT Like A Business (except Maybe You Can …)

Well-intentioned IT leaders, and their functional peers, want to apply run-like-a-business concepts like customer satisfaction and value creation to the operations of shared service functions. If we can describe things with the same words, we can apply the same fixes. But it's a bit tricky to restate things in a meaningful way...

Read more

An Author’s Journey – The Editor’s Harsh Bright Light

Second in a series of articles on the creation of Don’t Think So Much. Exposing yourself to the unbiased eye of your editor will be a humbling, but super valuable, experience.

Read more