Replying to LO24830 --
Doc,
thank you for your reply. I have also read your reply on knowledge
communities as a valuable comment, as well as recent contributions of Bill
Harris, thank you to you as well.
>The only thing that occurred to me that you may want to add is a
>methodology that integrates the use of the designed application into the
>workflow. Creating, contributing to and receiving value from a tool like
>this can only happen if it happens in their regular workflow. By the way,
>there are a few organizations that have integrated SAP with a
>knowledgebase tool...and they find this provides far more capability.
Which workflow? ;-))
Can you add a few keynotes on integrating SAP with knowledgebase tools?
>Also, it's often more practical to give people what they're looking for at
>the time that they're looking for it. Keywords are an inefficient way to
>search. Structuring your content can facilitate finding info so it can be
>used when needed.
The clue is that we don't give people any content in the beginning. They
have to create it themselves or it won't exist. So the content need to be
structured while it evolves.
What I am trying now is to collect those few, easy to understand starting
rules which will kick off this evolution. Of course then the issue of
searching for information added somewhen in the past will arise earlier or
later. I am thinking of structuring the growing content according to the
given keywords in a database.
The first aim I am targeting is to gain a sense of benefit for especially
sales people to contribute to broader sharing of current information which
is most valuable today but maybe not anymore tomorrow.
What do you think?
Liebe Gruesse,
Winfried
--"Winfried Dressler" <winfried.dressler@voith.de>
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.