Category Archives: Organizational Dynamics

The Swamp of Inertia

This retired life takes a little getting used to, in a good way of course. One important missing factor is the structure you get from work life. You know when you’re supposed to awaken, when to brush your teeth, when to get dressed. When we work a normal 40-hour week, we have these instances scheduled down to the minute because, in the DC area and I imagine most metropolitan areas, it matters dearly in terms of traffic whether you leave the house at 736 am or 747 am.

So I’m using my blog to put a little bit of structure around my mornings. I have an unmanageably long list of blogs and other websites that I would like to check on a regular basis, and every morning I start down that list until I’m waylaid by wanting to share something interesting I’ve read. Both today and yesterday the ambush occurred at Blog Stop #1.

Thinking back on most of the change initiatives with which I’ve been involved, they’re not blocked by some counteroffensive or a better idea. Instead, they usually just sludge to a dead stop in the Swamp of Inertia. In fact, I don’t know anything that bureaucracies are better at than producing swamps of inertia. They’re everywhere. Arlene Goldbard, who writes on culture, politics, and spirituality, describes in her most recent posting the psychological conditions prevalent in these swamps:

…the fear of alignment with a lost cause, of failing or looking foolish; the irrational conviction that we know the future and it’s against us; anger and resentment at indifference to injustice; all of that baked into a pièce de résistance that keeps us from trying—thus fulfilling the proposition that trying isn’t worth the effort.

So what techniques can you use to cross the swamp? One is to detach your ego from the success of your project. This is hard but remember it is usually personal disappointment, anger, and frustration that lead the change advocates to commit professional suicide and/or abandon their ideas–which, intended or not, is the objective of the swamp creatures, uh, I mean creators. Another is to stay as close as you can to the high ground as you maneuver the swamp. One high ground technique is not to advertise your project as a change initiative. I always resisted the idea of giving a project a high-falutin’ name, like Horizons or Tempest or Earthquake. It always struck me this was 1. an ego-trip; 2. an unnecessary bid for attention; and 3. a surefire way of making it easy for people to remember you if the project failed. And a final way to battle the swamp of inertia is persistence. As the great leadership film Galaxy Quest declares: “Never give up!! Never Surrender.”

I know I’ve given the discussion of crossing the swamp short shrift, but, really, I need to go brush my teeth.

(Originally I thought of calling this post the Inertia Swamp. (I know, only someone who spent almost 25 years editing others’ work would fret about the difference.) But I settled on the Swamp of Inertia because it had a better rhythm. This reminded me of the names real estate developers give to their fancy suburbs which, if they want to affect a particularly high tone, always involve a preposition. So in San Antonia, for example, you don’t see Stone Oak Hills, you see the Hills of Stone Oak. The Highlands of Stone Oak.  Or one of my favorites in northern Virgina, L’ambiance of McLean. Obvious bonus points there for using French. But I digress…)

Why Decisions are Like One-Night Stands, or Lesson 2

In my posting on Lessons from a CIA manager, Lesson 2 was:  “Remember, your decisions are going to have much less staying power than you’re expecting them to have. Decisions are not committed relationships; they are more like one-night stands.” As perhaps this analogy is not eminently or even imminently clear, it deserves some elucidation.

(Writing the word elucidation above, fine Norman English word if there ever was one, reminded me of the distinction between Anglo-Saxon English and Norman English, of which I learned while I lived in London in the early 90s. When William the Conqueror and the other Normans (i.e. French) invaded England in the 11th century, they brought their Latinate language with them. It promptly began to mix it up with the more Germanic/Norse language of the locals, which is one of the reasons why English is such a rich language, with many more synonyms than most others. We have Anglo-Saxon words, such as start, and Norman/Latinate words such as commence. And because the Normans were the conquerors and the Anglo-Saxons the losers, society began to associate or, to use the A/S word, link Norman English with the better, higher class of people. And to this day, many of us slip into Norman English, i.e. use long, fancy words, when we want to impress with our intelligence, or A/S word smarts. But, I digress…)

Much is made of decision-making. And as my responsibilities grew over the years, I began to appreciate the importance of making decisions promptly. I believe that nothing gums up an organization more than interminably-delayed decisions. Even bad decisions are to be preferred over no decisions because, unless they are nihilistically-awful, any decision at least keeps people moving in an organization, which is always preferable to being stopped dead in one’s tracks. It is simply a matter of physics: it is easier to be agile and quick if you’re already in motion. It requires less energy than getting going from a dead start. This is Lesson 18.

