Knowledge management = creating environments for learning

One of the recent additions to my feed subscriptions is Confused of Calcutta by JP Rangaswami. Recently, he’s been thinking about Facebook and its potential role in Enterprise settings. Today’s installment has an interesting riff on the nature of knowledge management. It dovetails nicely with some of the things I’ve had to say about visibility and knowledge work.

Facebook and the Enterprise: Part 5: Knowledge Management

Knowledge management is not really about the content, it is about creating an environment where learning takes place. Maybe we spend too much time trying to create an environment where teaching takes place, rather than focus on the learning.

Since people want to learn by watching others, what we need to do is to improve the toolsets and the environment that allows people to watch others. It could be as simple as: What does my boss do? Whom does she talk to? What are her surfing habits like? Whom does she treat as high priority in terms of communications received? What applications does she use? Which ones does she not use? When she has a particular Ghost to deal with, which particular Ghostbuster does she call?

It’s not about creativity, it’s about curiosity

The critical leverage point for an organization seeking more effective innovation is establishing new attitudes toward curiosity. Industrial organizations were optimized to extract value from tiny doses of curiosity and cannot tolerate larger doses. Today’s organizations require more frequent and intensive invention and innovation, which depends in turn on learning to foster and effectively channel curiosity in greater doses.

The industrial economy was driven off of very small doses of curiosity, carefully controlled and administered. New ideas were the province of either the senior-most leaders in an organization or their specifically designated deputies (industrial engineers, product designers, strategy consultants). Outside of this small cadre, the rest of the organization was charged with pulling on the oars and carrying out the execution of the designs created by this cadre. Industrial organizations are optimized to extract the maximum output from the least curiosity. Moreover, our schools and other social systems are built around throttling curiosity and channeling it into acceptable settings; isolating the most curious from the rest of the system. For those immersed in the industrial mindset, unfettered curiosity is a serious threat that operates at an emotional rather than rational level.

In the knowledge economy invention and innovation take a more central role. Success based on the ability to out-execute the competition is increasingly short-lived. The changing economics of information and communications technologies continue to drive down the costs of execution. They shorten the distance, in both time and money, between idea and execution. They also shorten the distance between innovation and duplication. The need for more systematic and effective invention and innovation is generally acknowledged. Curiosity is the necessary prerequisite and fuel for this invention and innovation.

Alan Kay tells a story of his days at Xerox PARC. The suits from headquarters in Stamford Connecticut had come to Palo Alto to inspect their investment in open-ended research. Alan carefully explained the nature and risks of research; that PARC was conducting experiments, that most experiments failed, but that even failures moved the research forward. The suits nodded politely, allowed as how they understood what Alan had said, and insisted that these experiments be designed to succeed.

Given the degree to which curiosity in most organizations is discouraged and often suppressed, the first task is to carefully reawaken it. Carefully, because too much curiosity will trigger corporate immune responses. Fortunately, despite all the best efforts of our school systems and organizational watch guards, the human animal remains fundamentally curious. We need to give permission for this curiosity to be engaged and protect its first cautious glimmerings.

Here is one place where RSS and blogging have an important, low threat level place inside the organization. Seth Godin captured this succinctly as quoted in Naked Conversations last year:

Not only are bloggers suckers for the remarkable, so are the people who read blogs,” said Godin. “This is the most curious segment of the population, the people who are seeking out the new and the useful. This is the audience that doesn’t need to be interrupted because they are already listening. They are alert, on the lookout for the next big thing. No need to yell. If you’ve invested the time and the energy and the guts to make something remarkable, this audience can’t wait to hear about it.

(Naked Conversations, Chapter 3, Word of Mouth on Steroids, p.40)

Find and encourage those in your organization who are already paying attention to do so a little more systematically. Encourage them to begin to pass along what they are finding to others who might also be interested.

The second task is to start channeling this nascent curiosity toward potentially useful deliverables that can be judged and evaluated. Incorporate an interesting discovery into the next presentation to a customer. Adapt a lesson learned to an improvement process about to launch. Craft a proposal to target a new customer or begin a joint effort with an adjacent department.

Understand that channeling curiosity is a leadership challenge not a management task. Like a parent with an inquisitive toddler, leaders need to allow room for exploration, risk bumps and scrapes (and possibly worse), and intervene only to avert real danger. If they opt to guide exploration into familiar paths, they will get familiar results.

If you are still unsure about the importance of curiosity, recall what Albert Einstein said toward the end of his life:

I have no special talent. I am only passionately curious.

 

Warren Bennis on Great Groups

Bennis - Organizing Genius

Organizing Genius : The Secrets of Creative Collaboration
Bennis, Warren; Biederman, Patricia

