Skip to main content

ITSM vs. Biology

Information Technology Service Management (ITSM) is a specialization of the more general practice of Service Management. I'm at a Pink Elephant conference this week and I'm been thinking about ITSM versus human biology.

When you eat a sandwich, you don't need to provide advanced notice to your pancreas that a "change" is coming to the "body environment." You look at the sandwich and get a whiff of it and your body takes those signals to start the salivation process. Once you start masticating the food, you push some of it down your throat with your tongue. That triggers the peristalsis that carries the food down to the stomach.

Each stage in the process keeps the coming stages apprised of what is coming and they each know what they need to do. There is a lot of communication going on all the time, but there is no master planning. Two way signals keep information where it needs to be, exactly when it is needed, and no more.

We risk running into the same problems with ITSM that we run into with central planning economies: There is no way to centrally manage and know all the information. Trying to accomplish it will result in painful bureaucracy and slow reaction times.

Be organic, with agile communication between steps, and perhaps you'll find better results. It works in biology.

Comments

Popular posts from this blog

Beyond Scrum?

[Adapted from a post to our internal Slack team.]

My manager has been working to get an agile consultancy into our university's central IT department to help us progress in our journey toward being more agile. I hope that the training and coaching we receive will focus more on the root principles of value in agile processes rather than on a single process like Scrum.

Are there any root agile principles that you think we need to be better at embracing? Here are some that come to mind for me.
Develop functionality vertically instead of horizontally. You don't create the database layer all the way, and then the web services layer all the way, and finally--after 9 months--start to create the web user interface. Instead, you find a way to introduce a complete feature that touches all those technology layers so that you can get real feedback about the usage and value of the system or feature.Be willing to throw things away. If we're going to experiment, we have to be okay buildin…

Making People Feel Stupid: A Cardinal Sin in Design

People will go to great lengths and inconvenience to avoid appearing or feeling stupid. A great example of when design makes a user feel stupid comes from Alan Coopers 1999 book The Inmates are Running the Asylum on page 24. Cooper is talking about the keyless entry system on his car keys.
"The large button locks the car and simultaneously arms the alarm. Pressing the button a second time disarms the alarm and unlocks the car. There is also a second smaller button labeled 'Panic.' When you press it, the car emits a quiet warble for a few seconds. If you hold it down longer, the quiet warble is replaced by the full 100-decibel blasting of the car alarm, whooping, tweeting, yowling, and declaring to everyone within a half-mile that some dolt--me--has just done something execrably stupid. What's worse, after the alarm has been triggered, the little plastic device becomes functionally inert, and further pressing of either button does nothing. The only way to stop that hon…