It is important, however, to think of decisions as temporal, even fleeting things. Too many individuals and the media these days think of decisions as these EXTREMELY IMPORTANT EVENTS that will have a permance that merits people like WOLF BLITZER talking about them in BASSO OSTINATO tones. Just flash back to the interminable coverage of the Afghanistan decision made by President Obama late last year. The world we live in today has become so fluid and complex that I actually have come to believe it is counterproductive to think of decisions as having much permanence at all. They need to be made but, even more important, they need to be constantly reconsidered. Hence, the analogy: are decisions one-night stands or are they committed relationships? Well, actually most are probably neither–they fall somewhere in between. But the dynamics of our era continues to shorten their lifespans.

I wrote on this issue about year ago in a piece that was published in Studies in Intelligence, the CIA’s professional journal. In the piece I was mostly discussing the learnings intelligence officers could draw from the economic crisis, but I also touched upon the delusion that our decisions are or should be permanent or longlasting. The folowing chart was included in the piece.

Decisions are clear because the world is:
evident
rational
predictable
human-actuated
straightforward enough to understand
in this world we need intelligence

 

Decisions are fluid because the world is:
obscure
irrational
not predictable
outside the control of humans
too complex for rules
in this world we need sense-making

Editorial note: Given that I am unlikely to stop myself from including the occasional, bordering-on-long tangent in my postings, I will delineate them with green text, so the reader can just jump right over them.

We Don’t Need No Stinking Rules–or Lesson 17

If you recall my post early on regarding the lessons I learned from 25 years as a CIA manager, I was able to recall 16. (And I also promised to flesh out most of them in individual posts–still planning on it.) But I ran across this useful piece yesterday on how the controls imposed by managers create unnecessary complexity in organizations: http://bit.ly/9FFX60 by Ron Ashkenas over at the Harvard Business Review site. And it reminded me of yet another lesson–#17–Management by rule-making is almost always a mistake.

I wanted to write on this right away because it’s an issue that particularly afflicts the federal government. Most of my adult life the news media have been perched on poles, like vultures in the Texas Hill country, waiting to catch reports of the federal government doing something exquisitely stupid–which unfortunately is not a rare occurence, we are humans after all–so they can publicize it and mock it and therefore jack up advertisement rates. Of course, nothing much works for the news media these days to jack up advertisement rates, but the bloggers and social network outlets have taken up the slack just fine, thank you. Leaving aside for now whether this constant focus on the negative is productive or fair, the fact the federal government is everyone’s favorite GOTCHA doll contributes to its tendency to react to mistakes by making new rules–Ashkenas uses the Transportation Security Administration as his first example in his piece. And as these rules add up, “the accumulation of these “reactive” controls often creates complexity, confusion, and unnecessary cost.”

The public focus on government mistakes and the call from them and from Congress to do something about it  is one of the dynamics that contribute to management by nonproductive rule-making. But there are others.

  • The role of ideology in setting government policies. When a policymaker has an ideological belief that concept X is essential to the survival of the republic and concept Y will only hasten its destruction, the tendency to create a rule is strong. These ideological debates could be settled by the use of data, but often neither side wants to take the risk.
  • The tendency for government functions to have legal and/or authoritative foundations. Much–but not all–of what government does is not suitable for market solutions–i.e. choices. Society functions perfectly well whether you shop at Walmart or Target, but we have yet to figure out how to run a society where individuals can shop for the legal structure  they prefer. So the culture of making rules or authoritative decisions slides over into the process of government itself. Related, many of the appropriate functions of government, like national security, are REALLY important, and organizations that carry out these responsibilities like to ensure absolute conformity in execution.

Conformity in execution is important, but what is even more important is conformity in outcome, and that is where the complexity generated by constant rule-making gets you into trouble. A very smart consultant once told me that if you manage everything like it is an exception, then nothing is an exception. This captures the folly of reacting to every mistake with a new rule. So the next time you are tempted to make a new rule, think hard about the message you’re delivering to your work force. Do you want them to think or do you want them to follow rules? Your choice.