THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: April 11, 2001 02:50 PM Wednesday;
Called Jack Park about peer review on KM explanation in POIMS.
2...Peer Review Does Not Comment on KM Opportunity Presented in POIMS
....AI, Web Page Engineers Do Not Have Architecture of Human Thought
....Killer Application Requires Effective Architecture
....Effective Architecture Requires Tools Used a Lot by Everybody
....Architecture Human Thought Key to Knowledge Management
....Case Study Email Limitations Collaboration Knowledge Management
....Collaboration Email Limitations Knowledge Management Case Study
....Knowledge Management Email Limitations Collaboration Case Study
....Email Weaknesses Case Study Collaboration Knowledge Management
....Knowledge Space Needs More Contributors
....Only One Person is Using SDS to Support Knowledge Space
....SDS Record on Internet Has Been Created by Only One Person
....Communication Requires Notice and Accountability
....SDS Adds Deliberation to Realtime Discussion, Calls, Email
....Realtime Discussion is Different from Deliberative Analysis
....Knowledge Space Transitions from IT to Culture of Knowledge
....Remembering Every Little Thing Supported by SDS Amazing
....Usefulness Requires Making Use of the Record, i.e., Action Items
....One-sided Musings Not Useful, Sometimes Incorrect - Need Feedback
....Collaboratory Turns SDS Space Over to Online Issue-Based Discussion
....SDS Supports Computer Aided Thinking That May Lead to AI
....Truth is a Moving Target Maintained by Alignment, Feedback
....AI Engine Proposed to Process Information to Create Knowledge
....IBIS Has No Record of Converting Information into Useful Knowledge
Click here to comment!
1...Jack's letter on 001030 reporting KM is hard to understand,
2...Peer review should discuss usefulness of analogies in POIMS
3...Couldn't one or two ideas in POIMS be given serious treatment?
4...This feedback seems incorrect to the extent that the section of
5...Possibly Jack can synthesize realtime and deliberative
6...Would like Jack's comments on "Knowledge Space," defined in
7...Assume a Collaboratory exists. How would it change daily work
8...Jack could help a lot by submitting work product illustrating
9...Jack might submit an example of an IBIS discussion to
0201 - SRI International
020101 - Mr. Pat Lincoln; Director
020103 - Computer Science Laboratory
0202 - SRI International
020201 - Mr. Curtis R. Carlson; President and CEO
020203 - Executive Offices
KM Request Peer Review POIMS Explanation
Peer Review on KM in POIMS, Jack Park, Doug Engelbart, Pat Lincoln
Examples Writing Limited Time Greases Slippery Slope Laziness Cursory
Cursory Analysis Solved by SDS Enables Writing More in Less Time
Park, Jack KM Engineer Developer Resists Reviewing POIMS to Study Wha
2307 - ..
2308 - Summary/Objective
230901 - Follow up ref SDS 68 0001, ref SDS 67 0000,
230903 - Peer review on KM in POIMS, similar to Jack's letter on 000331, would
230904 - be very helpful. ref SDS 0 LN4J Big idea in Jack's letter today, and
230905 - from our telecon, is a desire for realtime editing of other people's
230906 - SDS records on the Internet, perhaps related to Collaboratory Jack is
230907 - planning. ref SDS 0 NV5I SDS supports "deliberative analysis" to
230908 - prepare for realtime communication -- maybe a synthesis can be
230909 - developed, since these should be complimentary. ref SDS 0 237O Jack
230910 - indicates SDS has the same defects that occur in email. ref SDS 0 627F
230911 - He proposes IBIS to improve collaboration. ref SDS 0 NH3O Frustration
230912 - in the letter that only one person is using SDS for anytime, anywhere
230913 - "intelligence, can be corrected by other people getting SDS to
230914 - supplement the SDS record on the Internet to provide a richer
230915 - Knowledge Space. ref SDS 0 633H
230917 - [On 010416 letter to Jack thanking him for comments. ref SDS 71
230918 - 0001
230920 - ..
230921 - [On 010716 follow up letter. ref SDS 77 0001
230926 - ..
2312 - Progress
231301 - ..
231302 - Peer Review Does Not Comment on KM Opportunity Presented in POIMS
231305 - Jack reported having sent a letter on 010409 with peer review on KM
231306 - explained in POIMS, responding to telecon on 010405, ref SDS 69 SH5O,
231307 - following up telecon on 010329, ref SDS 68 SH5O, which was confirmed
231308 - in the letter the same day. ref DIP 3 0001
231310 - ..
231311 - The original request was issued by copy of a letter to Pat Lincoln at
231312 - SRI, ref DIP 2 0001, on 010321, ref SDS 67 5R9O, after making
231313 - additions to POIMS. ref SDS 67 0001
231315 - ..
231316 - While we talked, Jack re-submitted his letter, and I received it in
231317 - the record,
231319 - ..
231320 - Jack indicated today he thought Morris had produced SDS. We reviewed
231321 - the record showing Morris wrote a macro language for an editor that
231322 - evolved into a programming language for SDS, per record on 000723l.
231323 - ref SDS 43 0008 He has made improvements once or twice a year for the
231324 - past 15 years. Prior to that he was more active creating commands
231325 - when needed to maintain progress. He has not worked on SDS design nor
231326 - coding. On 910810 Morris tried using SDS and commented favorably on a
231327 - "breakthrough" design. ref SDS 3 7793 Later on 911121 he found SDS
231328 - was harder to use than conventional methods. ref SDS 4 7420 On 980722
231329 - Morris advised that the SDS design is hard to understand, and
231330 - difficult to reverse engineer. ref SDS 19 3280
231332 - ..
231333 - This reflects IBM's experience finding KM difficult to understand
231334 - and develop, from published article Jack submitted on 001130.
231335 - ref SDS 55 F26K A month earlier on 001031, Jack sent a letter to
231336 - OHS/DKR team noting challenge of KM design. ref SDS 50 0S8L
231338 - ..
231339 - KM is not an easy subject because it requires understanding the
231340 - architecture of human thought, discussed in POIMS. ref OF 1 0561
231342 - ..
231343 - Peer review is more effective, if language from POIMS is quoted, and
231344 - citations are linked, as called out by Doug Engelbart in his letter to
231345 - the OHS/DKR team on 001025. ref SDS 48 00VU This seems to be a
231346 - continuing issue in obtaining useful peer review, see for example the
231347 - record on 990817. ref SDS 24 3660
231349 - [On 010426 peer review from Pat Lincoln provides feedback on the
231350 - language in POIMS. ref SDS 74 IB6N
231352 - ..
231353 - Jack says in his letter today commenting on KM in POIMS.......
231355 - You broke the KM jockeys into two groups, those that talk and those
231356 - that do otherwise. You then marry the talkers with email and
231357 - proceed to show 4 reasons why that is bad. ref DRT 1 4V6F
231359 - [On 071220 case study on Jack's support for SDS "worthy of
231360 - review" as a technology platform that makes Knowledge
231361 - Management an effective tool to improve daily work.
231362 - ref SDS 99 M53N
231364 - ..
231365 - Spontaneous, emotional reaction is not constructive to advance
231366 - Knowledge Management tools and practices. Cursory analysis of
231367 - POIMS aligns with the record on 990718 showing need for tools
231368 - that make analysis fast and easy, based on Drucker's call that
231369 - analysis is essential for good management, reviewed on 931130.
231370 - ref SDS 6 7911 POIMS explains how SDS supports this
231371 - requirement, ref OF 1 QZ4F, and Jack's letter on 000504
231372 - recommended people "ponder" POIMS to make progress on KM.
231373 - ref SDS 37 6082 The difference between advocating that people
231374 - ponder POIMS, and the lack of analysis in Jack's letter today,
231375 - compared to analysis of Jack's letter in this SDS record, shows
231376 - that people lack tools that make analysis fast and easy, like
231377 - SDS does. This conclusion is supported by Cliff Joslyn's
231378 - letter on 000425 disclosing the "wish" to be able to create
231379 - analysis enabled by SDS. ref SDS 34 0001 As a result, the gap
231380 - between good management that people know should be done, and
231381 - recommend be done, and actual practice, demonstrated today,
231382 - creates a widening Knowledge Management dilemma that is
231383 - resolved by giving up, anger, frustration and dispare, noted,
231384 - also by Drucker. ref SDS 6 3851
231386 - [On 010908 Jack reports laziness causes people to press the
231387 - "Reply" button responding on impulse to email, rather
231388 - invest time for deliberative analysis. ref SDS 78 YF5O
231390 - ..
231391 - [On 020610 Dave Snowden at IBM offers cursory analysis of
231392 - POIMS. ref SDS 85 MV9G
231394 - ..
231395 - On the merits of Jack's response, "talkers" and tool makers are
231396 - both related to email, not just the talkers. ref OF 1 CZ6K
231398 - ..
231399 - Jack does not address the explanation in POIMS of a specific
231400 - division between orality and literacy, which is, also,
231401 - summarized as talent and tools, where talent relates to
231402 - reliance on innate capabilities, and tools, like the alphabet,
231403 - the printing press, paper, writing instruments, computers and
231404 - other information technology augment natural talent.
231405 - ref OF 1 O87L Some people like to walk to the store, others
231406 - feel comfortable driving. Similarly, some in the KM movement
231407 - are wary of "mechanized thinking," noted by John Maloney in a
231408 - letter on while others are comfortable with technology for
231409 - information, but not for knowledge, noted by Eric Armstrong on
231410 - 000503. ref SDS 36 5033 This reluctance to analyse POIMS that
231411 - seems to be driven by fear of thinking about "knowledge,"
231412 - creates emotionally charged feelings that present a big hurdle
231413 - blocking progress on KM.
231415 - ..
231416 - Jack's letter on 001030 reporting KM is hard to understand,
231417 - ref SDS 50 0S8L, justifies investing time to understand POIMS
231418 - explanation of KM that offers a fruitful development path for
231419 - working on technology.
231421 - ..
231422 - [On 011003 Jack reports there are no clues for advancing KM
231423 - and there has no progress by anyone reviewing POIMS in
231424 - order to understand SDS.
231426 - ..
231427 - Alphabet technology, ref OF 1 ER3G, and Phaedrous are cited in
231428 - POIMS to show a deep, historical, emotional tear in the human
231429 - psyche between natural talent, and using tools to augment,
231430 - particularly mental, talent. ref OF 1 PY8O Since psychological
231431 - conflict hinders progress on KM, and since progress on KM can
231432 - reduce bumbling that causes loss, crisis, conflict and calamity
231433 - that disrupts lives due to recession, when too many people are
231434 - having too many problems, reported on 001207, ref SDS 57 MZ7G,
231435 - the opportunity to redress this condition justifies investing
231436 - time to understand implications that help formulate a useful
231437 - theory of knowledge.
231439 - ..
231440 - Peer review should discuss usefulness of analogies in POIMS
231441 - between orality and literacy, and talent and tools. Peer
231442 - review could strive to understand why alphabet technology is
231443 - put forward as the core of KM, relative to integrating time and
231444 - information; and, it might address meaning drift, false
231445 - knowledge, alignment, organic subject structure, Knowledge
231446 - Space, intelligence, Com Metrics, the management cycle,
231447 - thinking through writing. In other words, there are a lot of
231448 - ideas in POIMS, but none are addressed in the letter today.
231450 - ..
231451 - Couldn't one or two ideas in POIMS be given serious treatment?
231453 - ..
231454 - Two examples of useful peer review are.....
231456 - 1. Jack's letter on 000331. ref SDS 32 3905
231458 - 2. Gary Johnson's letter on 001222, ref SDS 59 K58L, and
231459 - more recently on 010408. ref SDS 70 FT4N
231461 - ..
231462 - Limited bandwidth cited by Doug on 000221, ref SDS 28 V2GS,
231463 - prevents learning KM, which Jack noticed in a letter on 001031.
231464 - ref SDS 50 0S8L It is a KM dilemma. Limited span of attention
231465 - delays discovering what works, because people are busy on
231466 - other things that seem attractive at the moment. see POIMS,
231467 - ref OF 1 2050
231469 - [On 010416 letter to Jack was linked to this record
231470 - providing opportunity for further comment. ref SDS 71 0001
231472 - ..
231473 - [On 010716 follow up letter. ref SDS 77 0001
231476 - ..
231477 - AI, Web Page Engineers Do Not Have Architecture of Human Thought
231480 - Jack says....
231482 - Your first point, that there exists (implied: as far as you know)
231483 - no evidence that AI and web pages can support (your words) an
231484 - effective architecture for human intelligence. Gads, that's a huge
231485 - one to hoist aboard. ref DRT 1 346J
231487 - This refers to the POIMS section that says....
231489 - There is no record that AI and web page engineers can
231490 - support an effective architecture for human intelligence.
231491 - ref OF 1 084J (which is linked to the explanation of
231492 - "intelligence," in the paper. ref OF 1 0367
231494 - ..
231495 - Possibly Jack could provide an example of AI and/or web page
231496 - engineering using an architecture of human thought that
231497 - improves handling of daily working information set out in
231498 - Doug's 1972 paper, reviewed on 000327. ref SDS 30 3971
231500 - ..
231501 - On 000324 Lee Iverson reported research by SRI shows that KM
231502 - projects have failed, which was cited as an opportunity for the
231503 - OHS/DKR project to succeed by providing missing ingredients.
231504 - ref SDS 29 4877 The following week Marcello Hoffman reported
231505 - that research by his group at SRI shows that Doug Engelbart's
231506 - work is the only useful information SRI has discovered on KM.
231507 - ref SDS 31 0713 On 000504 there was a report during a meeting
231508 - at SRI that Doug wanted more work on understanding "knowledge"
231509 - in order to develop DKR tools. On 000615 the DKR team reported
231510 - consensus that there is not enough knowledge to develop KM.
231511 - ref SDS 40 6271 On 001031 Jack cited this record noting lack
231512 - of progress, even while having continual and unique KM support.
231513 - ref SDS 50 I67L On 001130 Jack submitted an article reporting
231514 - IBM could not produce KM by upgrading Lotus Notes, ref SDS 55
231515 - F26K IBM invested $4B to get Lotus Notes, and likely several
231516 - $100M more to convert LN to KM.
231518 - ..
231519 - This record shows KM is a counterintuitive capability that is
231520 - subtle and, therefore, difficult to discover. It, also, shows
231521 - that AI engineers do not have a theory of human intelligence
231522 - that can be readily translated into useful KM tools for
231523 - producing better knowledge work.
231525 - ..
231526 - Research in cognitive science on 900319 indicates that "memory"
231527 - is a powerful factor of human intelligence. ref SDS 2 1323
231529 - ..
231530 - Jack notices in his letter today that Rod "remembers every
231531 - little thing," which indicates SDS provides a practical way to
231532 - augment human intelligence, which is a goal of OHS/DKR,
231533 - reported by Eric Armstrong on 000423, ref SDS 33 5096, and it
231534 - solves a big problem. see below. ref SDS 0 RY3M
Architecture Computers Integrate with Architecture of Human Thought
Architecture KM Hard to Design, Not Understood
Intelligence Improves Daily Knowledge Work
DKR Difficult to Design, Not Enough Known about Knowledge, KM, 000615
Architecture Human Thought Intelligence in POIMS, 010411
AI Does Not Have Architecture of Human Thought for Reasons in POIMS,
Knowledge Connects Experience into Chronologies of Cause and Effect
Killer App Collaboration Communication Civilization Shows Cost Saving
Effective Architecture Used by Many a Lot for Everything, Alphabet, M
371201 - ..
371202 - Killer Application Requires Effective Architecture
371203 - Effective Architecture Requires Tools Used a Lot by Everybody
371204 - Architecture Human Thought Key to Knowledge Management
371207 - Jack says....
371209 - I suppose that elsewhere in your verbiage, there exist words that
371210 - properly lay out an *effective architecture that supports human
371211 - intelligence* I have not seen anything that I can explicitly
371212 - identify as an architecture that suits that problem space, whatever
371213 - that problem space is. ref DRT 1 7G6O
371215 - This feedback seems incorrect to the extent that the section of
371216 - POIMS Jack discusses, ref OF 1 084J, is linked to a theory of
371217 - cognition in the POIMS paper that is supported by the SDS
371218 - design. Cognition covers thinking, knowledge, intelligence,
371219 - information. Would like Jack to comment on this section, since
371220 - it explains the problem KM can solve. ref OF 1 0367 Jack
371221 - recognized on 000426 that SDS is a proof of concept for KM,
371222 - ref SDS 35 3315 A comprehensible explanation of the theory
371223 - that makes SDS possible is needed to understand SDS.
371225 - ..
371226 - "Problem space" SDS addresses is the need to move from IT to a
371227 - culture of knowledge that implements a form of Knowledge Space
371228 - for solving the problem of information overload, which
371229 - accelerates meaning drift leading to bumbling, loss, crisis,
371230 - conflict and calamity. Traditionally, the only way out is an
371231 - imploding management that downsizes (see NWO, ref OF 3 4925),
371232 - commonly called a recession that occurs when too many people
371233 - are having too many problems, see on 001207. ref SDS 57 V54M
371235 - ..
371236 - Therefore, it is difficult to grasp why "problem space" is
371237 - questioned, when it is discussed in POIMS, and everybody
371238 - confronts the tension between limited time and accuracy every
371239 - day, due to information overload that causes meaning drift,
371240 - false knowledge and bumbling.
371242 - ..
371243 - "Effective" means an architecture for technology that can be
371244 - used every day, all day long (24 7) by anyone for any subject
371245 - to add "intelligence" to information that improves daily work.
371246 - So it is a much broader objective than collaboration. A key
371247 - component of being "effective" is "alignment" that avoids
371248 - meaning drift, since that problem makes daily work ineffective.
371249 - The alphabet and mathematics are "effective" technologies,
371250 - because they can be used by anyone, anywhere, anytime to
371251 - strengthen human thought, i.e., natural talent, for any
371252 - subject. POIMS explains improving alphabet technology by
371253 - integrating with the mathematics of time and organic structure
371254 - developed for accounting creates a spreadsheet for knowledge.
371255 - For convenience, we simplify and say integrating time and
371256 - information produces knowledge. ref OF 1 1232 Since
371257 - "knowledge" is used regularly, everyday, like information, SDS
371258 - is a new kind of "effective" technology that provides a
371259 - "killer" or compelling, application, which the PC industry has
371260 - sought in order to maintain industry growth, as reported Larry
371261 - Ellison, Oracle Corporation, during an industry event on
371262 - 970222. ref SDS 17 8529 This elements make SDS an "effective"
371263 - architecture, and a disruptive technology, explained on 990527.
371264 - ref SDS 23 5258
371266 - ..
371267 - Jack commented previously on 000503 that Knowledge Space is a
371268 - useful step, ref SDS 36 6138, and on 001116 he joined Paul
371269 - Fernhout in recognizing SDS is a powerful new capability,
371270 - ref SDS 52 0001, so why should there be reluctance on this
371271 - occasion to discuss in a constructive way market conditions
371272 - surrounding KM, and the problems of meaning drift and false
371273 - knowledge which SDS strives to redress, as set out in POIMS?
Email Limitations in POIMS Poorly Crafted, Jack Park
520401 - ..
520402 - Case Study Email Limitations Collaboration Knowledge Management
520403 - Collaboration Email Limitations Knowledge Management Case Study
520404 - Knowledge Management Email Limitations Collaboration Case Study
520405 - Email Weaknesses Case Study Collaboration Knowledge Management
520407 - Follow up ref SDS 70 9H8H, ref SDS 67 ID6M.
520409 - Jack continues...
520411 - ....email does help me to *do the right thing* on occasion, and
520412 - sometimes not. ref DRT 1 U58F
520414 - ....your four arguments against email are poorly structured, and
520415 - maybe wrong. ref DRT 1 4R8H
520417 - [On 010420 Jeff Conklin explains limitations of email for
520418 - organizational memory, collabortion, and knowledge
520419 - management. ref SDS 72 087F
520421 - ..
520422 - [On 010908 Jack explains laziness makes email attractive,
520423 - ref SDS 78 FV4G, illusion of progress imparts feeling of
520424 - effectance ref SDS 78 YF5O, Jack cites weaknesses of email.
520425 - ref SDS 78 YF3I
520427 - ..
520428 - POIMS explains why email is error prone. ref OF 1 084J
520430 - ..
520431 - Case study shows email reduces productivity....
520433 - 1. Least effective system at Intel... 950927, ref SDS 11 4939
520435 - 2. Diligence "reads her email"
520436 - rarely found on the job........... 951214, ref SDS 12 I741
520438 - ..
520439 - 3. Compounds complexity.............. 960305, ref SDS 14 0001
520441 - ..
520442 - 4. Chatting lacks organization....... 990510, ref SDS 21 8064
520444 - ..
520445 - 5. Morris Jones engineers don't like
520446 - to write, organize, and analyse
520447 - want to do technology............. 990525, ref SDS 22 0966
520449 - ..
520450 - 6. One-sided delayed feedback email
520451 - less accurate than conversation
520452 - makes communication biggest
520453 - risk in enterprise................ 990924, ref SDS 25 0715
520455 - ..
520456 - 7. Medical practice fails............ 990924, ref SDS 25 0715
520458 - ..
520459 - 8. Trip to Mars failed............... 991001, ref SDS 26 3077
520461 - ..
520462 - 9. Improvements urgent............... 000503, ref SDS 36 C48F
520464 - ..
520465 - 10. Morris Jones demonstrates linking
520466 - in email with Microsoft Word
520467 - and Outlook take a lot
520468 - of hard work...................... 000706, ref SDS 42 FPW7
520470 - ..
520471 - 11. Defects in email.................. 000928, ref SDS 46 474N
520473 - ..
520474 - 12. Gary Johnson email many defects... 010408, ref SDS 70 9H8H
520476 - ..
520477 - 13. Jeff Conklin email poor support
520478 - for organizational memory......... 010420, ref SDS 72 087F
520480 - ..
520481 - 14. Pat Lincoln engineers add
520482 - structure that makes email
520483 - effective......................... 010426, ref SDS 74 QY5G
520485 - ..
520486 - 15. Lee Iverson Nodal email difficult
520487 - collaboration cumbersome.......... 010620, ref SDS 76 IR4O
520489 - ..
520490 - 16. Lee Iverson collaboration email
520491 - needs content retrieval........... 010620, ref SDS 76 04HS
520493 - ..
520494 - 17. Lee Iverson Nodal email bloat..... 010620, ref SDS 76 BW9J
520496 - ..
520497 - 18. Jack Park email Reply button
520498 - laziness implusive cursory........ 010908, ref SDS 78 US8O
520500 - ..
520501 - 19. Morris Jones linking Microsoft
520502 - Word and Outlook fast and
520503 - easy.............................. 020110, ref SDS 82 5HYX
520505 - ..
520506 - 20. Federal Acquisition Regulations
520507 - (FAR), industry standards requiring
520508 - good management practices for
520509 - documentation commonly
520510 - ignored........................... 020504, ref SDS 84 NS6F
520512 - ..
520513 - 21. Murray Altheim giving up on
520514 - linking too difficult............. 020820, ref SDS 86 UV6G
520516 - ..
520517 - 22. Murray Altheim giving up on
520518 - accuracy unimportant because
520519 - linking too difficult............. 020820, ref SDS 87 V66I
520521 - ..
520522 - 23. Lotus Notes improves email........ 020822, ref SDS 88 UPWP
520524 - ..
520525 - 24. Lotus Notes customers feel pain... 020822, ref SDS 88 Q99G
520527 - ..
520528 - 25. Groove improves email............. 020822, ref SDS 88 H1WX
520530 - ..
520531 - 26. Limitations frustrating........... 020822, ref SDS 88 HW8H
520533 - ..
520534 - 27. Reduces productivity.............. 020822, ref SDS 88 WO8H
520536 - ..
520537 - 28. Analysis too difficult............ 020822, ref SDS 88 QJ3M
520539 - ..
520540 - 29. Onerous constraints............... 020823, ref SDS 89 WZUS
520542 - ..
520543 - 30. Metadata cannot be added.......... 021031, ref SDS 91 M53H
520545 - 300 unread letters email
520546 - overwhelms span of
520547 - attention......................... 050722, ref SDS 94 RP54
520549 - ..
520550 - 31. Email piling up on computers
520551 - drives people to rely on
520552 - conversation and personal
520553 - memory............................ 060408, ref SDS 95 6O6O
520555 - ..
520556 - 32. Medical Chart shows 4 times daily
520557 - instead of 3 times daily for
520558 - prescribed medication; typing error
520559 - not corrected because there
520560 - is no feedback loop in
520561 - the communication
520562 - process........................... 070302, ref SDS 96 FN5M
520564 - ..
520565 - Jack summarizes....
520567 - In short, for many of the reasons you say that email is bad, so
520568 - might be SDS. ref DRT 1 C95F
520570 - Email is criticized in POIMS for lacking alignment, ref OF 1
520571 - 084J, which was called out by Doug in his letter to the team on
520572 - 001025. ref SDS 48 00VU This record provides links to original
520573 - sources showing SDS supports alignment, which is missing from
520574 - email.
520576 - ..
520577 - Email is criticized in POIMS for being stream-of-conscious
520578 - reaction, which is error prone because it is spontaneous, also,
520579 - called "realtime," and therefore cursory.
520581 - ..
520582 - SDS is deliberative to provide organization, context, history,
520583 - (i.e., chronology), alignment, summary connected to details and
520584 - feedback loops. Preparing summary headings in SDS provides
520585 - structure that is missing from email. SDS linking to original
520586 - sources reveals deviations from alignment that permit timely
520587 - action to avoid problems. SDS linking reveals correlations,
520588 - implications and nuance in relation to collateral information.
520589 - Subject assignments in SDS expand recognition of impacts on
520590 - objectives, overcoming limits of human cognition reported on
520591 - 990303 that limit awareness of "subjects." ref SDS 20 6120
520592 - Organizing the record into logical chunks provides further
520593 - pause for deliberation that strengthens usefulness of the
520594 - record. All of this is missing from email, and other standard
520595 - work practices. SDS provides a lot of firepower that augments
520596 - human intelligence, explained on 950204. ref SDS 8 4995
520598 - ..
520599 - Jack previously notified the OHS/DKR team that....
520601 - "...the ability of SDS to delineate temporal sequences
520602 - appropriate to this discussion is simply amazing. Of
520603 - course, anyone could mine the archives and eventually arrive
520604 - at the same or similar statements, but Rod does it
520605 - automatically, by way of his technology."
520607 - ....in a letter on 001116. ref SDS 52 0001
520609 - ..
520610 - This shows SDS improves conventional work practice, rather than
520611 - replicates defects in realtime communications like email.
520613 - [On 010420 Jack submitted reference to paper by professor
520614 - Jeff Conklin, PhD, who makes similar arguments that email is
520615 - not an effective knowledge capability. ref SDS 72 087F
520617 - ..
520618 - That doesn't mean there are no mistakes in SDS. Feedback is
520619 - called out in POIMS to correct understandings in the record,
520620 - adjust alignment of related context, and plan follow up.
520621 - ref OF 1 2200
520623 - ..
520624 - Realtime communication will remain the dominate force in daily
520625 - affairs. see POIMS, ref OF 1 24A7 SDS strives to add a process
520626 - that helps people be prepared to make realtime communication
520627 - more effective. see POIMS, ref OF 1 6944
520629 - ..
520630 - This is the extent of Jack's comments on the language in POIMS.
Changing SDS Records Proposed for People Other than Original Author
Deliberative Analysis SDS Thinking Through Writing Management Cycle
Be Prepared SDS Provides 80% of Preparation Automatically
Changing SDS Records Proposed for People Other than Original Author
Knowledge Space Needs More Contributors 1-sided Interpretation Needs
Feel Good Management Notice Accountability for Communication to Align
Accountability Communication Provided by Notice Requirements
Anger Notice Communication Accountability Frustrates Feel Good Manage
Deniability Wiggle Room Fear Accountability SDS Maintains Alignment A
741201 - ..
741202 - Knowledge Space Needs More Contributors
741203 - Only One Person is Using SDS to Support Knowledge Space
741204 - SDS Record on Internet Has Been Created by Only One Person
741207 - Jack criticizes SDS content on the Internet, saying....
741209 - ....one of the problems I have harped on for a long time now with
741210 - your rendition of an SDS: it's just YOUR rendition, not mine and
741211 - not anybody else's. ref DRT 1 GJ8O
741213 - [...below, Jack proposes re-implementation that enables
741214 - people to edit SDS records on the Internet. ref SDS 0 NV5I
741216 - ..
741217 - SDS is a software "rendition" of requirements specified for
741218 - POIMS technology. ref OF 1 0001
741220 - ..
741221 - Jack may have in mind here that content on the Internet created
741222 - with SDS, so far, has only been prepared by Rod Welch, which
741223 - reflects one-sided work product interpreting daily information.
741225 - ..
741226 - This is easily remedied.
741228 - ..
741229 - SDS enables everyone to augment intelligence to think, remember
741230 - and communicate, explained in POIMS. ref OF 1 3742 If there is
741231 - demand for others to use SDS, markets empower people to satisfy
741232 - that demand, as proposed in a letter to Jack and other OHS/DKR
741233 - team members on 001121. ref SDS 53 XU8I
741235 - ..
741236 - On 001126 Eugene Kim recommended people learn KM by greater
741237 - diligence using IT, instead of SDS. ref SDS 54 QW8I The same
741238 - day, Grant Bowman pointed out this doesn't work. ref SDS 54
741239 - X8PW Jack's letter letter today supports Grant.
741240 - ..
741241 - Therefore, the remedy is to buy SDS and issue content
741242 - that expands interpretations on the Internet. SDS can be
741243 - improved to reflect the vision and talents of others, as Jack
741244 - proposed on 001130. ref SDS 56 0001 We cannot do everything at
741245 - once. But we can try in good faith to make steady progress.
741248 - ..
741249 - Communication Requires Notice and Accountability
741250 - SDS Adds Deliberation to Realtime Discussion, Calls, Email
741251 - Realtime Discussion is Different from Deliberative Analysis
741252 - Knowledge Space Transitions from IT to Culture of Knowledge
741255 - Jack says SDS is....
741257 - ....just an enormous information space filled with records of
741258 - events that have crossed your path, and a collection of your
741259 - musings on those events. Powerful stuff, that, but there is no room
741260 - for realtime discussion. Rather, discussion comes in the form of
741261 - clippings from emails or phone conversations (which, on occasion,
741262 - contain improper or wrong *interpretations* of what you heard),
741263 - followed by lots more stuff that reads like a muse. ref DRT 1 BK9J
741265 - [...below, Jack proposes re-implementation that enables
741266 - users to edit SDS records on the Internet. ref SDS 0 NV5I
741268 - ..
741269 - Possibly Jack can synthesize realtime and deliberative
741270 - communication based on the following....
741272 - ..
741273 - Below, Jack proposes a Collaboratory, which may entail realtime
741274 - editing. ref SDS 0 NV5I
741275 - ..
741276 - In our discussion during the call today, Jack seemed to
741277 - explain a desire to edit Rod's records, rather than create his
741278 - own, and/or submit feedback correcting the record. This
741279 - violates good communication practice. If party A receives a
741280 - letter from party B, there is no entitlement for party A to
741281 - change party B's letter, because that would vitiate the
741282 - practice of notice that provides accountability to make
741283 - communication effective. see book on management reviewed
741284 - 970829. ref SDS 18 L24N
741286 - Jack recognized this danger in his letter on 000623 that
741287 - cautioned against permitting others to change original
741288 - work. ref SDS 41 5475, see also 010124 reviewing BrowseUp.
741289 - ref SDS 61 00FO
741290 - ..
741291 - Frustration about alleged, unspecified errors, and
741292 - one-sided interpretations in the record was reported by USACE
741293 - on 961017. ref SDS 16 5832 Yet USACE later found, after
741294 - gaining more experience, that SDS provided useful intelligence,
741295 - ref DRP 2 6172, which, in turn, saves time and money.
741296 - ref DRP 3 0001 Peirce, whose work Jack recommended on 000515,
741297 - points out that "knowledge" requires continual refinement to
741298 - work toward accuracy, which is never fully achieved.
741299 - ref SDS 38 7380 Therefore, feedback correcting the record is
741300 - critical to accomplish effective communication, as stated in
741301 - POIMS. ref OF 1 2200 NWO further explains importance of
741302 - feedback. ref OF 3 0936
741304 - ..
741305 - Jack was asked to review the section in POIMS that explains KM.
741306 - ref OF 1 1850 One part of this new material points out that
741307 - collaboration is an important derivative, or benefit, of adding
741308 - intelligence to information. ref OF 1 K84L This is another way
741309 - of saying SDS adds "metrics' to communication. NWO explains
741310 - that "communication" is not entirely realtime, in the moment,
741311 - activity. ref OF 3 2732 It has other aspects which are
741312 - helpful. SDS tries to address the aspects of understanding and
741313 - follow up, see NWO. ref OF 3 3279
741315 - ..
741316 - SDS is not designed for realtime discussion; other tools do
741317 - that well. Realtime communication is reactive, spontaneous, in
741318 - the moment, which is essential and useful for calls, meetings,
741319 - email, etc. (see above, ref SDS 0 5Y8I) SDS is deliberative
741320 - analysis that manages knowledge beyond the moment, enabling
741321 - people to be prepared for realtime communication, explained in
741322 - the record on 950327. ref SDS 9 TM5G On 960205 a study showed
741323 - people waste 70% of the day in realtime discussion because they
741324 - are not prepared. ref SDS 13 5902 SDS might help people be
741325 - prepared to save time and improve earnings.
741327 - ..
741328 - Both realtime and deliberative forms of communication advance
741329 - civilization, see POIMS. ref OF 1 5418
741331 - ..
741332 - Deliberation is not dynamic; it takes time, as explained in a
741333 - letter to the DKR team, ref DIP 5 E46H, on 000920. ref SDS 44
741334 - 2V5F People deliberate before, during and after realtime
741335 - communication, as an involuntary exercise of wondering,
741336 - pondering, worrying, thinking, analysing, musing. SDS helps
741337 - this part of cognition to discover mistakes and opportunities
741338 - that are missed in realtime communication, for the reasons
741339 - explained on 991108 reviewing differences between literacy and
741340 - orality. ref SDS 27 4505 Adding an "intelligence" effort helps
741341 - avoid the malady of false knowledge. ref OF 1 TJ6I
741342 - ..
741343 - For example, this SDS record has direct quotes from
741344 - Jack's letter, and links to original sources that maintain
741345 - alignment for accuracy. Describing SDS as "clippings" may
741346 - imply SDS presents information out of context, which is
741347 - incorrect since the full context is instantly available.
741348 - ref DRT 1 BK9J This improves conventional publications, which
741349 - merely identify a source. In SDS, the original source can be
741350 - opened at the exact location where a quote is cited. SDS
741351 - strengthens context by showing alignment with related sources,
741352 - objectives, history, requirements and commitments. This larger
741353 - context is missing from other methods.
741355 - "Information space" is not a useful description of SDS.
741357 - ..
741358 - Would like Jack's comments on "Knowledge Space," defined in
741359 - POIMS explaining SDS has more than "information." ref OF 1 034J
741360 - On 000503 Jack rejected Eric Armstrong's proposal for KM to
741361 - merely improve email; at that time he indicated support for
741362 - Knowledge Space. ref SDS 36 6138
Remember Every Little Thing Enables Rod to be a Mastermind Not SDS O
A50401 - ..
A50402 - Remembering Every Little Thing Supported by SDS Amazing
A50403 - Usefulness Requires Making Use of the Record, i.e., Action Items
A50404 - One-sided Musings Not Useful, Sometimes Incorrect - Need Feedback
A50407 - Jack says....
A50409 - Rod, I strongly believe that what you are doing is of enormous
A50410 - value. But, it serves collaboration only to the extent that you
A50411 - are able to behave as a mastermind, remembering every little thing
A50412 - anybody ever wrote that you came across. That's useful.
A50413 - Sometimes, your musings are not (at least to me) all that useful.
A50414 - Sometimes, for me, they are wrong. And, on those occasions, it may
A50415 - not be personal opinion, rather actual knowledge of facts that
A50416 - greatly differ from those you reflect and react to. ref DRT 1 KR4H
A50418 - ..
A50419 - On 001116 Jack reported to OHS/DKR team that SDS ability to remember
A50420 - every little thing enables creating "amazing" work product.
A50421 - ref SDS 52 SN4N
A50423 - ..
A50424 - Earlier on 890809 Ross worried about writing everything down was
A50425 - unnecessary overkill. ref SDS 91 3S6H
A50427 - [On 050115 Jack illustrates routine requirements for timely
A50428 - access to the record that improves accuracy of memory,
A50429 - rather than rely on assumption. ref SDS 92 EH6U
A50431 - ..
A50432 - [On 070729 Everything is Miscellaneous book explains hard
A50433 - work organizing the record causes people to store documents
A50434 - in stacks on desks, the floor, in cabinets, coffee table,
A50435 - anywhere handy, including the backseat of the car.
A50436 - ref SDS 98 IG9F
A50438 - ..
A50439 - [On 071220 Jack advises SDS subject indexing worthy of
A50440 - review for his work at SRI. ref SDS 99 M53N
A50442 - ..
A50443 - [On 071220 case study shows Jack Park identifies SDS unique
A50444 - support for Knowledge Management. ref SDS 99 ST6J
A50446 - ..
A50447 - [On 081219 doctor concerned that writing down every little
A50448 - thing prevents good health care focusing on important
A50449 - issues. ref SDS A1 589M
A50451 - ..
A50452 - Feedback refines accuracy and improves usefulness of knowledge,
A50453 - per Peirce reviewed on 000515. ref SDS 38 7380 Feedback
A50454 - identifies an error at a specific location in Knowledge Space,
A50455 - and sets out lack of alignment with a source at another
A50456 - location in Knowledge Space. Criticisms without specifics do
A50457 - not permit correction.
A50459 - ..
A50460 - USACE reported SDS provided useful "intelligence." A similar
A50461 - effort may not be useful or readily transferable; although,
A50462 - Doug Engelbart reported on 001027 that he found SDS is useful.
A50463 - ref SDS 49 XV6F SDS was useful to USACE is because action
A50464 - items guided conduct toward accomplishing objectives. On
A50465 - 000922 OHS/DKR was notified there are about 100 or so action
A50466 - items pending. ref SDS 45 0001 Jack and others can get greater
A50467 - use from SDS by performing action items. These action items
A50468 - are based on experience developing SDS, which has some of the
A50469 - features discussed for OHS/DKR. Failure to perform action
A50470 - items derived from experience doing the work contemplated by
A50471 - the project, reduces the value of SDS, as Jack reports today.
A50473 - "Musings" sounds like another word for "analysis," which is a
A50474 - task that correlates new information from correspondence,
A50475 - calls, meetings, reading, television, etc., and objectives,
A50476 - requirements, history, policy and commitments. Drucker, who is
A50477 - a recognized expert on management, says that "analysis" is an
A50478 - important responsibility of management. see review on 931130.
A50479 - ref SDS 6 7911
A50481 - "Intelligence" is another word for "musings." The CIA spends a
A50482 - lot of money to gather information and analyse correlations,
A50483 - implications and nuance in relation to objectives, principally
A50484 - national security. SDS helps do this work better. All of the
A50485 - "intelligence" prepared by the CIA is not accurate, but without
A50486 - the effort even greater errors occur due to the complexity of
A50487 - daily life.
A50489 - ..
A50490 - Anyone can get SDS to add more "masterminds," as Jack requests.
A50491 - ref DRT 1 KR4H
A50493 - ..
A50494 - Remembering "every little thing" is effective organizational
A50495 - memory that is a major objective for KM. Aligns with Jack's
A50496 - report on 001130 that SDS has the right structure for knowledge
A50497 - management and the interface that makes the structure of
A50498 - knowledge useful to people. ref SDS 56 H17O
A50500 - ..
A50501 - Everyone can be a "mastermind" using SDS to improve memory,
A50502 - rather than rely on limited span of attention, commonly called
A50503 - remembering only the "gist of things." Henry van Eykan found
A50504 - SDS improves memory, when he saw a demonstration on 001105.
A50505 - ref SDS 51 FB4I USACE made a similar finding reported on
A50506 - 990303. ref SDS 20 9499 On 950204 the fragility of human
A50507 - memory is strengthened by SDS fire power that expands span of
A50508 - attention. ref SDS 8 4995
A50510 - [On 010425 Morris feels using SDS to remember every little
A50511 - thing is "utopia." ref SDS 73 EP7F
A50513 - ..
A50514 - [On 010916 Eric Armstrong reported SDS has amazing memory
A50515 - using mechanisms that obviously work. ref SDS 79 0001
A50517 - ..
A50518 - [On 010916 Eric Armstrong discouraged that nobody can find
A50519 - anything using other methods. ref SDS 80 KA6H
A50521 - ..
A50522 - [On 050303 binary search in the Subject Index reduces time
A50523 - to find relevant words and phrases in the organic structure
A50524 - of context from 17 down to 1 second; synergy with precision
A50525 - access for dynamic linking makes makes finding critical
A50526 - details fast and easy for "connecting the dots" in time to
A50527 - be effective, because everythng is in the right place at
A50528 - the right time. ref SDS 93 C16D
A50530 - ..
A50531 - [On 070511 subject index tools improved to reduce time for
A50532 - finding everything organized in right place at right time,
A50533 - ref SDS 97 VL9N; list backgroung developing subject
A50534 - indexing. ref SDS 97 LP5J
A50536 - ..
A50537 - [On 080831 Jack Park provides example of SDS benefits for
A50538 - better personal and organizational memory; noting document
A50539 - re-submitted because could not remember submission several
A50540 - months earlier. ref SDS A0 H65G
Collaboration Goal Enterprise/Knowledge Management Does Not Improve P
Collaboratory - Link SDS with Ontology
Collaboration Customer Requirement NIH, Others, Pat Lincoln
Collaboratory with AI "Engine" Proposed to Improve SDS, Jack Park
Engine Map Topics for Subjects Ontology Graphical
Engine Process Record
SDS Records Muse Space be Turned Over to Collaboratory So Everyone Ca
Glass Bead Game Describes Com Manager Magister Ludi to Add Intelligen
Shared Information Escalates Risk Conflicting Action without Intellig
AZ1201 - ..
AZ1202 - Collaboratory Turns SDS Space Over to Online Issue-Based Discussion
AZ1205 - Jack proposes a collaboratory.....
AZ1207 - From my model of collaboration (which, IMHO, is a greatly different
AZ1208 - behavior than minding the events with SDS), what would be needed is
AZ1209 - that the muse space of SDS be turned over to a collaboratory, one
AZ1210 - in which the musings are output to an online issue-based discussion
AZ1211 - seeking a consensus interpretation of the events in question.
AZ1212 - ref DRT 1 PE5L
AZ1214 - ..
AZ1215 - "Collaboration" is applied here to change the way SDS is used
AZ1216 - from individuals creating and editing content separately, to,
AZ1217 - instead, permit multiple users access for realtime editing of
AZ1218 - SDS records on the Internet to reach a concensus interpretation
AZ1219 - of events where multiple people "collaborate" by changing
AZ1220 - someone else's original work. This is proposed to solve
AZ1221 - concern about SDS being a one-sided, biased interpretation,
AZ1222 - discusses above, ref SDS 0 633H and ref SDS 0 237O, and seems
AZ1223 - to align with Jack's ideas on 001130 for a 3-layer architecture
AZ1224 - with an "engine" to support a web-based Collaboratory,
AZ1225 - ref SDS 56 BQ3F, that includes users manipulating the archive
AZ1226 - (solely) by adding new commentary and participating in
AZ1227 - IBIS-based dialogs (DR). ref SDS 56 NX66
AZ1229 - [On 020310 Sparrow Web appears to provide the features Jack
AZ1230 - wants for collaboration. ref SDS 83 0001
AZ1232 - ..
AZ1233 - [On 020924 Jack clarifies these goals. ref SDS 90 H98H
AZ1235 - ..
AZ1236 - On 000623 Jack discussed a collaborative evolutionary
AZ1237 - epistomlogy, which has not been defined by tools, scenarios,
AZ1238 - time and skills. ref SDS 41 4752
AZ1240 - [On 010614 notice of collaborarium that sounds similar to
AZ1241 - Jack's proposal. ref SDS 75 LH3O
AZ1243 - ..
AZ1244 - On 940510 article in Harvard Business Review points out that
AZ1245 - people have difficulty sharing information, indicating that
AZ1246 - while people argue for sharing information in the abstract, the
AZ1247 - reality is that Jack's vision is not widely shared. ref SDS 7
AZ1248 - WH6M
AZ1250 - ..
AZ1251 - The same article sasy people have difficulty reaching concensus
AZ1252 - because the meaning of information various based on personal
AZ1253 - experience, which is different for everybody. ref SDS 7 3829
AZ1255 - ..
AZ1256 - SDS helps people add intelligence to information that creates
AZ1257 - knowledge of cause and effect. This is difficult, time
AZ1258 - consuming work that requires a lot more than everybody adding
AZ1259 - their "2 cents." If everyone edits the record, then no one is
AZ1260 - responsible, accountability is impossible.
AZ1262 - ..
AZ1263 - SDS records are available for use in a "collaboratory" for
AZ1264 - "processing" right now. When Jack gets this record he can
AZ1265 - process it, just as I "processed" his letter today using the 8
AZ1266 - steps shown on 001219, ref SDS 58 4W4L, by looking up history,
AZ1267 - assigning subjects, tying things together for alignment to
AZ1268 - check accuracy and discover correlations, nuance and
AZ1269 - implications that seem to strengthen understanding, which then
AZ1270 - leads to follow up actions, including questions
AZ1272 - ..
AZ1273 - Why can't SDS records be processed by other folks the same way?
AZ1274 - People can use SDS for this purpose, which is why it was
AZ1275 - created; or, they can create something else that does more
AZ1276 - processing, as Jack plans. In either case, the record is
AZ1277 - sitting out there to be processed, so long, ref SDS 0 HW9O, as
AZ1278 - the original work is not changed, for the reasons above.
AZ1280 - ..
AZ1281 - Assume a Collaboratory exists. How would it change daily work
AZ1282 - for digging a ditch, baking a cake, designing a Collaboratory,
AZ1283 - reading a book, fixing the car, writing a letter, flying to
AZ1284 - mars? How would people do these common tasks differently?
AZ1286 - ..
AZ1287 - Try it another way.....
AZ1289 - ..
AZ1290 - POIMS explains the basic difference SDS brings to daily work.
AZ1292 - ..
AZ1293 - The SDS typical day scenario tries to explain how SDS changes
AZ1294 - daily work. ref OF 2 0001 What additional or different changes
AZ1295 - does a Collaboratory portend?
AI Cannot Think No Biological Drives Cannot Map Human Experience
SDS Different Design from AI KM
Computers Help Aspects of Cognition
AI Black Box Engine Mechanized Knowledge False Dangerous Idea 2 Group
AI Web Software Engineers Moved to KM with TQM Project Management Ora
AI Moved to KM Use Software Build Web Pages for Collaboration Ontolog
Truth Moving Target on Information Highway, Needs SDS
Linking Alignment Traceability Original Sources Attribution
BC1101 - ..
BC1102 - SDS Supports Computer Aided Thinking That May Lead to AI
BC1103 - Truth is a Moving Target Maintained by Alignment, Feedback
BC1104 - AI Engine Proposed to Process Information to Create Knowledge
BC1107 - Jack says....
BC1109 - As I have said before, such a collaboratory will need the
BC1110 - capability of maintaining a kind of truth maintenance system, one
BC1111 - that is capable of spotting such faux pas as self-contradictions,
BC1112 - referents not *on the same page* and so forth. Such a system
BC1113 - would, ultimately, probably need the ability to go outside the
BC1114 - present universe of discourse and bring in other evidence by
BC1115 - itself. The system should probably also be capable of weighing the
BC1116 - information content of various statements, judging whether they
BC1117 - represent an addition to the conversation, or just noise. POIMS,
BC1118 - as it appears to be implemented in SDS, does not give evidence that
BC1119 - it is capable of doing any of these things. ref DRT 1 LI6H
BC1121 - ..
BC1122 - This sounds like the "engine" discussed on 000623, and later on
BC1123 - 001130. ref SDS 56 0001 More recently on 010223 Jack proposed
BC1124 - an "engine." ref SDS 64 3RKS The submission on 010405 proposes
BC1125 - a "groves" engine that is not defined. ref SDS 69 485N Eugene
BC1126 - Kim explains Groves with references. ref SDS 69 NV9H These
BC1127 - methods may support SDS organic subject structure. Experience
BC1128 - using SDS may increase progress on these efforts.
BC1130 - ..
BC1131 - Questions on Jack's ideas for an "engine" are pending action
BC1132 - items in the prior records, and so are not repeated.
BC1134 - ..
BC1135 - Jack could help a lot by submitting work product illustrating
BC1136 - application for these proposals that shows capabilities exist,
BC1137 - or would be useful, if they could be produced. This would offer
BC1138 - reasonable grounds to rebut the contrary conclusion set out in
BC1139 - POIMS. ref OF 1 084J
BC1141 - ..
BC1142 - SDS maintains "truth," by automatically linking records to
BC1143 - build chronologies of cause and effect, that further show
BC1144 - alignment with original sources, under ISO criteria reviewed on
BC1145 - 950721. ref SDS 10 1740 Since the complexity of the modern work
BC1146 - environment escalates meaning drift that makes "truth" a moving
BC1147 - target, reviewed on 960518, ref SDS 15 4488, SDS automated
BC1148 - linking saves a lot of time and money. This is not "automated"
BC1149 - in the sense of throwing a switch, and an "engine" determines
BC1150 - to link record "a" to record b, c, f, k, etc, because the
BC1151 - magnitude of complexity is too great for such an effort, as
BC1152 - explained in POIMS. ref OF 1 8774 The present design may be a
BC1153 - step in that direction, and it saves enormous time and money,
BC1154 - with ROI of 10:1, reported by USACE. ref DRP 3 0001 USACE,
BC1155 - also, reported separately that SDS provides useful intelligence
BC1156 - that solves problems and reveals opportunity. ref DRP 2 6172
BC1158 - ..
BC1159 - SDS strives to augment human thinking, not replace nor perform
BC1160 - "thinking." Once we learn to augment, then we can turn to the
BC1161 - larger task of actual "thinking," which requires formulating an
BC1162 - architecture of human thinking that can be effectively
BC1163 - supported by technology. POIMS strives to start this this
BC1164 - effort. ref OF 1 0561
IBIS Rigid Ineffective, 000218
BL0401 - ..
BL0402 - IBIS Has No Record of Converting Information into Useful Knowledge
BL0405 - Jack concludes....
BL0407 - How might, say, a re-implementation of the present SDS move in this
BL0408 - direction? My hunch is that SDS should be re implemented to behave
BL0409 - just as it presently does, but with the addition that it can submit
BL0410 - its musings to an IBIS discussion list and acquire responses for
BL0411 - further musing, which, of course, would be presented to the
BL0412 - discussion. Simply make SDS a node in a discussion system and
BL0413 - you're awfully close to collaboration as I presently see it. The
BL0414 - human should stay precisely in the loop you presently implement,
BL0415 - but that loop needs to be tweaked. ref DRT 1 WP3I
BL0417 - ..
BL0418 - Jack might submit an example of an IBIS discussion to
BL0419 - illustrate this is a useful exercise, as requested on 001130.
BL0420 - ref SDS 56 AZ7J
BL0422 - ..
BL0423 - Several folks have reported SDS saves time and money....
BL0425 - PG&E......... ref DRP 1 8444
BL0426 - USACE........ ref DRP 3 0001
BL0428 - ..
BL0429 - What evidence shows IBIS can improve this record?
BL0431 - ..
BL0432 - The SDS record can be incorporated into other discussions at
BL0433 - any time, including IBIS.
BL0435 - ..
BL0436 - Therefore, not sure there is a big problem here.
BL0437 - ..
BL0438 - Why does SDS have to be a node?
BL0440 - ..
BL0441 - There is no node for a chair, light bulb, microprocessor or
BL0442 - other tool needed for KM.
BL0444 - ..
BL0445 - Why not get SDS and start saving time and money doing KM,
BL0446 - instead of IT? If IBIS turns out to be helpful, so much the
BL0447 - better.
BL0449 - ..
BL0450 - The challenge is transitioning from consuming information to a
BL0451 - culture of knowledge that invests intellectual capital.
Distribution. . . . See "CONTACTS"