What’s the Dimwit Duration On Your Team?

One of the sad realities of life in a team is that decisions often become stupider as they filter their way from the decision maker to the place where they get implemented.  Over and over, I’ve seen something that started out as a rational and well-intentioned idea become twisted into something pointless or annoying or awful as it percolates its way through an organization.  If you are the one at the end of that process, it can be really hard to believe that it ever started out as even vaguely rational.  Why does this happen?

Decision “Telephone”

Well, one problem is that the person implementing the decision often doesn’t really understand the original idea.  You’ve probably played “telephone” as a kid – take a phrase and pass it by word of mouth down a line of people.  At the end, the result is revealed to much hilarity since it never even resembles how it started out.  Well, that’s what happens to decisions – their basic shape might make it down, if you are lucky, but the context and the rationale for it are often mangled beyond recognition.  This is just a fact of life about people – they are a very lossy channel for communication – and it isn’t fixable.

Decision Combinatorics 

The other problem is that a single decision will often end up getting applied in a lot of places to a lot of people, and the person who made it doesn’t always have a clue about them all.  And, multiple decisions, each of which may make a lot of sense in isolation, combine into a mess.  For example, “we won’t push out an update to our web site until we run our test passes on it.”  And, “our test passes will try out all the different browsers that people are commonly using.”  Result: the site is down for hours because you can’t push an update that is a tiny little tweak to a configuration setting.

Can Rationality Prevail?

You can try to counteract these problems by having rational people at the tip of the spear who apply the decision with flexibility and humor.  That way, something that becomes completely impractical is not rammed down the throats of the team.  It is very hard to create a culture at scale that works this way; it is just a lot easier to be rigid than to be thoughtful, and people are inclined to be lazy.  Also, someone is much less likely to get into trouble for applying a policy than for setting it aside, and many people are very risk averse.

By all means, try to do this .. but don’t be surprised if it fails a lot.

Enter the Dimwit Duration

The only real cure I’ve ever seen for the bad decisions that slip through is to minimize what I call the “dimwit duration”.  This is the period of time that the stupid implementation of a decision stands, before somebody with the power to undo it finds out and can fix it.  Now a lot of factors play into this:

  • How often the decision maker meets and talks to the people who implement their ideas
  • How much power and authority is pushed down the organization
  • How detail-oriented and open-minded the decision makers are about what’s really going on
  • How egregious the decision is and how many people are affected
  • Where the team falls on the culture spectrum between “ruthless candor” and “sir, yes sir”.

The size of the team also has a lot to do with it – it’s one of the many reasons that I like smaller teams, where the doers and the leaders bump into each other often and know each other well enough to be honest.  In many large organizations, they never really do meet, and bad decisions can persist forever.  People can fall into a sense of despair that sanity will prevail, and you get the kind of bureaucratic inertia that Kafka satirized so effectively, with everybody just marching along.

What’s the Dimwit Duration on your team, and what are you doing to shorten it?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: