Cow’s eye view

mooTSAMoo, moo…..

That’s how I felt earlier this week going through security at Newark airport. I was recently re-reading parts of Thinking In Pictures : and Other Reports from My Life with Autism by Temple Grandin for some posts on my autism blog, 29 marbles, in which she talks about her job designing cattle chutes for slaughterhouses (she’s world reknowned for this, despite [because of?] being autistic. Ever on the lookout for connections between apparently unrelated things, my brain presented me with the following thought: “I wonder if Temple Grandin could come up with a better design for airport security queues?”

Maybe not, but this got me thinking about cross-functional lessons learned. Too often, in my experience at least, lessons learned and best practices are explored only from the perspective of a specific functional area. There is a lot to be learned from looking at stories from similar, but completely different, functions.

Using the case of the airport security queue as an example:

  • Many people going through an airport security checkpoint have never done so before (like most [all!] cows at the slaughterhouse)
  • For all practical purposes, the way through the process is to simply follow the person in front of you
  • Occassionally, you will get redirected by a security person to a different line, told to stop, etc with little or no explanation (as if you don’t deserve it or won’t understand it anyway)
  • etc.

The situation of people in a strange (as in unknown) queue system that has no obvious explanation in some ways is not really much different from that of a cow going through cattle chutes. What lessons can we take from Temple Grandin’s success in designing cattle chutes that result in smoother operation and apply to the security line problem?

My real point here is that sometimes you can take insights learned from one thing and apply them to something completely different with great success.

Note: Temple Grandin’s personal choice of a title for Thinking in Pictures was Cow’s Eye View, a reference to how she comes up with her designs. Maybe that’s the simple lesson to be learned here: look at the problem from the point of view of the one going through the process.

Which came first – the knowlege or the knowledge management?

What is knowledge? What is knowledge management? (Uh oh, here we go again!) In a recent post, Jeremy has the following to say about trying to define knowledge:

Part of the problem, I think, is that there really is no general agreement on what Knowledge Management actually is. And since one’s definition of knowledge really depends upon one’s definition of KM the knowledge question won’t be adequately answered until the KM question is dealt with.

I read the statement twice, then read it again to make sure it said what I thought it said. And it did.

If I had written the sentence above, I would likely have said “one’s definition of knowledge management depends on one’s definition of knowledge.” Because, after all, how can you manage something if you don’t know what that something is? (Chicken or the egg?)

But it does get you thinking….

– – — — —– ——–
Just an interesting note: my second post to this blog, back in June ’03, was entitled What is Knowledge Management, anyway?. Amazing to reflect on how much has been achieved and figured out in that time, but how we are still trying to figure out the answer to the basic question.

"Knowledge Management is both a goal and a means" for DoD

The May ’05 issue of Signal Magazine from the Armed Forces Communications Electronics Association (AFCEA) has a large section addressing the role of knowledge management in today’s Department of Defense. The articles range from discussions of technology used to create a “net-centric” force to descriptions of ongoing research into the cognitive workings of teams (that one is my favorite).

If nothing else, the article provides a glimpse at the challenges faced by military forces in collecting, processing, distributing, and using information and knowledge, both from a technical perspective and a “people” perspective. Check it out when you have a chance.