Tuesday, January 29, 2013
Does your team have Blame Well?
Now, the way it works is, each week the team rotates the role of Blame Well to a new team member. During that week, if *anything* goes wrong that team member immediately assumes *all blame* for anything that goes amiss.
The role of Blame Well enables the team and stakeholders to immediately get past trying to figure out whose fault anything is. Instead, the team can directly move into useful discussion about resolving whatever issue came up.
So…this post is definitely tongue-in-cheek. I think if a team really needed a Blame Well there are deeper problems to address.
What I hope folks could take away from this is that assigning fault and blame is pretty pointless. A better approach is to simply figure out what the next best thing can be done in the current context.
This doesn't mean teams shouldn't inspect and adapt…but true reflection and growth happens without fault and blame.
I'd enjoy hearing stories about how people helped their own teams or organizations get out of the blame game.
Posted by Matt Barcomb at 11:56 AM