8th February 2012

Network Dictionary – Blamestorming

The intention of this disgusting practice show how base human nature can be. Originally intended to be a review of an outage or network impact so that analysis of the problem could occur and management could consider action that might prevent a repeat of the problem. Thus it was “brainstorming” the problem

The reality is that most people are not big enough to own up to an error, or admit that they did not follow procedure, or that some part of the design did not work as expected. The person in charge is forced to conduct a witch hunt, and ends up running a judicial process and less like an arbitration.

Someone is going to be blamed. And the process becomes a negative thing.

And that’s why its called “blamestorming”.

This post is copyright of Thropos Ltd ©2008-2011 at Etherealmind.com - contact | email: greg.ferro@packetpushers.net - twitter: @etherealmind | All rights reserved
About Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus

  • Tim

    That is what happens just before they break out the “Blamethrower”