Let it happen

I come across this frequently enough that I’m sure I’ve blogged about it before, but context dictates that I do it again. The story I hear goes pretty much like this:

My team really needs to improve X, but nobody is taking responsibility for it. The fix is obvious – we need our exec / manager / project owner to mandate that we do X and measure Y & Z to make sure people are doing the right thing.

Here’s a concrete example. I was on a team once where quality was in the toilet. We couldn’t even get a build to run for over a week. The solution was require everyone on the team to perform a list of actions before every check-in. Of course, the list including using flaky tools, and getting sign off on every step, even if the step wasn’t applicable to a particular check-in. Given the extra work required for check-in, developers queued up weeks worth of check-ins for one big check-in rather than go through the steps in the checklist multiple times. Day to day build quality was slightly better, but velocity was way down. While slower velocity is not necessarily a bad thing, the big problem was culture. Someone honestly thought the mandates would create a culture of quality – but the only culture they created was a culture of finding ways to skirt the damn checklist. Team morale sucked, and the product we built sucked too.

To be fair, I’ve seen some successful mandates in my career. The push for improvement in every developer to write secure software at MS worked. But that culture change was also pushed by huge monetary losses.

In general (and in every other case I can think of), mandates don’t work – especially if you are using the mandate to change culture. Yet I see mandates suggested as a solution for changing culture time and time again. I just don’t get it.

The folks at 37 Signals say it best, “You don’t create a culture. Culture Happens.”

So help let it happen. Instead of a mandate, help your team see where you want to go. Make it personal. Appeal to their own pride and values. Show them how change will help them. Find allies who think like you do. Experiment.

Let it happen. Make it happen.

Similar Posts

  • Conferences – again!

    I took some time off from speaking (too much) at conferences over the past few years. I spoke at TestBash Philadelphia a year ago (and also spoke at the Online Test Conference last summer), but 2017 (and, IIRC, 2016) have been light on me in terms of external speaking. But I’m going to kick off…

  • Five for Friday – October 9, 2020

    Not sure if it’s possible to find anything more interesting than Pence’s fly this week, but I tried. Mike Cohn wrote (yet another) article I enjoyed – this week’s topic asks, Are We Really Bat at Estimating? This twitter thread had some unsurprising thoughts (with some research) on the future of remote work. It’s now…

  • HWTSAM–Five Years Later

    Five years ago this week, How We Test Software at Microsoft hit the shelves. The book has done well – both in sales, and in telling the story of how Microsoft approaches software testing. An unfortunate aspect of writing a book like this is that after five years, most of the book is obsolete. Sure,…

  • Leadership

    When I was 9 years old, I’d play pick up soccer at recess. A couple of kids – the “leaders” would pick teams, and then we’d play. Since we were kids, the leaders of the teams were sometimes the best players, but usually the loudest kids. Leadership was short-lived, but effective for the purpose. I…

2 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.