2 September 2010

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”.

Please rate this post:

1 Star - It\\\'s Crud2 Stars - It\\\'s Tosh3 Stars - Something\\\'s missing4 Stars - Needs works5 Stars - Good Enough6 Stars - Good7 Stars - Excellent8 Stars - Brilliant9 Stars - Astonishing10 Stars - Awesomely Godlike? (No Ratings Yet)
Loading ... Loading ...

About Greg Ferro
Greg is a Network and Security Architect / Designer / Engineer working freelance in the UK and worked for Resellers, DotCom's, Large Corporate's and Service Providers across a variety of products & Vendors. He prefers to work for end users, believes in the life cycle, total cost of ownership and that near enough is often good enough. He likes talking about himself in the first person to feel "royal", even when hosting the Packet Pushers Podcast on Data Networking. More about Greg at http://etherealmind.com/who-am-i/ and you can follow him on Twitter.

Comments

  1. Tim says:

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

Speak Your Mind

*