THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


S U M M A R Y


DIARY: July 10, 2002 08:42 PM Wednesday; Rod Welch

John Maloney letter on Manhattan Project for Knowledge Sciences.

1...Summary/Objective
2...Manhattan Projects Attract Resources for Solving Important Problems


..............
Click here to comment!

CONTACTS 
0201 - Knowledge Management Consortium, In  800 340 7064
020101 - Mr. John Maloney; President =415 820 2351
020102 - kmcluster@collaboratory.com

SUBJECTS
Manhattan Project for Knowledge Sciences, John Maloney
Secret SDS Only KM Design Counterintuitive Difficult to Discover Arch
Disallusioned KM Too Difficult Giving Up Technology Cannot Improve Ma
Work Product Inability Other Methods Generate KM Work Product Shows K
Innovation Loop Programmers Don't Know What to Program to Improve Man
SDS Standard Knowledge Management, 000907
Manhattan Project for Knowledge Sciences, John Maloney
SDS Only Example of Anyone Doing KM, Bill Bearden
Knowledge Management Many Projects Need Solution

1711 -
1711 -    ..
1712 - Summary/Objective
1713 -
171301 - Follow up ref SDS 60 0000, ref SDS 57 0000.
171302 -
171303 - Received ref DRT 1 0001 from John Maloney saying...
171304 -
171305 -   1.  The Behavioral Computational Neuroscience Group and The
171306 -       OntologyStream are proposing a Manhattan Project to establish
171307 -       the Knowledge Sciences:
171309 -          ..
171310 -         http://www.bcngroup.org/area3/manhattan/sindex.htm.
171311 -
171312 -            [On 030427 Paul Prueitt proposes support for a Manhatten
171313 -            project to develop Knowledge Sciences. ref SDS 62 RJ52
171315 -        ..
171316 -   2.  The BCNGroup Founding Committee asks that we forward information
171317 -       about this Project to a wide audience!
171319 -        ..
171320 -   3.  The link at...
171321 -
171322 -         http://www.bcngroup.org/area3/manhattan/sindex.htm
171323 -
171324 -       ...has a button and Java script to automate the sending of
171325 -       e-mail about the Manhattan project to e-mail addresses that you
171326 -       enter.
171328 -  ..
171329 - John's report that people are willing to spend more money to work on
171330 - KM is heartening, and shows continued interest in advancing from
171331 - information to a culture of knowledge, as proposed to SRI in the
171332 - letter on 001011. ref SDS 31 0001
171334 -  ..
171335 - Earlier this was proposed to LANL in a letter on 000731, ref SDS 30
171336 - 0900, and more recently on
171338 -  ..
171339 - Submitted ref DIT 1 0001 saying....
171340 -
171341 -   1.  As we have discussed, a "knowledge" sciences effort indicated in
171342 -       your letter on July 8, is important, but has proven elusive, as
171343 -       reported by Dave Snowden at IBM in the paper you cited in a
171344 -       letter on 020608. ref SDS 52 ZN6I
171345 -
171346 -          [On 020718 Eric Armstrong commends the letter today reviewing
171347 -          challenges developing KM. ref SDS 61 0001
171349 -        ..
171350 -   2.  You may recall that on 991217 we attended a KM event in San
171351 -       Ramone, ref DIT 1 WQ5O, where the attendees did not know
171352 -       anything about KM. ref SDS 18 9030
171354 -        ..
171355 -   3.  Subsequently, on 991221 you sent a letter that suggested helping
171356 -       Doug Engelbart and the people at SRI ref DIT 1 ZR6L, with their
171357 -       goal to advance KM, ref SDS 19 0001, using a similar
171358 -       Manhattan-project- like effort called out in your letter on
171359 -       020708, per above. ref SDS 0 0001
171361 -        ..
171362 -   4.  On 991222 review of Doug's writings showed interest in fostering
171363 -       a new way of thinking and working. ref SDS 20 3696  Discussion
171364 -       with Doug, ref DIT 1 YB7J, showed interest in learning about
171365 -       Communication Metrics that empowers people to use Knowledge
171366 -       Management. ref SDS 20 0837
171368 -        ..
171369 -   5.  On 000120 the central dilemma of KM was presented to Doug's
171370 -       group, ref DIT 1 KD8I, about defining a meaningful distinction
171371 -       between information and knowledge. ref SDS 22 5063
171373 -        ..
171374 -   6.  On 000212 Eric Armstrong made some progress, ref DIT 1 WI9F, on
171375 -       this issue. ref SDS 23 G49J
171377 -        ..
171378 -   7.  On 000324 SRI reported other KM projects had failed, adding
171379 -       urgency to resolving the dilemma of Knowledge Management that
171380 -       prevents progress on advancing from IT to a culture of
171381 -       knowledge, ref SDS 24 4877, and presaging Dave's report two (2)
171382 -       years later on 020608 that KM has failed to meet expectations
171383 -       for improving information technology, ref SDS 52 ZN6I, per
171384 -       paragraph one, above.
171386 -        ..
171387 -   8.  On 000407 Doug's SRI group was reminded about the need to define
171388 -       knowledge, ref DIT 1 RT4N, in order to avoid failure that
171389 -       plagues other projects, as previously suggested on 000120.
171390 -       ref SDS 25 2805
171392 -        ..
171393 -   9.  However, on 000503 Eric reported this task is too difficult.
171394 -       ref SDS 27 5033  A month or so after Eric's report, the entire
171395 -       team adopted Eric's position, ref DIT 1 QP5J, that there is not
171396 -       enough knowledge about knowledge to develop technology to
171397 -       support Knowledge Management. ref SDS 29 6271
171399 -        ..
171400 -  10.  Since that time, there has been a lot of discussion for over two
171401 -       (2) years about ontology, Wiki, SOAP, dialog maps, IBIS, C++,
171402 -       Java, collaboration, semiotics, topic maps, et al., but there
171403 -       has been no progress on understanding a meaningful distinction
171404 -       between information and knowledge that enables advance from IT
171405 -       to KM, ref DIT 1 RQ6I, as seen by Dave Snowden's report which
171406 -       you submitted on 020608. ref SDS 52 ZN6I
171408 -        ..
171409 -  11.  For example, on 001025 Doug Engelbart made a simple request for
171410 -       people to put a link or two in communications that show
171411 -       alignment between current perspective and related information
171412 -       that provides context, ref SDS 33 00VU, and, also, helps grow a
171413 -       culture of knowledge by giving people experience working with
171414 -       connections of cause and effect. ref DIT 1 0Z3F Doug's request
171415 -       reflects good management practice calling for an audit trail
171416 -       showing traceability to original sources, reviewed on 950721.
171417 -       ref SDS 8 1740
171419 -        ..
171420 -  12.  This request has not been met, ref DIT 1 T34I, as Dave Snowden
171421 -       relates in his paper, which you submitted on 020608. ref SDS 52
171422 -       ZN6I
171423 -
171424 -
171425 -
171426 -
1715 -

SUBJECTS
Best Brightest Mental Biology Overwhelmed Information Overload Needs
Manhattan Project Uses Best Brightest Focus Resources Solve Technical

3204 -
320501 -  ..
320502 - Manhattan Projects Attract Resources for Solving Important Problems
320503 -
320504 -
320505 -  13.  People revert to calling projects "Manhattan" in hopes of
320506 -       creating sufficient attention for empowering improvement,
320507 -       following the model of WWII, where the bombing of Pearl Harbor
320508 -       and fear of German success with nuclear ordinance focused
320509 -       attention on solving a complex problem. ref DIT 1 Q54O
320510 -
320511 -          [On 020718 Eric Armstrong comments on ingredients that enable
320512 -          a Manhattan Project to succeed. ref SDS 61 PQYP
320514 -           ..
320515 -          [On 030427 Paul Prueitt proposes Manhatten project for
320516 -          Knowledge Sciences. ref SDS 62 RJ52
320518 -        ..
320519 -  14.  In that case, people working on the problem understood the
320520 -       underlying science, but had to work out technicalities of
320521 -       implementation (according to the movies I have seen).  The
320522 -       difficulty in the case of KM, ref DIT 1 175J, is that the design
320523 -       seems to be a secret, as shown in the record on 000425.
320524 -       ref SDS 26 0480  The people at Microsoft, IBM, Yale, Stanford,
320525 -       and so forth don't have an underlying concept to follow because
320526 -       the distinction between information and knowledge seems to
320527 -       require experience doing KM in order to discover and understand
320528 -       the core process of converting information into knowledge.  So
320529 -       far, nobody has time to gain this experience, shown by lack of
320530 -       response to Doug's request on 001025, ref SDS 33 00VU, as
320531 -       reported on 001026. ref SDS 34 0001
320533 -        ..
320534 -  15.  Moreover, once the secret is discovered a new set of social
320535 -       problems arise, ref DIT 1 P46L, because the light of knowledge
320536 -       brings the burden of responsibility, under the rule "So-and-so
320537 -       knew, or reasonably should have known," as related on 990527.
320538 -       ref SDS 15 0001
320540 -        ..
320541 -  16.  As a result, fear of accountability makes the light of knowledge
320542 -       a greater burden than the darkness of ignorance, ref DIT 1 YF7I,
320543 -       under the legend of Prometheus reviewed on 991108. ref SDS 17
320544 -       XP53
320546 -        ..
320547 -  17.  This record seems to suggest that a Manhattan project can be
320548 -       effective for KM. I was just curious whether anyone has focused
320549 -       on these thorny issues that have persisted for several thousand
320550 -       years. ref DIT 1 JH7O
320551 -
320552 -          [On 020718 Eric Armstrong commends the letter today reviewing
320553 -          challenges developing KM. ref SDS 61 0001
320555 -           ..
320556 -          [On 030427 Paul Prueitt proposes Manhatten project for
320557 -          Knowledge Sciences. ref SDS 62 RJ52
320558 -
320559 -
320560 -
320561 -
320562 -
320563 -
320564 -
320565 -
320566 -
320567 -
Distribution. . . . See "CONTACTS"