From the Swamp of Inertia to the Road to Success

Writing about the Swamp of Inertia this morning made me think of one of my most favorite websites. Strange Maps, and a posting from it last year of a 100-year old or so map of the Road to SuccessThis map deserves careful study. Judging from the outfits individuals are wearing it must come from early in the 20th century. I think it is very sweet that near the pinnacle individuals must pass through the Gate of Ideals. And I just love it that early on people can be waylaid by entering what appears to be the garden of Bohemianism. I have to say I think I would have ended up there myself. Click here to get to the original posting on Strange Maps. Warning: you can get lost in this website for hours and it doesn’t have a map of the way out.

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…)

Your Calendar Reflects your Priorities or Lesson 10

On one of my first postings, Lessons from a CIA Manager, I listed 16 lessons I had more or less learned in almost 25 years as a manager there. (I think now we may be up to 18 actually.) Lesson 10 was: Your calendar reflects your priorities. You can talk about x or y issue being important to you, but if it never makes your calendar you’re lying to yourself and, worse, lying to others.

This is so simple and yet often overlooked. By now, almost all federal senior executives have had enough sensitivity training to know at least to talk a good game about issues such as diversity, employee engagement, work-life balance, etc. But it does you no good to tell employees that x, y, and z are priorities for you if you never can make the time to actually attend discussions on diversity, meet regularly with small groups of employees for straight talk, and deal with your own work-life balance issues. Remember that as a senior executive, your ACTIONS ALWAYS speak LOUDER than words. The individuals who work under your leadership pay careful attention to what you do.

I remember at some point at the Agency attending a diversity-related function and being thanked by the organizers for actually staying through the entire event. They marveled that “such a busy person” would have the time. Well, harumph! You can’t be very much of an executive manager if you can’t manage your schedule to do the things you say you care most about.

I also enjoyed blogging while at the Agency and found that to be a very effective way of getting my thoughts out to others. (It is amazing how muddy your message gets as it is translated through the layers of bureaucracy.) People would tell me they too would like to blog but they just couldn’t find the time and I would think, OK, communicating effectively with your employees has got to be one of your most important tasks and yet somehow you can’t carve out 30 minutes on your schedule. Somehow, I didn’t really find the time excuse to be that credible.

Finally one last trick about making yourself accessible as a senior manager. I am a slow walker. I like to ride the escalators–I find it pleasant. I learned from a management consultant–but I don’t remember who exactly–that the pace with which you walk the halls determines whether others find you accessible. People walking slowly are telling others, I have time for you, I can be interrupted. And so people will come up to you in the halls to talk, to tell you something you would not otherwise hear from them in a formal meeting. Fast workers send the exact opposite message.

So it’s not enough to  manage by walking around. You need to manage by walking around VERY SLOWLY.

(I googled the phrase “your calendar reflects your priorities” and hit upon several good pieces. Here’s one on whether your to do list reflects your passions. And another on whether your life reflects your moral compass.)

Personalized Work

David Warlick is a North Carolina-based educator and consultant who keeps a blog, 2 cents worth. His most recent posting describes the transition education is making, as a result of the information, communications, and technology revolution, to personalized learning. As someone who believes work itself will be reconceptualized in the next decade or so, I found many parallels between education’s major transition points and where work is likely to go. Indeed, it is hard to imagine how we could ever take individuals who have learned through the process he describes and then shoe-horn them into jobs as they are currently designed.

His major points are that personalized education:

  • Will be fueled by questions,
  • Provoke conversations,
  • Be responsive, i.e. be interactive
  • Will learn from mistakes, and
  • Will lead to personal investment from the learner and contribute to his/her evolving identity

(I reordered Warlick’s points slightly and did just a little wordsmithing, but I think I’m true to his ideas.)

