Does your organization need a neurologist?

When addressing the idea of tacit knowledge in respect to knowledge management, most descriptions focus on the tacit knowledge IN organizations – that is, the tacit knowledge of the individual members of the organization – and how to capture and share that tacit knowledge. While I believe it is important to understand this tacit knowledge, I’ve always been more attracted to an understanding of the tacit knowledge OF an organization, what it is the organization as a whole ‘knows.’

As with individuals, organizations operate based on the tacit knowledge they possess and their ability to act on that knowledge when needed. In the human brain it is the connections between neurons – and the ability of the brain to reorganize those connections to meet the situation – that makes up the intelligence and tacit knowledge of the individual. In organizations, it is the connections between people. (see this post of mine from 2006 for a bit more on this.)

Many years ago, in one of my first ever blog posts, I wrote that “KM is the neuroscience of an organization.” After reading Is Enterprise 2.0 the neuro-organization? a couple of days ago, and a brief discussion with Harold Jarche (@hjarche), I was once again curious.

Here’s a start. (Definitions from Wikipedia)

Neurology: a medical specialty dealing with disorders of the nervous system. Specifically, it deals with the diagnosis and treatment of all categories of disease involving the central, peripheral, and autonomic nervous systems, including their coverings, blood vessels, and all effector tissue, such as muscle.  –>OD ?

Neuroscience: the scientific study of the nervous system, the scope of neuroscience has broadened to include different approaches used to study the molecular, developmental, structural, functional, evolutionary, computational, and medical aspects of the nervous system. –> KM?  IT?

Psychology: the scientific study of human or animal mental functions and behaviors, psychologists attempt to understand the role of mental functions in individual and social behavior, while also exploring underlying physiological and neurological processes.  –> OD? Training/Learning?

Psychiatry: the medical specialty devoted to the study and treatment of mental disorders—which include various affective, behavioural, cognitive and perceptual disorders; mental disorders are currently conceptualized as disorders of brain circuits likely caused by developmental processes shaped by a complex interplay of genetics and experience.  –> HR?

Way off base? On the right track?

What we need are knowledge curators, not managers

The concept of “knowledge curator” has been creeping slowly from the back of my mind to the front over the past couple of years, and received a couple of jolts over the weekend that resulted in one of those elusive “aha moments”.

What we need are curators of knowledge,
not managers of knowledge.

First, I noticed the blurb “curated content from Flickr” when I used the Flickr module on a Squidoo lens.

Second was a quote from Liz Danzico (that I found via Signal vs. Noise blog).

A portfolio of work is a curated experience. … but oftentimes, a portfolio only contains final pieces, as applicants are overly concerned about presenting perfection. Polish doesn’t communicate process though, and therefore I’m left with only part of the story. Messy problems — and how applicants work through them — can show a great deal more in a portfolio than one finished, airtight solution.

I didn’t know it at the time,but this all started back in November 2005 with an article titled Technology makes it easy to ‘remember,’ the trick is learning how to forget, in which I wrote:

My early days in Knowledge Management included a lot of time developing, deploying, and getting people to use “knowledge repositories.” (At least trying to get people to use them.) … I finally realized one day that the problem has become not, “How do we remember all this knowledge that we’ve learned?” but rather, “How do we forget all this knowledge we’ve accumulated that we no longer need so we can focus on what we do need?”

I also noted a quote from the book The Trouble with Tom by Paul Collins related to the need to “eliminate” memories:

Memory is a toxin, and its overretention – the constant replaying of the past – is the hallmark of stress disorders and clinical depression. The elimination of memory is a bodily function, like the elimination of urine. Stop urinating and you have renal failure: stop forgetting and you go mad.

It was this latter quote that was in my mind last summer when, in The importance of forgetting,  I wrote about John Medina’s thoughts on the question of memory and forgetting in Brain Rules:

The last step in declarative processing is forgetting. The reason forgetting plays a vital role in our ability to function is deceptively simple. Forgetting allows us to prioritize events. Those events that are irrelevant to our survival will take up wasteful cognitive space if we assign them the same priority as events critical to our survival.