Much of the talk about Enterprise 2.0 centers on the possibilities that new technologies open up for improved cooperation and collaboration in organizations. The problems of cooperation and collaboration in organizations have attracted attention long before today s technology options existed. Warren Bennis has been studying the issues of leadership and organizations for decades. In Organizing Genius, Bennis turns his eye toward the lessons we might draw from the successes of great groups.

Published in 1997, Organizing Genius examines the case histories of seven great groups, whose stories are worth knowing regardless of the lessons they contain. The groups the Bennis and co-author Patricia Ward Biederman chronicle include Disney s animation studio, Xerox PARC, Apple s Macintosh team, Clinton s original election campaign team, Lockheed s Skunkworks, Black Mountain College, and the Manhattan Project. As a long-term student of leadership, Bennis here emphasizes the importance of the group in achieving exceptional results when those results call for creativity and innovation. While there is still an important role for leadership, it is leadership that calls for a much more delicate touch than we are accustomed to seeing or valuing. In Bennis s view, in fact, great leaders cannot arise absent a great group to lead.

Bennis highlights the following lessons about great groups:

  1. Greatness starts with superb people
  2. Great groups and great leaders create each other
  3. Every great group has a strong leader
  4. The leaders of great groups love talent and know where to find it
  5. Great groups are full of talented people who can work together
  6. Great groups think they are on a mission from God
  7. Every great group is an island but an island with a bridge to the mainland
  8. Great groups see themselves as winning underdogs
  9. Great groups always have an enemy
  10. People in great groups have blinders on
  11. Great groups are optimistic, not realistic
  12. In great groups, the right person has the right job
  13. The leaders of great groups give them what they need and free them from the rest
  14. Great groups ship
  15. Great work is its own reward

Bennis also has an online article on The Secrets of Great Groups, which summarizes his insights in a slightly different way. None of these lessons are exceptional, although it s good to see that Bennis emphasizes the importance of shared mission. That s something that I see as a frequent problem in groups that are struggling.

In all of this, technology is not center stage. What Bennis does is to show us places where you might focus your technology efforts.

Alan Kay on learning and technology

Alan Kay is talking once again about what went wrong with the personal computer and personal computing. Here’s a pointer to a recent interview he did with CIO Insight magazine that is well worth your attention.

A CIO Insight

Alan Kay was recently interviewed for CIO Insight magazine’s Expert Voices feature. In this piece entitled Alan Kay: The PC Must Be Revamped–Now, Alan discusses the mindsets that stand in the way of real innovation – and what his not-for-profit VPRI is doing to address the issue. In the article, Alan defines Croquet as one of those efforts and as “a new way of doing an operating system, or as a layer over TCP/IP that automatically coordinates dynamic objects over the entire Internet in real time. This coordination is done efficiently enough so that people with just their computers, and no other central server, can work in the same virtual shared space in real time.”
[Julian Lombardi’s Croquet Blog]

Alan is up to his old tricks of trying to invent the future instead of predicting it. His focus remains on viewing the personal computer as a learning tool more than a productivity tool, which means, among other things, that you should be prepared to invest time and effort in that learning. He is not fond of efforts that sacrifice the real potential of tools by focusing on making the first five minutes easy and entertaining at the expense of crippling the long-term capabilities of the tools.

Alan remains a disciple of Doug Engelbart:

 Engelbart, right from his very first proposal to ARPA [Advanced Research Projects Agency], said that when adults accomplish something that’s important, they almost always do it through some sort of group activity. If computing was going to amount to anything, it should be an amplifier of the collective intelligence of groups. But Engelbart pointed out that most organizations don’t really know what they know, and are poor at transmitting new ideas and new plans in a way that’s understandable. Organizations are mostly organized around their current goals. Some organizations have a part that tries to improve the process for attaining current goals. But very few organizations improve the process of figuring out what the goals should be. [Alan Kay: The PC Must be Revamped Now]

There is a potentially deep and rich connection between challenging knowledge work and technology. But realizing that potential will require different attitudes about how much time and effort we should be prepared to invest in learning. Organizations thinking about investing the technologies collectively identified as Enterprise 2.0 should also be thinking about what investments they should be making in the appropriate individual and organizational learning

Jack Vinson’s plans to blog with his knowledge management class

I had lunch yesterday with Jack Vinson. Jack is teaching about knowledge management again this Spring and is planning on having his students keep blogs as part of the class experience. Back in 2002, I tired a similar experiment at Kellogg and blogged about the results then. I figured I would share the pointers here, in case anyone else wants to take a peek

Blogs in the classroom

Blogging in the classroom, Part 2. Forced blogging = flogging?

Blogging in the classroom, Part 3. Developing an initial view on klogging

Blogging in the classroom, Part 4. Plugging into the conversations

Certainly, the technology environment has gotten richer and easier to work with. My recommendation to Jack was to keep everything browser based, especially given that many of his students work full time and have computers locked down by  their IT departments.

