CONTACTS 
0201 - Chips & Technologies
020101 - Mr. Morris E. Jones
020102 - Sr. Vice President

SUBJECTS
SDS Windows Design
Measuring Communication Issues

0604 -
0604 -    ..
0605 - Summary/Objective
0606 -
060601 - Follow up ref SDS 26 0000.
060602 -
060603 - Considered using Jim DeHart to provide SDS support for Morris, and
060604 - then develop the SDS Windows code.
060606 -  ..
060607 - Considered further Morris interest in TQM, and how SDS and
060608 - communication metrics can be marketed.
060609 -
060611 -  ..
0607 -
0608 -
0609 - Discussion
0610 -
061001 - Presented idea of bringing Bill's son, Jim DeHart, on board to work
061002 - under Morris in creating the SDS Windows code.  Morris said he sent
061003 - Jim's resume to someone in the company, and expects that Chips may
061004 - have tried to call Jim, but did not reach him because of his
061005 - relocation to his parents home in Antiock.
061007 -  ..
061008 - The idea would be for Jim to provide TQM support for Morris by
061009 - providing "communication engineering" using SDS.  This would enable
061010 - Jim to learn how SDS works, so he would know what to program.  Morris
061011 - seems to recognize the importance of this idea.  That is why I have
061012 - been trying to get him to use SDS for the past 10 years.
061014 -  ..
061015 - We agree it is critical to build the marketing ideas (discussed below)
061016 - along with a Windows implementation.
061017 -
061018 -     [On 950414 work on advertising supports this idea. ref SDS 32 914L
061019 -
061021 -  ..
061022 - I suggested he contact the person to whom he submitted the resume, and
061023 - see what needs to be done to move the matter forward.  This would fit
061024 - with Morris' notice today, that Chips is working a lot of overtime
061025 - these days, and so actually need help.  He said though that they have
061026 - received a lot of resumes from engineers due to recent layoffs by
061027 - other employers in the Valley.
061028 -    ..
061029 -    Morris indicated that if Jim were hired, he may not have time
061030 -    to work on SDS.  I explained that when an organization becomes
061031 -    "busier" that is the time they most need to be using SDS in order
061032 -    to avoid the ravages of Murphy's Law.  Every one is excited, and
061033 -    working hard.  They are expediting, and taking a few short cuts to
061034 -    get things done.  Little mistakes are creeping into the ether. More
061035 -    management is needed to dig these out and prevent them from
061036 -    becoming big disasters in 6 months or 2 years.
061038 -     ..
061039 -    Thus, the better investment is in a little better management.
061040 -
061042 -  ..
061043 - Morris showed me a requirements spec he prepared for the marketing
061044 - people, and a review he did of the engineering specs, to evaluate the
061045 - correlation between expectations and designed capabilities.
061047 -  ..
061048 - This is a good application for SDS.
061050 -  ..
061051 - Morris feels that Chips has a good data base for this information that
061052 - is better and easier to create than using SDS.
061053 -
061054 -    Since the afternoon was going well, and since it was late for my
061055 -    meeting at ASPE, I did not ask how Chips' data base correleated
061056 -    engineering progress, with correspondence, analysis, telephone
061057 -    calls, meetings, etc, in light of the report on 950428 that this
061058 -    work is not getting done. ref SDS 33 3921  We did not review
061059 -    Morris' report on 911121 that Chips' used an AI program that was
061060 -    better than SDS for engineering management, but it turned out that
061061 -    it was not very useful. ref SDS 4 5609
061062 -
061063 -        [On 990524 Morris maintained that Intel has better engineering
061064 -        management programs than SDS, but the engineers don't have
061065 -        enough time to use them. ref SDS 53 6892
061067 -         ..
061068 -        [On 010614 Morris feels Intel uses Check Out and Check In to
061069 -        manage work to prepare a contract a contract that works better
061070 -        than SDS. ref SDS 58 RW5F
061072 -  ..
061073 - Actually, it would be a good idea for me work with him a bit to see
061074 - what kind of relationships are best for SDS to track, and what if any
061075 - is helpful in the system he is now using.  He said they can "link"
061076 - stuff.  What does this mean?
061077 -
061078 -
061079 -
061080 -
061081 -
061082 -
0611 -

SUBJECTS
Personnel Training, Management Skills, TQM
SDS Marketing, Product Definition, POIMS, Communication Metrics
Surveys, Meetings, Meeting Notes, confirm understandings
Metrics (analysis, aligning, testing)

2906 -
290701 -  ..
290702 - Whats a Metric - Accuracy Critical Factor Measured by Links
290703 -
290704 - Follow up ref SDS 26 5868, ref SDS 19 5468.
290705 -
290706 - Morris seems a bit more open today about the idea of "Communication
290707 - Metrics."  He has become familiar with TQM.
290709 -  ..
290710 - Morris suggests developing intermediate metrics that provide
290711 - quantitative diagonstics for communication which customers can perform
290712 - or a sales agent can provide, following up discussion on 950223.
290713 - ref SDS 26 5567
290714 -
290715 -     We have already done a form of this with the questionaire
290716 -     developed on 930712. ref SDS 8 4829.  Quantitive diagnostics could
290717 -     be a helpful means to open people's eyes, as well as a good sales
290718 -     medium to maintain customer contact.  Effectiveness for improving
290719 -     the work to save time and money is less clear.
290720 -
290721 -         [On 950401 reviewed ideas for developing numerical reporting
290722 -         for communication. ref SDS 31 5839
290724 -          ..
290725 -         [Created utility to capture more communication diagnostics on
290726 -         970803, ref SDS 51 line 60.]
290728 -          ..
290729 -         [On 971001 applied communication diagnostics to calculate cost
290730 -         savings using SDS for Com Metrics. ref SDS 52 R48U
290732 -      ..
290733 -     Today, Morris came up with what seemed like a good list of issues
290734 -     that can be quantitfied.
290735 -
290736 -         [Followed up at ref SDS 29 line 63.]
290738 -      ..
290739 -     I did not press the point that Communication Metrics discovers
290740 -     things that need to be done which do not arise in a meeting, but
290741 -     are discovered by writing up the record, as shown by Morris'
290742 -     example reported on 950204. ref SDS 19 8A9F  Further discover to
290743 -     refine accuracy of understanding and expand discover occurs by
290744 -     using SDS to place new information in the context of relevant
290745 -     history, objectives, requirements and commitments that emerge from
290746 -     adding organization, alignment, summary and feedback, i.e.,
290747 -     intelligence expands span of attention.  Whether this results in
290748 -     fewer or more meetings is irrelevant to saving money, as Morris
290749 -     reported on 910520. ref SDS 3 HV66  Below, Morris cited the need
290750 -     for this support at Chips. ref SDS 0 1994  Having made
290751 -     discoveries, this needs to be distributed in an effective manner
290752 -     to build and maintain shared meaning, so that action can be taken
290753 -     in time to avoid mistakes and sieze opportunity.  This needs to be
290754 -     accomplished in a way that does not point fingers or cast
290755 -     aspersions on individuals, but rather enables everyone to
290756 -     continually learn and apply experience as organizational memory,
290757 -     and history.
290758 -
290759 -
290761 -  ..
290762 - Quantifying Communications
290763 -
290764 - We need a form that sets out some commonly understood derivitives of
290765 - "communications" like "action items" which can be quantified.  He
290766 - listed a few ideas which at this time do not come to mind.
290767 -
290768 -    [Followed this up at ref SDS 30 0000 314 and on Landauer's book on
290769 -    the "Trouble with Computers," ref SDS 36 line 153.]
290771 -     ..
290772 -    [Created utility to capture more communication diagnostics on
290773 -    970803, ref SDS 51 line 60.]
290775 -     ..
290776 -    [On 971001 calculated cost savings based on SDS communication
290777 -    diagnostics. ref SDS 52 R49R
290779 -  ..
290780 - Diagnostics Morris has in mind seem to require collaboration with
290781 - people in order to dig out meaningful scenarios.  I could have
290782 - presented this to PG&E but until we have an actual example, they would
290783 - have no idea how SDS solves the problem, and many would be in denial
290784 - of the problem.
290785 -
290786 -         "Oh no, it does not occur with us, and if it does, no one can
290787 -         do a better job than we are already doing to avoid such
290788 -         problems."
290789 -
290790 -         "We are using Windows, TQM, reengineering and everything, so
290791 -         nothing more can be done."
290792 -
290793 -
290794 -
290795 -
290796 -
290797 -
2908 -

SUBJECTS
Customer Perceived Value, Thinking Through Writing
Maintain Shared Meaning, Metrics
What Did We Say, Hear, See, What Does It
Organizational Memory Intelligence Organization Analysis Alignment Su
History Who What When Where Why How Capturing Organizational Memory H
Everybody's Talking, Nobody's Listening, No Time to Undrestand
Meetings Unproductive Misunderstanding Failed Communication Causes Re
Design SDS Breakthrough Hierarchial Relational Architecture
Meetings Waste Time Example Upproductive Nobody Prepared
Jones, Morris Frustrated Meetings Waste Endless Hours Arguing About W
Frustrated Meetings Waste Endless Hours Arguing About Who Said What a
Jones, Morris Frustrated Meetings Unproductive People Need Command Co

7114 -
711501 -  ..
711502 - Meetings Reduce Productivity - Who, What, When, Where, Why...
711503 -
711504 - Morris feels a big need for SDS is improving meetings, which aligns
711505 - with Eric Jenett's article in PMJ reviewed on 940114. ref SDS 9 2290
711507 -  ..
711508 - Morris was frustrated about the way meetings are conducted, wasting
711509 - time going over and over arguing about prior understandings, who said
711510 - what, when, where, why -- the revised fax that modified the email that
711511 - clarified the phone message, etc., etc.
711513 -  ..
711514 - Earlier on 921127 Morris was frustrated by overlooking inconsequential
711515 - details that later explode into major problems. ref SDS 7 0674
711516 -
711517 -        [On 950303 Morris gave an example of a meeting in Paris which
711518 -        Chips people attended, and later a legal dispute arose about
711519 -        what was discussed and agreed; he feels this is an application
711520 -        for SDS, because nobody can remember what happened. ref SDS 30
711521 -        3333
711523 -         ..
711524 -        [On 960205 study published showing people waste 70% of day in
711525 -        unproductive meetings because nobody has invested time to be
711526 -        prepared by reading the record, ref SDS 38 5902; then everybody
711527 -        argues about what was said at the last meeting. ref SDS 38 5F4S
711529 -         ..
711530 -        [On 960326 meeting with Morris shows people resist reading the
711531 -        record to prepare for conducting an effective meeting,
711532 -        ref SDS 39 LO5G; then argue about what happened at the last
711533 -        meeting. ref SDS 39 7390
711535 -         ..
711536 -        [On 960721 people angry at meetings between Chips, Intel,
711537 -        Lockheed/Martin because everybody remembering what happened at
711538 -        the last meeting differently. ref SDS 42 0896
711540 -         ..
711541 -        [On 970123 Intel uses confrontation to resolve differences in
711542 -        memory of prior meetings, rather than capture record of
711543 -        organizational memory. ref SDS 48 1111
711545 -         ..
711546 -        [On 970707 USAFIT entropic model posits that management large
711547 -        projects degrades toward failure, ref SDS 50 628M, because
711548 -        everybody is talking and nobody is listening. ref SDS 50 0108
711550 -         ..
711551 -        [On 990527 Andy Grove reported that engineers resist reading.
711552 -        ref SDS 54 5110
711554 -  ..
711555 - We reviewed Morris feeling on 950204 that SDS is unnecessary overkill,
711556 - ref SDS 19 5932, which reflects his experience last year on 940327
711557 - when people got mad because he submitted his notes to refresh
711558 - conflicting memories. ref SDS 11 J47F
711560 -  ..
711561 - He feels today that normally SDS is not needed but sometimes it can be
711562 - useful to avoid constantly plowing the same ground, because continual
711563 - "rework" in meeting after meeting brings productivity to a standstill,
711564 - i.e., to 0.
711565 -
711566 -        [On 960406 Morris reported finding information on a computer is
711567 -        very difficult without SDS. ref SDS 40 4249
711569 -         ..
711570 -        [On 011003 Eric Armstrong reported that productivity is
711571 -        paralyzed because nobody can remember how to
711572 -        find anything.
711574 -  ..
711575 - Morris noted today everyone remembers things differently, everyone's
711576 - talking, nobody listens, and no one has notes anyone can decipher,
711577 - including the person who wrote them, aligns with NWO... ref OF 2 3118
711578 - On 890809 Morris felt that creating organizational memory in a legible
711579 - record takes too much time. ref SDS 2 5930  Today, he seems to be
711580 - clarifying that better memory supported by SDS might be helpful to
711581 - improve productivity of meetings.
711582 -
711583 -        [On 950303 Morris gave an example of a meeting in Paris which
711584 -        Chips people attended, and later a legal dispute arose about
711585 -        what was discussed and agreed; he feels this is an application
711586 -        for SDS, because nobody can remember what happened. ref SDS 30
711587 -        3333
711589 -         ..
711590 -        [On 990721 Morris suggested explaining SDS as a "memory" aid.
711591 -        ref SDS 55 0001
711593 -         ..
711594 -        [On 960326 people resist reading the record to prepare for
711595 -        conducting an effective meeting; then argue about what happened
711596 -        at the last meeting. ref SDS 39 LO5G
711598 -         ..
711599 -        [On 020217 people point fingers in accusation and blame when
711600 -        they cannot point to contextually relevant record of daily work
711601 -        from meetings, calls, and documents; solved by SDS support for
711602 -        Communication Metrics. ref SDS 60 9360
711604 -  ..
711605 - On 890809 Morris said listening is a big problem, helping people to
711606 - understand and follow up.  Chips sends people to seminars to learn
711607 - better listening. ref SDS 2 CJ9J
711609 -  ..
711610 - On 940114 there was an example of poor management productivity in
711611 - meetings at Chips and Technologies. ref SDS 10 O15M
711612 -
711613 -        [On 950303 people cannot remember what happened during a
711614 -        meeting in Paris, France. ref SDS 30 3333
711615 -
711616 -        [On 970110 similar problem at USACE. ref SDS 46 2487
711618 -  ..
711619 - On 911123 Morris cited "feel good" management as a common practice of
711620 - executives who don't like SDS methods. ref SDS 5 4930  On 920215
711621 - meetings were the only source for organizational memory to guide
711622 - downsizing decisions; there wasn't enough time for using SDS.
711623 - ref SDS 6 HJ8G
711625 -  ..
711626 - The only solution is to use Communication Metrics for internal
711627 - management, as discussed on 890809. ref SDS 2 8492  A good example
711628 - from the PG&E experience occurred on 941211 showing SDS avoids this
711629 - problem by investing intellectual capital. ref SDS 16 6488
711630 -
711631 -     [On 950303 Morris developed advertising concept to illustrate SDS
711632 -     keeps daily work aligned with objectives, using a bow and arrow,
711633 -     and target image. ref SDS 30 3497
711635 -      ..
711636 -     [On 950303 Morris gave example where SDS improves productivity on
711637 -     remembering critical details about meetings. ref SDS 30 3333
711639 -      ..
711640 -     [On 950605 Anne Bevington mentioned same problem. ref SDS 34 1842
711642 -      ..
711643 -     [On 951101 hiring a psychologist to avoid conflict because people
711644 -     remember differently. ref SDS 37 5500
711646 -      ..
711647 -     [On 960205 managers waste 70% of day in meetings. ref SDS 38 5222
711649 -      ..
711650 -     [On 960326 example wasting time arguing about Asilomar.
711651 -     ref SDS 39 8442
711653 -      ..
711654 -     [On 960510 meetings with Intel and Lockheed/Martin unproductive.
711655 -     ref SDS 41 2943
711657 -      ..
711658 -     [On 960721 poor productivity of meetings at Intel and Lockheed.
711659 -     ref SDS 42 0896
711661 -      ..
711662 -     [On 960924 USACE pilot tests Com Metrics to improve organizational
711663 -     memory, improve meetings, management. ref SDS 43 4454
711665 -      ..
711666 -     [On 961023 managers cannot read their notes. ref SDS 44 2079
711668 -      ..
711669 -     [On 961218 managing by guess and gossip ref SDS 45 5790, and again
711670 -     on 970110, no one can "remember." ref SDS 46 5893
711672 -      ..
711673 -     [On 970116 communication fails because of "fractionalized"
711674 -     subjects. ref SDS 47 1732
711676 -      ..
711677 -     [On 970123 "constructive confrontation" makes meetings productive.
711678 -     ref SDS 48 1111
711680 -      ..
711681 -     [On 970418 USACE reports SDS enables Com Metrics that helps add
711682 -     "intelligence" to meetings for improving productivity. ref SDS 49
711683 -     5368
711685 -      ..
711686 -     [On 971001 calculation of cost savings by reducing "rework."
711687 -     ref SDS 52 4472
711689 -      ..
711690 -     [On 001207 productivity, earnings, stock prices declining because
711691 -     too many people have too many problems. ref SDS 56 V54M
711693 -      ..
711694 -     [On 010425 Morris feels Typical Day Scenario illustrates "utopia'
711695 -     using SDS compared to other methods. ref SDS 57 EP7F
711697 -      ..
711698 -     [On 020208 manager software development group of 100 engineers
711699 -     reports productivity of meetings poor because of weak and
711700 -     conflicting organizational memory. ref SDS 59 J66L
711702 -      ..
711703 -     [On 020415 manager software development group calculates $40K per
711704 -     day loss that can be recovered using SDS for Com Metrics.
711705 -     ref SDS 61 C28K
711706 -
711707 -
711708 -
711709 -
711710 -
711711 -
711712 -
711713 -
711714 -
711715 -
711716 -
711717 -
711718 -
7118 -