As I noted then, this is no less true in the organizational context of knowledge/concept work.

Simply capturing everything in document repositories and best practices, without the ability to forget – or supercede – any of it, takes up a lot of “cognitive space” that organizations could be putting to other wise good use.

The trick is figuring out how to forget, and how to figure out what to forget.

A checklist for checklists

It’s easy to say, “Make a checklist for your complex process and use it”. It’s another thing altogether to actually make a checklist that is good and that works.

One of the things that I like most about The Checklist Manifesto is that it recognizes and addresses the challenges inherent in designing a good checklist. In fact, a good part of the story revolves around making the WHO surgical checklist a good one. In the acknowledgements section of the book, Gawande credits Boeing engineer Dan Boorman (who is also mentioned in the book) as an “essential partner” in the ongoing development of new checklists, and from the looks of it they’ve been hard at work.

Most relevant to my ongoing thread here is the Checklist for Checklists, pictured below. If you have decided that checklists can help you, this is an excellent place to start as you begin the process of developing your checklists.

Simplifying the execution of complexity

My review of Atul Gawande’s latest book The Checklist Manifesto focused, by design, on the broad scope of the book. Within that “big picture” lesson, though, are many smaller, more specific lessons to be learned.

For example:

No, the real lesson is that under conditions of true complexity – where the knowledge required exceeds that of any individual and unpredictability reigns – efforts to dictate every step from the center will fail. People need room to act and adapt. Yet they cannot succeed as isolated individuals, either – that is anarchy….

[U]nder conditions of complexity, not only are checklists a help, they are required for success. There must always be room for judgment, but judgment aided – and even enhanced – by procedure.

During this discussion, he refers back to what he had learned from the skyscraper-building industry, that they had figured out how to put an understanding of complexity into a series of checklists. That they had, in Gawande’s words, “made the reliable management of complexity a routine.”

What makes this even more fascinating is how the checklist, the lowly checklist that Steven Levitt had no interest in (until reading this book), can help simplify the execution of complexity even when the team members have never before worked together.

Just think what they could do for a team that works together all the time.

Navigating complexity with checklists (a book review)

Atul Gawande’s latest book, The Checklist Manifesto: How to Get Things Right is an incredible book that I highly recommend to anyone that works in a complex environment, especially if that involves working with multi-discipline teams. And most especially if this involves frequently working with people you have never worked with before.

I picked the book up not really knowing what I was in for. Talking about checklists, I thought maybe it would be a discussion of how to document and implement best practices, or something similar. Boy was I wrong.

At the surface, the book is the story of how Gawande, as part of a World Health Organization initiative to reduce surgical complication rates around the world, discovered the power of checklists to help avoid “avoidable failures.” Looked at more closely, it is a study of the importance of team building, team work, and communications between team members as they tackle the complex problems we all face today.

The first chapter, titled “The Problem of Extreme Complexity”, sets the stage. Later chapters build on this problem statement and uses examples from many diverse fields including aviation, construction,  and the operations of corporations and government. The common thread through each of these examples is the checklist – the lowly, simple checklist.

The challenges face by Gawande and the WHO team were (are) two fold: figuring out how to take what worked in these other industries and translating it into the needs of the surgical community; and getting past the culture of surgery and surgeons. The former was a relatively simple matter of trial and error, see what works and give it a try (in simulation first, where possible). The latter, on the other hand, remains a significant issue.

Part of the resistance is, according to Gawande, a misconception about what checklists are and the purpose they serve. This is a lesson he learned as he worked with engineers from Boeing in trying to understand what makes a good checklist:

It is common to misconceive how checklists function in complex lines of work. They are not comprehensive how-to guides, whether for building a skyscraper or getting a plan out of trouble. They are quick and simple tools aimed to buttress the skills of expert professionals. And by remaining swift and usable and resolutely modest, they are saving thousands upon thousands of lives.

