THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: June 14, 2002 07:34 AM Friday; Rod Welch

Mark at Microsoft received communicaton on SDS memory problem.

1...Summary/Objective


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

CONTACTS 
0201 - Microsoft Corporation                                                                                                                                              O-00000364 0507
020101 - Ms. Brenda Cannon; Windows Enterprise Support
020103 - Windows 2000 Support
020104 - Applications and Performance                                                                                                                                     O-00000364 0507
0202 - Microsoft Corporation                                                                                                                                              O-00000364 0506
020201 - Mr. Mark Mueller; Manager
020203 - Windows 2000 Support
020204 - Applications and Performance                                                                                                                                     O-00000364 0506

SUBJECTS
SRX020519601479 Microsoft Called and Got Incident Number to  nvestiga
DOS Memory Get 750K Instead of 634K
DOS Memory Program for More than 640K
Memory Above 640K Submit SDS Program for Review by Brandon
640K Memory Limit for DOS Need Solution
Submitted E Exe to Brandon at Microsoft
Letter to Brandon Asking About Progress on Investigating Increasing R
Jones, Morris Submit Questions to Brends Cannon at Microsoft on Using
Cannon, Brenda Inquiring About Specific Questions Submitted by Morris
Support Team Getting Communication Out of Sequence Causes Teamwork to
Communication Out of Sequence Causes Teamwork to Fail
SDS Memory Increase above 640K Ask Gary to Comment on Whether there a
Email Out of Sequence Delivery Causes Communiation and Teamwork to Fa
Team Getting Communication Out of Sequence Causes Teamwork to Fail Wo
Email Killer App Causes Mistakes Kills Productivity Needs SDS for Int

2917 -
2917 -    ..
2918 - Summary/Objective
2919 -
291901 - Follow up ref SDS 34 0000, ref SDS 33 0000.
291902 -
291903 -                       SRX020519601479
291904 -
291906 -  ..
291907 - Received an email from Mark this morning that is dated 020612, two
291908 - days ago.  This is a two (2) day lag in delivery of mail.  Mark simply
291909 - acknowledged receipt of a letter to him the same day, on 020612 that
291910 - re-submitted a letter sent the day before, which Mark had not received
291911 - when we talked by phone on 020612. ref SDS 33 QG4O
291913 -  ..
291914 - Last night on 020613 Brandon at Microsoft reported he had not received
291915 - a letter sent to him on 020612 that provided contact information for
291916 - Morris. ref SDS 34 W26K
291918 -  ..
291919 - This record of mail being delivered out of sequence has devestating
291920 - impacts on communciation and productivity.  The sender feels
291921 - coordination is occurring that not only is not taking place, but when
291922 - team members working together on tasks, as with Brenda and Brandon,
291923 - get information out of sequence, it falsely conveys an impression that
291924 - they are "out of the loop," as indicated by Brandon's letter.
291925 - ref SDS 34 RE6K
291926 -
291927 -      [On 020718 talked to Brenda about solving this problem by solving
291928 -      DOS memory problem. ref SDS 35 SZ9F
291930 -  ..
291931 - Submitted ref DIT 1 0001 to Mark saying....
291932 -
291933 -   1.  Thanks for your notice on Wednesday, June 12, 2002, of having
291934 -       received re-submission of a letter to Brandon on Tuesday, June
291935 -       11.  Since I received your notice just this morning on June 14,
291936 -       2 days after it was sent, this confirms a variable lag in
291937 -       delivery of mail that complicates communication. You noted in
291938 -       our call on June 12 that communication is a big challenge.
291939 -       ref SDS 33 QG4O
291940 -       ..
291941 -   2.  Part of the problem is variable delivery of the mail, when
291942 -       several people are contributing, and they receive mail at
291943 -       different times.  Not a big deal when the variance is a few
291944 -       minutes, but hours and in this case days, cause a big impact on
291945 -       teamwork. ref DIT 1 E56N
291947 -        ..
291948 -   3.  Last night for example, Brandon was concerned because he did not
291949 -       receive requested information, ref DIT 1 S57K, and this conveyed
291950 -       an incorrect impression that certain initiatives he was pursuing
291951 -       on this case were not being followed by the rest of us.
291952 -       ref SDS 34 W26K
291954 -        ..
291955 -   4.  Turned out the information was timely submitted to Brandon, but,
291956 -       as with you on 020612, and now again today with me, per above,
291957 -       there was a lag in delivery on some mail, while other mail is
291958 -       being delivered promptly, with the result that the flow of
291959 -       communication is being received out of sequence.  Since sequence
291960 -       is a critical part of human reasoning (see POIMS), ref OF 1
291961 -       0367, this significantly compounds the challenge of
291962 -       communication that you mentioned occurs at Microsoft, and of
291963 -       course everywhere else. ref DIT 1 SP8R
291965 -        ..
291966 -   5.  Drucker says people have just given up on communication,
291967 -       ref DIT 1 RS9I, because the range of problems is overwhelming.
291968 -       ref SDS 5 3851
291969 -       ..
291970 -   6.  Being aware of the problem, and reacting, as Brandon did
291971 -       last night, ref SDS 34 RE6K, to inquire about things that seem
291972 -       out of step with plans, helps get things done by taking
291973 -       complementary, ref DIT 1 1U9O, rather than conflicting, action
291974 -       that can help see us through, until the mail gets back to timely
291975 -       delivery.
291977 -        ..
291978 -   7.  Just want to thank everyone for sticking with this thorny issue
291979 -       despite it seeming at times like the gods are against us.
291980 -       ref DIT 1 PPWW
291981 -
291982 -
291984 -  ..
2920 -
2921 -
2922 - 1340
2923 -
292301 - Called Brenda.
292302 -
292303 - She has received the letter from Morris, ref DRP 6 0001, with
292304 - questions he has on improving memory for SDS, and Brenda received the
292305 - letter I sent this morning to Mark. ref DIT 1 0001
292307 -  ..
292308 - She is working on Morris' questions, and understands she can
292309 - coordinate dirctly with Morris to get clarifications and explore
292310 - ideas, per analysis of Brandon's letter in the record last night.
292311 - ref SDS 34 LR8U
292312 - ..
292313 - Brenda advised that she has sent an acknowledgement letter to me
292314 - on this matter about 20 minutes ago.
292316 -  ..
292317 - She is pursuing the ideas she has, and will file a report with
292318 - Brandon.
292319 -
292321 -  ..
2924 -
2925 -
2926 - 1351
2927 -
292701 - Received ref DRT 1 0001 from Brenda saying...
292702 -
292703 -     I received the email from Morris, ref DRP 6 0001, [submitted on
292704 -     June 13, 2002]. ref SDS 34 QU4O
292706 -      ..
292707 -     I will relay any information I found to Brandon.
292709 -  ..
292710 - This aligns with planning last night on 020613. ref SDS 34 FH9M
292711 -
292712 -
292713 -
292714 -
292715 -
292716 -
292717 -
292718 -
292719 -
292720 -
292721 -
292722 -
2928 -
Distribution. . . . See "CONTACTS"