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”.
Other posts in the series
- Network Dictionary - Washing My Patch Cables
- Network Dictionary - Coin Operated
- Network Dictionary - Pinch off a Packet
- Network Dictionary - Cloudtard
- Network Dictionary - Default Gateway of Blame
- Network Dictionary - Negotiable Affection
- Network Dictionary - Reverse Recruiting
- Network Dictionary - percussive maintenance
- Network Dictionary - Powerpoint Waterboarding
- Network Dictionary - Oral Masturbation
- Network Dictionary - consultant
- Network Dictionary - Eye Dee Ten Tee
- Network Dictionary - Moregasm
- Network Dictionary - Blamestorming (This post)
- Network Dictionary - velvet rut
This post is copyright of Thropos Ltd ©2008-2011 at Etherealmind.com - contact | email: greg.ferro@packetpushers.net -
twitter: @etherealmind | All rights reserved