As a systems engineer I recognize many of the issues, challenges, and solutions that Gawande discusses in the book. I was (am) quite appalled at how little of this systems type thinking seems to exist in the world of surgery and am quite hopeful that the idea of checklists catch on at all hospitals. If I ever have to go in for surgery, one of the first questions I ask the surgeon and his team is going to be, “Do you have a checklist prepared for this procedure?”

Perhaps the greatest insight about checklists in the book is that checklists – a lowly, simple, well crafted checklist – can take a group of individual experts and quickly turn them into an expert team.

All you have to do is use it.

Update: For more on the book, links to various media interviews, and some examples of effective checklists, visit Atul Gawande’s website.

The futility – and value – of planning

In his recent article Planning is very important…. It doesn’t work, Jack Vinson has this insight into planning:

If they hadn’t planned, there is no chance they would have been able to accomplish what they wanted to do.  At the same time, if they had decided that the plan was exactly what they were going to do, they would have never made it either.

This is a lesson I learned very early on in my military career, and something I wrote about back in March 2005 (has it really been that long?) while digesting the ideas in Malcolm Gladwell’s then-new book Blink.  The following is a slightly edited version of those original thoughts.

– – — — —–

Have been spending a lot of time “adjusting” plans lately. A colleague made the following comment today in one of our many (many many) sessions:

He who plans early, plans twice.

Which got me thinking about the apparent futility, and the obvious value, of planning.

The aphorism “No plan survives first contact with the enemy” is absolutely true. Proper preparation, though, can make that fact largely irrelevant. The very act of planning, and rehearsing that plan, involves preparation that enables you to effectively react to most any situation that may arise. In other words, proper planning allows you to IMPROVISE.

“What?” you say. “Improvise? That’s fine for comedy and music, but military operations? Business? I don’t think so. The whole purpose of planning is so you know what is going to happen, and when it is going to happen. Not to just wing it.”

In an Industrial Age setting, I may have agreed with that. But in the Information Age, I strongly disagree. If you tie yourself too tightly to a plan, and stick to it no matter what, you are doomed to fail.

As an example, consider a football (American) team – or any other team sport, for that matter. It is possible to develop a detailed game plan that dictates every play you will use, and when you will use them in the game. You could make a simple list of plays: On the first play, do this; On the second play, do that. etc. Or you could have a more detailed plan: If it is second and under 5 yards, and we’re in the red zone, we do this. etc. You could even take it a step further and include separate options that take into account the opposition’s activities. Of course, the more contigencies you identify, the bigger the play book you have to carry around and the longer it may take to figure out exactly what to do.

What actually happens is that the team develops a basic game plan ahead of time and rehearses the execution of that plan. By doing this, the focus of the team becomes achieving the goal of winning the game, and not just simply executing the plan.

I was inspired to write this post partly by a few key passages in Malcolm Gladwell’s new book Blink , in which he uses the obvious example of an improv comedy troupe (which in turn cites as one of their references a basketball team) to support the concept of “thin-slicing,” the ability to parse a given situation into the minimum information required to deal with that situation.

Management : Efficiency :: Leadership : ??

When talking about management, what most people are thinking about is efficiency, maximizing output per unit of input. Many (most?) people talk about the need for leadership in addition to, or even instead of, management.

But what exactly do we get from leadership? What is its purpose?

The first word that comes to mind is “effectiveness”. But most measures of effectiveness are based on a desired end-state, which to me makes this just a different way of measuring efficiency.

Is leadership just another way to get people to do what you want them to do so you can accomplish your own goals? Or is it something different, something more?

<break title=”flight to phoenix”>


Some thoughts:

When you “manage” something / someone, the best you can hope for is what you ask for. When you “lead” someone, there is no way to know ahead of time what you will end up with.

Maybe the question is better addressed in the context of the Cynefin framework:

Management : Simple :: Leadership : Chaotic

(and possibly disorder), with a sliding mix of the two being appropriate in complicated or complex situations.

Of course, I’m not the first person to consider this question. There are many (many many) more thoughts on this question out there, as you can see in the Google search results for leadership vs. management.