Personalized work follows along similar lines. What do I mean by personalized work? Most jobs today are still designed according to some archaic position description, this is certainly very common in the government environment. These descriptions are infrequently updated. (I remember at the CIA it was always a very bureaucratically fearful time when the professional job redescribers descended upon your office.) (This makes me think of another post that would be fun to work on: When Bureaucrats are Scared, but I digress.) But if you just think about it, doesn’t it seem nonsensical that in this day and age we would organize the work of our mission around position descriptions that can frequently, I think, be more than a decade old. But it’s not the vintage of the description that’s the real sin, it’s the fact that you could never find a single person who could perfectly perform all the tasks required. So because of the perceived need to order work in ways that the bureaucracy and pay system can best handle, we actually make inefficient use of people, our most important resource as we are often and unattractively reminded.

Is there another way to organize work? YES!! Innovative organizations are beginning to work with new designs that actually allow them to match tasks to the best-suited individual. And they use technology to mash the two up. Every manager needs to visit and become familiar with Amazon’s Mechanical Turk. (I’ve made more than forty dollars there so far as a worker, enough to finance my MP3 purchases, but I digress.) At Mechanical Turk, large missions and jobs are being atomized into minute tasks, allowing individuals to self-select the tasks they are both good at and enjoy. What a concept!!!! I actually believe this approach could be applied to many tasks, including some missions of the federal government.

Another approach to personalizing work is to bring the aspects of game design into the work environment. It is an odd phenomenon that millions of individuals, many of whom have important positions in their analog lives, voluntarily and happily spend hundreds of hours a year playing computer games such as World of Warcraft. They solve complicated problems, collaborate and form trust relationships with people they’ve never physically met, and all for very little tangible reward. And yet some, when they come into work, mail it in. What is wrong with this picture? What is it about how work is designed that is demotivating, while game design engages individuals? Could it be factors such as immediate feedback, transparency, personalization? For more on this topic, check out recent books such as Total Engagement for eye-opening discussion on why games are not the opposite of work.

Anyway, this posting is already too long and there’s still much more to say and do on the topic. These changes are fueled by technology, but I don’t in any way consider myself a technology expert. I associate myself with David Warlick’s own description of himself: Technologists get excited by the light. I get excited by what we can shine that light on.

We are Part of the Solution

At my car dealer this morning bringing the old 2001 Mazda in for service. (I need to give a shout out to Rosenthal Mazda in Arlington, VA. They provide free if somewhat poky WIFI. And I guess as a blogger I need to state clearly that Rosenthal Mazda has provided me no financial renumeration. Au contraire!! But I digress…) Anyway I was checking out my Twitter feed for useful leads to interesting information and found William Eggers, who just wrote a great book, If We Can Put a Man on the Moon, about making government better, providing a link to his new website Policy Design for Execution. If you pick up the book or check out the website, government workers will appreciate the  sympathetic analysis of what leads to government disfunction. As the website notes, “policy ideas go straight from the idea stage through the legislature without being subjected to the exacting design process that occurs in the private sector.”

Well, I don’t know that the design process in the private sector is always that exacting, but I think the general point is still true. Government workers are often asked to turn some incompletely (or worse ill) conceived idea into reality, and then get all the blame when it doesn’t work. You can’t even say it doesn’t work as designed, because it WAS NEVER DESIGNED!!! And then, most galling, the very individuals who generated the idea–the legislators–then enjoy beating up the incompetent government workers who can’t get it right. Really, it is time for us govies to stop accepting victim status and join the conversation about out what, other than our own performance, also needs to change to produce better government results.

At the start I mentioned that I checked my Twitter feed. If you don’t twitter and don’t use it specifically to gather a posse of smart people you turn to for advice and ideas, then you are really missing out on one of the real benefits of social networking. At least among the people I follow, Twitter has evolved from idle chatter to focused sharing. For example here’s a link that just popped up to an interesting article in Foreign Policy on the new rules of war: http://bit.ly/9TmAvb .

Give Twitter a try.

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.

