Replying to LO26092 --
Some wonderfully rich insights. I want to add just a little voice to the
wisdom flowing here. Rick added this note:
> [Host's Note: Thanks Ana. I agree with your comments on "create.. share..
> store.. evaluate" as a cycle. And, I'm surprised that there is no spot in
> that cycle in which the proposed "knowledge" is used.
to which Patrick Sue responded:
> My interpretation is that Ana is referring to a (cyclical) process in
> which the knowledge is the implied object of the process. When Thomas
> Edison was inventing the light bulb (reportedly after 1000 tries), every
> try was a cycle. What he created each time (except for the last), was
> knowledge about how not to contruct a light bulb. That knowledge wasn't
> actually used in the process, but as input to the next attempt. The final
> bit of knowledge (how to make a sufficiently durable light bulb), was
> presumably used to manufacture light bulbs.
My experience is that knowledge is created on demand (by me or someone
else) or when someone anticipates the demand. The knowledge is "used" by
sharing it. The knowledge can be stored in a dynamic environment. In
this state, it may be referred to as a knowledge object. Once this cycle
begins it might look like this:
a. knowledge demand==>search for knowledge object==>no relevant knowledge
object==>create knowledge==>frame knowledge object==>share
knowledge==>create knowledge object==>store knowledge object
but when cycle "a" begins, we see the potential for cycle "b"
b. knowledge demand==>search for knowledge object==>find relevant knowledge
object==>evaluate knowledge object==>share knowledge==>improve knowledge
object==>store knowledge object==>and so forth
This follows a continual improvement model that improves knowledge as it
is used. I also found that finding a knowledge object that is closely
related to the knowledge that is required frequently shortens the amount
of time needed to develop the new knowledge. In this case, the knowledge
object provides insight for the person creating knowledge (cycle "c")
c. knowledge demand==>search for knowledge object==>find relevant knowledge
object==>evaluate knowledge object==>knowledge object somewhat
relevant==>create new knowledge using insights from somewhat relevant
knowledge object==>share knowledge==>improve knowledge object==>store
knowledge object==>and so forth
This process allows people to reuse knowledge that's been created before.
It also allows them to capture knowledge as they create it (or at least as
synchronously as the author is capable of doing this). In any case,
people still create the knowledge, often in collaboration with others.
This is just a way to capture what they create in a format that
facilitates reuse by others. I refer to this as "just-in-time"
knowledge...as it's found, created, shared, or improved when it's needed.
"Richard Holloway" <firstname.lastname@example.org>
Learning-org -- Hosted by Rick Karash <Richard@Karash.com> Public Dialog on Learning Organizations -- <http://www.learning-org.com>
"Learning-org" and the format of our message identifiers (LO1234, etc.) are trademarks of Richard Karash.