An interesting tale of ITIL trademarks

Here is an interesting story of the use of the ITIL name....

Read this link first.

I take these lessons from this:

1) Lawyers are incapable of subtlety or nuance, or even thinking much.

2) Build an open content website and they won't come.

ISACA Bylaws change 2015

Rumblings of dissent over ISACA internal governance? Say it ain't so.

The IT Liberation Movement

[Update: At the DOES15 conference, I think George Spafford finally nailed the name of this for me: an IT Renaissance ]

Things ITSM consultants hear

We started to put together a list of the silly things ITSM consultants hear. You might like to add to it...

The IT Skeptic is nine years old today. Thank-you!

...and what fun it has been.

Considerations for Multi-Speed IT

Recently I posted about the "Big idea" I am focused on for 2015: Multi-Speed IT Capability. Let's drill down into some of the further considerations that come out of that.

Copyright issues when using ITIL at the coalface

Axelos are shooting themselves in the foot by constraining consultants' use of ITIL.

the internet fosters madness

The world (epicentre USA) needs to address the madness promulgated by the internet.


  • Sandy Hook “truthers”: the government staged or faked the shootings to usher in gun control laws
  • NASA are geo-engineering the weather
  • anti-vaxxers who call vaccination "a form of rape" and deny the science

Whats up with Cyber Resilience?

I'm puzzled by all the activity around Cyber Resilience.

Multi-Speed IT

© Copyright Canstock Photo IncEnterprises are wrestling with the conflicting needs to chase competitiveness in a world of endlessly changing technology, whilst still remaining mindful and careful. In IT we are caught in the same bind. I have written about this squeeze before in "To Protect and Serve".

This year I'm looking at solutions: how IT can deal with the dichotomy with Multi-Speed IT. By embracing Agile, DevOps, BYOD and other "liberation" approaches, and integrating them into our ITSM, risk, and governance practices, we can create an IT environment with a better chance of responding at the speed of business, whatever the business chooses that speed to be. This article proposes a nuanced approach to two-speed IT, where each lifecycle implementation is a blend of the two "speeds".

Syndicate content