Is this Social Networking Contagious or Something?

Here it is after 530 pm on the East Coast, and I have hardly tweeted today and I haven’t facebooked and I haven’t checked into FourSquare anywhere and I certainly haven’t blogged, and I actually get this physical sensation of incompleteness, like a hunger, but not a hunger to eat but a hunger to share.  And I’m struck with how powerful the imperative to share becomes once you’ve switched your mental model–from hoarding information for yourself to telling everyone everything you think you know. It’s like geometry or algebra–it’s exponential. In the first model, you take many instances of knowledge and reduce them to a factor of 1. In the second model, every unit of information is multiplied by the  factor of infinity. Now I ask you, which is likely to be the more productive model?

Jonah Lehrer who writes on cognitive issues in his great blog The Frontal Cortex touches on the multiplying aspects of generosity in his piece from yesterday. Also check out this great piece from Signal Magazine about the Air Force’s emphasis on collaboration. They cite many reasons but of interest is the importance of collaboration to deal with the projected shortage of skilled labor in the decades ahead.

Oh and what was I doing today that kept me from being part of the great collaborative flow? Breaking in my new laptop. Transferring all the data. Figuring out what programs I’ll have to repurchase. GRRRRRRR…

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.

Cedars of Change

When I’m in TX, where my mom and I have a house and 14 acres north of San Antonio, I spend about two hours every morning clearing cedar, so-called but they’re actually members of the Juniper family. These invasive and water-hogging trees have pretty much taken over the grasslands of the Texas Hill Country and they’re just about impossible to kill. The only animals that will eat them are goats but even they only like the seedlings, so first you’ve got to whack out all the growth. I’ve taken to going out every morning when it’s cool with a good quality tree lopper to commit cedarcide. (eventually I’ll have to burn the stumps too) When friends visit, I put them to work, and it is emotionally very satisfying. (I’m tempted to say it is emotionally satisfying for me to have them do the work, but I’m out there with them too.)

I got to thinking yesterday there are plenty of metaphors to be drawn from clearing cedar that can be applied to clearing organizations, i.e. organizational change. (Organizational change being such a complex and daunting subject you can actually draw lessons for it from just about every moment of life–the movie Finding Nemo, for example, is rich in lessons to be learned…but anyway, I digress…)

When you clear large cedars, i.e. those taller than a person, and your tree lopper can only handle about one inch-diameter trunks, it is best to lop off the tall skinny parts first. Then you’re able to look down at the remaining cedar, see its pattern, and attack the radiating branches killing new beneficial growth underneath.

So it is with change. To really do organizational change well, you have to acquire a proper vantage point where you can really see the best places to attack. This place is probably somewhere near the top of the organization, where the different processes meet to confront success or failure. Otherwise, you’re like the blind men and the elephant, whacking away at whatever you touch first.

The toughest cedars to attack are the ones that have become huge spider webs, with many entangled branches. They usually send out what I think of as running branches low and parallel to the ground, often difficult to see in the brush. But it is critical you attack these.

Any organization around for a while will have its share of spider web departments and processes, which have a pernicious effect on the bottom line but are difficult to identify unless you are standing right on top of them. And you will also find spider web people. They can be unhelpful–i.e. they form the center of unhealthy dynamics in your group, but they often can be good–they are the master hubs that allow otherwise disfunctional processes to deliver worthy output…or they are the key advisers whom others turn to for knowledge. Many change efforts fail when they are unable to account for the complex dynamic of real work.

Unless you have powerful equipment, your cedar attack campaign will leave behind many stumps upon which others can trip. Eventually you have to remove these stumps but if you try to dislodge each one as you go, it bogs you down and I, at least, find it more psycholigically motivating to look back each morning on a larger field of accomplisment.

Similarly, organizational change efforts can get bogged down tackling wicked problems that no doubt need to be removed at some point. But be wary of  the psychological costs tackling these tough spots impose on your followers and lukewarm supporters. Steady momentum in most cases is more valuable than perfection.

