Library clips

sharing ideas thoughts and feedback

June 1, 2011

The inventors notebook : the lost and found of KM

Filed under: km

"….the blueprints for the Saturn rocket have been lost and much of the knowledge of the 400,000 engineers that made the first moon landing possible lies in documents that are devoid of meaning without the contextual and personal knowledge of those who generated them."

Jon Glesinger

"NASA had lost knowledge of how to manufacture the material because it had kept few records of the process when the material was made in the 1980s, and almost all staff with expertise on production had retired or left the agency"

How the US forgot to make Trident missiles

The cost of knowledge, in this case lost knowledge and attrition, is one of the reasons that we need a KM department; to coach and counsel organisations in the value of knowledge, and moreso the lack of resilience in a loss of knowledge.

A lot of KM has to do with knowledge sharing, (especially across silos), accessing people who can help, communication, and awareness…and we claim the lack of this is partly to blame for disasters perhaps like "Tsunami Japanese Nuclear Plant" the "Challenger space shuttle disaster", "9-11" etc…just quietly this may be more a problem of seeing the world as connecting the dots, rather than anticipatory awareness.

In this case the aspect of KM I’m talking about is observable work…which of course can help with awareness and other points I’ve mentioned above, but it also helps in understanding why decisions were made. If we can find the workings out, the work-in-progress, the thinking out loud conversations, the peripheral information, then we will understand the meaning and the context behind decisions.

Not only that, we can re-mix these nuggets of work-in-progress and assemble them with other thinking to create something entirely new…this is KM as a flow or as a flux…fragments connecting, morphing…

"Why was this decision made in paragraph 2 on page 3…I want to use the thinking behind this for something else" asks the manager.

"I’m not sure, it must be in emails, minutes of meetings, buried in our repository…one of those people are currently on vacation and the other has left the organisation" says the worker.

That’s right our knowledge is in our head and is represented in conversation and email communications…where it goes to die. Hence Ross Mayfield’s brilliant insight in using social tools for doing work; which retains the represented knowledge by default. Not only this; but it can be commented on, talk to the author, re-used, enhanced, re-mixed…

In a comment on a past post I likened this to a maths problem:

"Again this is like a maths solution to me in a way

From equation to solution

- show me the workings out

- show me all the paths that we took that failed

- in essence show me all the conversations around each step in both the failed paths and successful path"

And all this brings me to the idea of having an inventors notebook and diary; all the thinking (and the "way" they think), workings out, conversations, peripheral information, and even failed attempts and wrong paths.

Without this how do we know why decisions were made (make sense of something without the underlying context), why they may have failed to see some things (again the context of the time or situation may give clues), what to avoid (which helps to not re-invent the wrong wheel), how to replicate starting conditions, how to re-create things, and how to take a fragment that made up a product and use it in another product.

Not just the know-what, but the know-why, and a glimpse into the know-how.

If we go back to the NASA documents; they are merely information…KM is not just about content and finished products. The repository of documents is not good enough if you can’t make sense of it…and a best practice may not be able to transfer to the new context or complexity of the situation. We need to connect with the authors or at least see their trails of conversation that led to these documents…only then can we get closer to the know-how and know-why. In this respect KM has more in common with observation, apprenticeship, conversations/stories than it does with organising documents (information management).

Here’s an example:

"In a blog post in January 2009, Gowers asked whether spontaneous online collaborations could crack hard mathematical problems—and if they could do so in the open, laying the creative process out for the world to see.

As Gowers wrote on his blog, Polymath may be “the first fully documented account of how a serious [math] research problem was solved, complete with false starts, dead ends, etcetera.” Or, as Tao puts it, the project was valuable because it showed “an example of how the sausage is made.”

Problem Solved, LOL: Scientific American

 

If you want an extended look at this thinking consult my two posts:

The know-why tragedy : divorced from my work on the cutting room floor

Real KM : It’s about the match play, not the scoreboard

3 Comments »

The URI to TrackBack this entry is: http://libraryclips.blogsome.com/2011/06/01/the-inventors-notebook-the-lost-and-found-of-km/trackback/

  1. John - Thank you for the excellent post! Your point on the value of an inventors notebook or diary is very well taken. Many research establishments such as Bell Labs or NRL had a policy requiring researchers to use permanently bound, sequentially page numbered, quad ruled lab notebooks - primarily for patent purposes. But the utility of these notebooks and serial files was much broader.

    I believe this practice was part of Doug Engelbart’s background when he decided to call his Augment / NLS system a Journal:

    Our Journal system was conceived by this author in about 1966. I wanted an underlying operational process, for use by individuals and groups, that would help bring order into the time stream of the Augmented Knowledge workers. The term “journal” emerged early in the conceptualization process for two reasons:

    1) I felt it important in many dynamic operations to keep a log (sometimes termed a “journal”) that chronicles events by means of a series of unchangeable entries (for instance, to log significant events while evolving a Plan, shaping up a project, trouble-shooting a large operation. or monitoring on-going operations). These entries would be preserved in original form, serving as the grist for later integration into more organized treatments.

    2) I also wanted something that would serve essentially the same recorded-dialogue purpose as I perceived a professional journal (plus library) to do.

    Compcon 75 Digest, Sep 1975 pp 173-178, Douglas C. Engelbart THE NLS JOURNAL SYSTEM see the full paper, courtesy of the Doug Engelbart Institute.

    Comment by Greg Lloyd — June 2, 2011 @ 1:27 pm

  2. Awesome as always Greg…it always come back to observable work.

    The fact that a journal is not outcomes based like a report, it’s more raw truths

    From the Black Swan:
    http://johntropea.tumblr.com/post/47312505

    “The journal was purportedly written without…knowing what was going to happen next, when the information available…was not corrupted by the subsequent outcomes.” “While we have a highly unstable memory, a diary provides indelible facts recorded more or less immediately; it thus allows the fixation of an unrevised perception and enables us to later study events in their own context. Again, it is the purported method of description of the event, not its execution, that was important.”

    Comment by John Tropea — June 3, 2011 @ 3:19 am

  3. Old school blogging (11mins)
    Darwin’s notebooks…in the enlightenment they were called “commonplace” books…people would record quotes from people and add their own ideas and sketches and thinking…
    http://johntropea.posterous.com/rsa-where-do-good-ideas-come-from

    Comment by John Tropea — October 14, 2011 @ 3:07 am

RSS feed for comments on this post.

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>



Anti-spam measure: please retype the above text into the box provided.

Please note that comments are moderated and will                  not therefore appear immediately.
                    Please do not repost.


Library clips
Library clips Subscribe by Email                                                    

Get free blog up and running in minutes with Blogsome | Theme designs available here

Related Posts Plugin for WordPress, Blogger...