John,
(01)
Thank you for the suggestions and the link,
(02)
Yefim (Jeff)
(03)
-----Original Message-----
From: ontolog-forum-bounces@xxxxxxxxxxxxxxxx
[mailto:ontolog-forum-bounces@xxxxxxxxxxxxxxxx] On Behalf Of John F. Sowa
Sent: Thursday, May 26, 2011 11:51 AM
To: ontolog-forum@xxxxxxxxxxxxxxxx
Subject: Re: [ontolog-forum] "tribal knowledge"
(04)
Dear Matthew, Yefim, and Dave,
(05)
I agree with all your comments, and I'd like to make a suggestion.
(06)
MW
> Some managers were demanding that their knowledge management
> team capture all the knowledge about the business they were in
> (construction) so that the business could be largely deskilled...
(07)
That's a good anecdote, which illustrates the point that trying
to "deskill" anything can lead to disaster. But there are other
important reasons for capturing knowledge.
(08)
YZ
> We constantly re-discover “stuff” in the long meetings and phone
> conversations... there are ways to significantly reduce the
> information gaps and the need for re-discovery.
(09)
That is the real goal: record and preserve knowledge so that
relevant knowledge can be found as needed.
(010)
Search engines can find documents, and they're easy to use.
But they can't find tacit knowledge, they often find too many
irrelevant documents, and they can't find exactly which parts
of which documents address the problem.
(011)
DMC
> I think we need to make as much knowledge explicit as we can
> to help the great number of people move up from beginnerhood,
> but at the same time we need to recognize that the higher skill
> levels need tacit knowledge that they can only get through
> practice and tutoring.
(012)
Yes, and I agree that there are no easy answers.
(013)
YZ
> Check the Rules Collector link.
> http://www.faqs.org/patents/app/20090144219
(014)
That looks like a good basis for some useful technology.
But I would like to suggest something simpler, which could
be used for the Rules Collector and many other purposes.
(015)
We need tools with the following requirements:
(016)
1. Support more focused search than Google.
(017)
2. Acquire and record tacit knowledge from experts.
(018)
3. Organize and present the knowledge at multiple levels:
glossary, executive summary, introductory tutorial,
and expert or professional-level detail.
(019)
4. Able to support further refinement and formalization in
databases, knowledge bases, and executable code.
(020)
As a first step, I suggest FactGuru as a useful tool. FG can
begin as a glossary that can be elaborated with more detail
as needed. Furthermore, it can support options to display
different amounts of detail in English-like formats, diagrams,
and any computer notation.
(021)
See the FG web site and look at the examples:
(022)
http://factguru.com
(023)
For further info, contact Doug Skuce (on cc list above).
(024)
John
(025)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
(026)
This E-Mail has been scanned for viruses.
(027)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J (028)
|