When I go out to clear cedar, I never wear a watch or carry anything that would reveal the time. I just set myself a target area and proceed until I’m finished. It strikes me as pointless to use time to measure my effort given that I’m in it for the long haul, but I find that I’m usually ready to break after about two hours of work.

This “time consciouness” seems to be the most important learning from cedar clearing for organizational change. The imposition of what, when you cogitate, are arbitrary deadlines on change efforts is usually one of the dynamics that most undermine them. Think about it! If you have correctly determined what your group needs to move forward, you should want to do it no matter how long it takes. Few change efforts actually need to have drop dead-lines, but these are imposed because of the expected tenure of a particular leadership team, the exigencies of some budget cycle, or, worst of all, the sense–I think perverted–that new, better things either have to be done in accordance with some arbitrary schedule or… not done at all. I remember once being told that time was the cheapest type of literary device.  I would simply offer that time and schedule should almost never be the key organising principle for your change effort, and yet observe how often they are.

There is another reason why time limits are so common. Discombobulation and a decline in productivity often occur early on in a change effort, as individuals struggle to learn new ways of being and doing. The response then is to work through the change process as quickly as possible, which is usually a mistake given the complexity of what you’re trying to accomplish. The best approach, barring an emergency where change is necessary to prevent disasters,  is to be a tortoise–or perhaps a trotting horse, when it comes both to organizational change and cedar clearing. Move at a steady pace, keep your wits about you and your head up so you know when it is time to take a break.

Check out this slide package for a good presentation on this and other pitfalls on the way to organizational change.

Change is Hard, but how People judge Change is Harder

The tale of the goddess Athena, springing fully formed (and fully armed!!) from the forehead of Zues is one of the great stories of  Greek mythology, although perhaps it is more accurate to say of Mediterranean basin mythology given that people living there in ancient times shared many of the same myths.  The story is quite colorful, as it actually has Zues swallowing Athena’s mother who busily kept forming Athena inside Zues until she was ready to be launched–a perfect creation. (Here is the Wikipedia version of the tale.)

But unlike the emergence of Athena, everything we have around us in society, in biology, in organizations is the result of a long, often messy, incremental process. (Another word for that is evolution, but I don’t want to get involved in an ideological fracas just yet–although I do hope to tackle the perils of ideology at some point.) None of our current institutions, whether it be the Department of Transportation or the Cable Television System or marriage or astronomy, emerged fully and intelligently formed out of some brilliant individual’s forehead. No, they usually began as half-baked ideas and almost always took turns and detours unanticipated by their originators and early supporters. And, this is the important point, we shouldn’t want it any other way. For only through a process that allows a “thing” to react to the environment around it, change and adapt, can we hope to produce organizations, processes, customs, and institutions that actually work, that deliver most of their promise, that are organically one with their environments.

But if you’re an advocate of a Change Initiative for an organization or a group, the first thing you hear from anyone you brief is: “Well, how is the whole thing going to work?” The only honest answer to that question is “I don’t really know. We’ll have to monitor that carefully.” although by so admitting you might as well just slink back to the advanced methods lab from whence you came. The status quo may have had a 50-year development process with abundant beautiful messiness, but if you as the Change Advocate can’t present the future operating environment as a beautiful schematic in a series of Powerpoint slides, with some vaguely inspirational and symmetrical logo in the corner, then you’re as doomed as doomed can be.

This then becomes a real leadership moment for a Federal Government or any other senior executive. Don’t be the senior executive whose expectations for neat and orderly change are so…well..delusionary that you force your enthusiastic future-thinkers to become hypocrites and to package their proposals in Power-pointless slide decks. Because if you demand certainty, you not only will buy into intellectual fraud, you will also eventually tear the heart out of your change champions.

Approach change for what it is–the normal course adjustment process that keeps your organization alive.