Skip to main content

How completely messed up practices become normal.

Paul Crowley (@ciphergoth) posted a couple of interesting links on Twitter about the "normalisation of deviance" and organisational culture. The first was about the crash of a light aircraft that happened in Boston in 2014.  The report concluded that the pilots omitted every safety check they should have performed before take-off, and even when they realised there was a problem they did not abandon the take-off attempt.  As a result, they and their passengers were all killed.

What is interesting about the article is the investigation into the culture of the company.  It seems that pilots never performed these safety checks.   The proper process was seen as an annoying waste of time.  We see this in our own industry as well and I was thinking of posting something about the tendency to skip proper sign-offs in a project process.

Fortunately, Paul saved me the effort by linking to a much longer blog post by Dan Luu, with the title How Completely Messed Up Practices Become Normal.  It's a fascinating look at some of the weird practices Dan has encountered in his career and at how organisations come to regard their practices as "normal".  He gives examples from open source projects and big companies.  I really recommend that everyone working in IT reads this and has a think about how we can make our own organisations more aware, both of our odd practices and of what the best organisations are doing instead.


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…