I am also inclined to start with reading blogs and following blog conversations via Bloglines or Google Reader pre-loaded with an initial set of feeds. Requests to comment on items and publish reactions will flow from that more naturally than from straight on assignments to post. I am looking forward to Jack’s efforts.

Business Problems and Root Causes

Thanks to Jon Husband for pointing this one out. I’ve been a fan of Evelyn Rodriguez’s Crossroad Dispatches for a long while. Her writing challenges me to take risks that I don’t always rise to, but always appreciate.

Business Problems and Root Causes

A delicious discovery whilst browsing this morning …

From Evelyn Rodriguez’ bio on her blog Crossroads Dispatches:

If one could honestly assess the root cause of many business problems – it’d be these intimately related concepts: being open is dangerous and being guided by the echoing fear in our heads is safe.

– Evelyn Rodriguez

Powered by Qumana

A nice substitute for plant tours

One of the enduring benefits of being a consultant over the years has been the opportunity to go on more than my fair share of plant tours. I love the chance to learn about all the ingenuity and creativity that goes into making stuff. If you can’t get to the actual plant tours, here’s one good alternative. Thanks to lifehack for the pointer.

How do they do that?

The National Association of Manufacturing has been posting a weekly video for over two years that shows how things are made. This is a great way to learn new information while being entertained. Some of their past topics are linked below:

The series has been going on for over two years which means there are well over 100 videos available.

How things are made – [Shop Floor]

A few quotes to ponder

 I found these at a blog I’ve recently added to my news aggregator. Both the quotes and the blog are worth your consideration.

Some quotes I really liked

Found these in a completely different context (a discussion group about Prediction Markets); thought that they were wonderful descriptions of the “provisionality” of blogs. See what you think.

Richard Feynman:

In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth.

Niels Bohr
:

Never express yourself more clearly than you think.

[Confused Of Calcutta]

Actually there is another good Feynman quote in the comments to this post that is also worth calling to your attention:

Richard Feynman

For a successful technology, reality must take precedence over public relations, for nature cannot be fooled

Sensemaking practices

There is an excellent discussion of learning as sensemaking going on over at Creating Passionate Users.  Dan Russell has a series of posts (Sensemaking 1, Sensemaking 2, Sensemaking 3) about his thoughts and practices when he takes on a new research based project. In addition to the value of Dan’s thoughts, each post has also sparked excellent discussion threads, which are also worth your time.

Here’s a definition of sensemaking that Russell gets to today:

Sensemaking is in many ways a search for the right organization or the right way to represent what you know about a topic. It’s data collection, analysis, organization and performing the task. [Sensemaking 3]

Sensemaking is a concept I’ve found useful and valuable in much of my work in organizations. I first encountered it in the writings of organizational theorist Karl Weick (e.g. .The Social Psychology of Organizing). Central to Weick and Russell’s thinking is that understanding is something you build over time as an active effort.

My sensemaking practices run along the following lines.

Data Immersion and Convergence. Like Russell and many of the commenters on his posts, immersing myself in the data is a primary component in my sensemaking practices. If I’m doing work inside an organization that includes getting my hands on whatever previous work I can find, public information, interviews, and keeping my eyes and ears open. I am a fan of Yogi Berra’s advice on this; “you can observe a lot just by watching.”

I’ll generally wrap up the initial data collection when things start to converge and get repetitive. Sometimes, this represents a plateau and more data collection will be needed later. More often than not, I have reached to point of diminishing returns and more data by itself won’t help.

Mindmapping and Issue Finding. I’ll draw a variety of mindmaps over the course of most projects. In them, I try out various ways of organizing and relating what I currently know and don’t know. In particular, I’m looking for issues and themes that provide a way to account for the data. With the advent of good software tools for mindmapping (e.g, MindManager), I have started to use my mindmaps as the primary tool to organize and link to the various data I am collecting.

Trip Reports. I’ve mentioned trip reports before as one of my sensemaking habits. At the end of a day collecting data I write myself a memo trying to understand what I might have learned. In my early days as a doctoral student, these were Word documents. They’ve since morphed into private blog entries. They are not transcriptions of my interview notes. Rather, they are first attempts to put my thoughts into story form.

Pictures and Diagrams. Stories are one form of sensemaking, pictures are another. I will play with various kinds of pictures and block diagrams to see what they might reveal about the subject at hand. I almost always start with hand drawn diagrams. If I need to share the drawing, I’ll create an electronic version in Visio. One problem that I sometimes encounter with sharing diagrams in Visio is that they may appear more “precise” than warranted. A partial solution I have had some success with is to use a font called Charette courtesy of the folks at Mindjet. This is a font the mimics the hand-lettering you might see on blueprints and helps convey the notion that what you are looking at should be seen as provisional and subject to revision and elaboration.