Skip to content
SQDC_001

SQDC for Enterprise IT – Introduction, Safety

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.

After a few attempts at a recurring IT status update for the executive team at a manufacturing firm, and met with indifferent and uncomprehending stares, I tried a different approach. Borrowing ideas from the Manufacturing Operation steam, I presented a summarized view of what was happening in IT – stealing ideas from the many Daily Management boards that I had seen during my visits to the plants.

I’ve gotten a lot of good feedback on the SQDC graphics that I’m using; these are the same four KPI categories used in all Daily Management meetings. Expressing IT performance using this approach has been well received, because the intent of the metrics are quickly meaningful to the operations-minded folks that I was communicating with.

Never heard of SQDC, not sure what it means? The acronym comes from the world of Lean Manufacturing, and it stands for Safety, Quality, Delivery, and Cost – four cornerstone KPIs of many manufacturing organizations. I took the classic focus for these KPI categories and applied them to the work we focus on in the IT group. It’s not a one-to-one transform, but with a little imagination and design, you can develop a better connection with the other functional areas of your business by speaking their language.

Safety

A primary focus for the manufacturing floor is safety. In our organization, we value people and their contribution to the company – one of the reasons we stress Great Global Teams as a critical high level objective. It’s also one for the most unique and recognizable metrics displays – the Safety Cross (or Safety Calendar), aptly named because it’s a calendar in the shape of a cross. We color in each day green for zero incidents, or yellow / red if there are any safety issues.

For the IT group – well, what sort of safety events are we going to track, a paper cut? Dropped a server on your foot? Safety incidents don’t happen very often for IT, so we are focusing on another critical resource – our information, and specifically the security of our Information. For Corporate IT, the Safety Cross is replaced by the Security Cross; same look-and-feel, but the topic is security incidents. Green is all clear, while Yellow means there was some sort of contained incident, and Red indicates that a serious data security breach or loss has happened.

SQDC 002

As you can see, we had a few minor incidents in January – a stolen iPad and a lost notebook computer – but February and March were quiet. Note that for the monthly report-out (above), I only showed the current month – just like in Daily Management!

In my next posts, I’ll explain the other three metrics (Quality, Delivery, and Cost) and talk a bit about what comes next.

11 April, 2013

Comments (1)

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