Skip to main content

Fear and blame.

Hands up if you've ever heard someone say:
"We don't have a fear-and-blame culture."

And keep them up if the reaction of the 'doers' was to roll their eyes and mutter something sarcastic.


It's a nice phrase to trot out at a senior leadership conference or to write in your 'best employer of 2020' application, but if you have to say it, it's probably not true.

And repeating the mantra won't make it any more true.

In fact, people might respect you more if you were honest and admitted that there is blame and where the boundaries lie.  At least in that scenario, the individual knows where they stand.
Instead, we often have the jarring dissonance of hearing our leaders say one thing and seeing them act entirely differently.

As a leader (especially a senior leader):
When you stand at the front of a room and tell the assembly that there is no fear-and-blame, look at their faces.  If they mostly appear too scared to disagree... you have a problem.

Or when you ask for questions to be submitted, get very little back, and your reaction is to assume people are just too lazy to respond,.  Chances are, the lesson has already been learned; that the safest thing is to stay quiet and avoid too much notice.

All this is amplified in organisations that ask for continual feedback but never make any real changes based on it.


When you do this you're asking people to take a risk with no hope of it leading to improvement.  Is it any wonder that employees are reluctant to raise their heads above the parapet?

(Un?)Fortunately, for those trying to maintain the illusion, there's almost always a corporate pet willing to play the game.  They'll complete every survey (positively), prepare (safe) questions for events and can be generally relied upon to involve themselves in anything under the banner of 'give-back' (because delivery is rarely what counts at appraisal time).


  1. If something is raised be honest in your answer - don't be a politician.  If the honest answer is that nothing is going to be done - just say it.  People will cope.  And your reputation will rise amongst the troops.  Of course, if your immediate thought on reading this is "I don't care what they think of me" then I'd suggest you're not suitable to lead a team.
  2. If less-than-glowing feedback is received, privately or publically, take it seriously, ESPECIALLY if you disagree.  Immediately dismissing the point, refusing to acknowledge the validity of it in any way, or putting down/attacking the person who raised it is the management equivalent of taking your ball home when it's your turn to play in goal.
  3. Respect that someone took the time to respond, your reaction might determine if they ever repeat the exercise (or at least repeat it honestly - they may just learn to play the game.)
  4. Be upfront about what may or may not be done in response.  The natural assumption is that once something has been raised the process of resolving it has begun.  If nothing is going to happen - say so.


The best information comes directly from the front line and those relationships must be cultivated and maintained.

IT folk aren't always the most naturally confident, but they do learn fast.  Don't let the lesson be to stay silent.

Comments

Popular posts from this blog

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement.  And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ?  I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise.  I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how  to become more effective, then tunes and adjusts  its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified i...

"We are Agile!"

A phrase Project Managers hear a lot, and one that occasionally proves to be at least partly true. As it's most often spoken rather than written, it is hard to know whether the speaker means 'agile' or 'Agile'.  I find that asking the question ('big A' Agile or 'small a' agile?) can reveal a lot about that person's knowledge of the 'Agile' world.  If you find yourself asking the people around you this question and you receive blank faces or confused responses you can be fairly certain you haven't landed in a particularly Agile organisation, rather you're somewhere that has rolled out a buzzword in the hope of improving speed of delivery. Organisations tend to fall into one of the following categories: - Comfortably Waterfall - Fine . This organisation knows how it wants to work and perhaps has reasons why they prefer to keep projects waterfall. - Waterfall but concerned they need to get on the Agile bandwagon - Confused ....

Definition of Done - An example

Done? To call a story 'Done-Done' we should refer to two things: the acceptance criteria for each story the team’s Definition of Done The DoD is defined by the team and should be updated whenever it seems appropriate e.g if there's a big change in the team or the work; or the team simply sees the need for a change. If you have project based teams, it's something to agree before timebox 1 kicks off. If you're more product based and continuously working through an ever growing backlog, slot it into a timebox kick-off, a retro (if that's where it was discussed) or just grab 10 minutes after the daily stand-up. An Example: Here's a basic example created by a team I was working with: ---------------------------------------------------------- A. Dev done ---- Code review done ---- Unit Tests written and passing ---- Integration tests written and passing B. Test complete ---- Manual Testing complete – Acceptance Met ---- Automation Tests written and ...