CONTACTS 
0201 - Chips & Tech.                                                                                                                                                      O-00000039 0201
020101 - Mr. Morris E. Jones
020102 - Vice President
020103 - Advanced Products

SUBJECTS
Subjects, Action Items
Information Management, Meetings
Communications & Communication Metrics
Information Organization & Maintenance
Writing & Subject Indexing, 910418, 930118
Action Items, Controlled Visibility
Correlation to accepted practice and
Organize Complexity of Life/Management
Knowledge Management Dilemma Balance Summary and Details
Details Hidden by Summary, But Hide Perspective
Action Items in Subject Report, 06112

3413 -
3413 -    ..
3414 - Summary/Objective
3415 -
341501 - Follow up ref SDS 18 0000, ref SDS 10 0000.
341502 -
341503 - Used work for PMI Subject Index performed today, to extend development
341504 - of Action Item management, integrated with Subject Index, initially
341505 - created for the PG&E assignment on 940830. ref SDS 10  Used ideas from
341506 - discussion with Jeff at Seawest Company on 950621. ref SDS 17 8449.
341508 -  ..
341509 - This record considers ways to automate aspects of Action Items using
341510 - the Subject Index and SDS subject reporting, which is a complex craft,
341511 - per report in Byte at ref SDS 4 5584. Today, the work is to improve
341512 - the procedures used on the PG&E project on 940830. ref SDS 10 7864
341514 -  ..
341515 - Developed concepts and design considerations; began implementation in
341516 - another record today. ref SDS 18 0001
341517 -
341518 -     [On 950627 see "evaluation" for overview at ref SDS 19 9750.]
341519 -
341520 -     [On 950703 turned out we needed two new menu functions to apply
341521 -     the citation feature, ref SDS 22]
341523 -      ..
341524 -     [On 951126 used Special Control Field to manage Action Items in a
341525 -     record segment. ref SDS 28 0001
341527 -      ..
341528 -     [On 951209 system was improved and expanded. ref SDS 29 0001
341529 -
341531 -  ..
3416 -
3417 -
3418 - Progress
3419 -
341901 - Goals to Improve Management of Action Items
341902 -
341903 - Worked today on SDS record for PMI meeting on 950612, ref SDS 16 0001,
341904 - to apply ideas on 940830 from PG&E contract where each meeting was
341905 - segmented by agenda items. ref SDS 10 7864   The work today considers
341906 - how to set up a SI for PMI that applies the experience from PG&E on
341907 - the CDWR and Gold Hills projects, particularly with respect to "Action
341908 - Items" that expand span of attention for getting things done
341909 - correctly, on time and within budget.
341911 -      ..
341912 -     Action Item Definition
341913 -
341914 -     An "Action Item" mainly tracks understandings and/or commitments
341915 -     for specific individuals to take action needed to accomplish a
341916 -     larger body of work identified by a Control System, such as a CPM
341917 -     activity, the SDS Subject Index, list of goals and/or objectives,
341918 -     a meeting agenda item, etc. (see also "Requirements" below,
341919 -     ref SDS 0 6301)
341921 -      ..
341922 -     See example of Action Item system reported on 941012.
341923 -     ref SDS 11 4881.
341924 -
341926 -  ..
341927 - Knowledge Management Dilemma Balance Summary and Details
341928 -
341929 - There are two competing considerations re the Subject Index:
341930 -
341931 -  •  Managing and using organic subject structure needs to be fast and
341932 -     easy to use in order to enhance the chance that it will be applied
341933 -     regularly.  If people don't use it, no benefit can be realized.
341934 -     This goal is frustrated by a complicated structure that takes time
341935 -     to understand and apply.
341937 -      ..
341938 -  •  The world is complex, and the practice of management is becoming
341939 -     more so due to the Information Highway of more meetings, calls,
341940 -     documents and regulations, as noted by Peter Drucker, reviewed on
341941 -     931130. ref SDS 8 1855  On 890523 the challenge of organizing an
341942 -     effective record with organic structure was reviewed. ref SDS 1
341943 -     SQ5L The SDS solution is to strike a simple balance between
341944 -     summary and detail that is fast and easy to implement.
341946 -  ..
341947 - Balancing summary and detail is a knowledge management dilemma, set
341948 - out in POIMS. ref OF 1 8774
341949 -
341950 -         [On 960322 subject index also helps balance summary for
341951 -         perspective on the "big picture," with command and control of
341952 -         details in the microcosm for getting things done. ref SDS 30
341953 -         7749
341955 -  ..
341956 - Success requires "understanding" complex relationships, i.e., context;
341957 - so, we don't want details to overwhelm the conscious span of
341958 - attention, which requires perspective, and we, also, don't want
341959 - summary (i.e., perspective) to hide or mask the need for careful
341960 - analysis by over simplifying reality, see also below under "Controlled
341961 - Visibility." see, ref SDS 0 1337
341962 -
341963 -        [On 970116 discussed with Morris. ref SDS 34 1732.]
341965 -         ..
341966 -        [On 000524 Paul Fernhout developed information storage
341967 -        architecture that is fast and flexible in storing records.
341968 -        ref SDS 35 1972
341970 -  ..
341971 - The Subject Index can meet these objectives by managing complexity
341972 - through an...
341973 -
341974 -                          organic structure
341975 -
341976 - ...based on hierarchical and relational methods, similar to Work
341977 - Breakdown Structure (WBS) practices.
341979 -  ..
341980 - This design enables complexity to be understood and applied as an
341981 - asset rather than a liability, per analysis on 930326. ref SDS 6 3345
341982 - Supressing complexity through sole reliance on summary, causes
341983 - mistakes under "Murphy's Law." ref OF 1 1102, which was reviewed at
341984 - the Asilomar Conference on 940612. ref SDS 9 5882
341986 -  ..
341987 - I would like to have in the Subject Index an entry for each Action
341988 - item, but this amounts to a lot of additional work in creating the
341989 - record, and greatly increases the size of the Subject Index. Since we
341990 - are defining "Action Items" above as a lower level of detail, it makes
341991 - sense not to include them in the SI.
341992 -
341993 -      [See later analysis of Internet directories, ref SDS 33 5555.]
341995 -       ..
341996 -      [On 970116 discussed with Morris. ref SDS 34 3109.]
341997 -
341999 -  ..
342000 - SDS Control Field Concerns
342001 -
342002 - A physical restraint on the complexity of the SI is keeping the
342003 - subject string on the screen, rather than have it run off the right
342004 - edge.  This can be solved in part, if we adopt a different SDS design
342005 - of making the SI a separate line number field, so it starts in column
342006 - 10 instead of column 53.  Of course in SDS, since we use codes, our
342007 - subject strings are much shorter than other systems that spell out
342008 - the entire description of a subject.
342010 -  ..
342011 - The need for "deep leveled" subjects arises from the advantage of
342012 - tracking information by its organic level.  In this case it seems
342013 - useful to use a main project heading of "communication" because that
342014 - is a fundamental function of Project Management, like Controls, Scope,
342015 - Planning, and so on.  Within Communication, it seems helpful to track
342016 - Meetings like at PG&E
342018 -  ..
342019 - For now will not re-design control field.  Will use existing
342020 - structure.
342021 -
342023 -  ..
342024 - Requirements
342025 -
342026 - The Subject Index "Communication" account covers the procedures which
342027 - are the "Communication Management" stuff mentioned in the PMBOK
342028 - Section 10; and it also has specific elements like meetings, calls,
342029 - reports and action items that require "connections" to create the
342030 - "understanding" and follow up, per definition of Communication Metrics
342031 - on 950327. ref SDS 13 0000.
342032 -
342034 -  ..
342035 - People want to know the status of Action Items from major meetings or
342036 - as listed in reports.
342037 -
342038 -     It seems useful to keep track of meetings according to the agenda
342039 -     for the meeting, since it reflects the context and mental maps of
342040 -     attendees.
342042 -      ..
342043 -     This will reduce SI complexity by eliminating separate subjects
342044 -     for Action Items (this idea comes from the PG&E experience where
342045 -     we tracked Action Items and Agenda Items separately - see below).
342046 -
342048 -  ..
342049 - Tracking particular meetings, reports, and Action Items will occur,
342050 - plus the relationships between them and other "Subjects" like
342051 - Initiating, Feasibility, Risk, Planning, Controls, Resources, etc.
342053 -  ..
342054 - Action Items can be also be generated outside of meetings, but this is
342055 - the source of greatest felt need, because most of the world still does
342056 - not have SDS which is aimed entirely at tracking Action Items.
342057 -
342058 -     [See follow up on how it turned out at ref SDS 19 0000.]
342059 -
342061 -  ..
342062 - Action Items & Agendas
342063 -
342064 - At PG&E I tracked Action Items separately from meeting Agenda items,
342065 - (see record on 940830, ref SDS 10 0880)  This now seems incorrect, at
342066 - least with respect to the goal of not proliferating and complicating
342067 - the SI.  Creating a separate subject for every Action Item greatly
342068 - increases the data entry in the SI which in turn takes time to perform
342069 - and maintain.
342071 -  ..
342072 - To meet the requirement of quickly determining pending Action Items
342073 - and their status, we will associate Action Items by SI catagory and
342074 - flag them with the SDS highlight function.  This will reduce coding
342075 - and the learning curve, since these elements already exist in SDS.
342076 - May also need reports on when an Action Item is completed.
342078 -  ..
342079 - This will permit assembling Action Items in Summary for meeting notes,
342080 - and will show the line numbers where the Actions occur in the record.
342081 -
342082 -      [This was accomplished at ref SDS 19 0000.]
342083 -
342085 -  ..
342086 - Problems of Prior System
342087 -
342088 - Action Items were summarized in the notes of meetings on the PG&E
342089 - assignment per analysis at ref SDS 10 0880, but it made reports longer
342090 - by adding a summary at the top of the record, in addition to setting
342091 - out the details and context of origination under the appropriate
342092 - subject.  This method met the objective of "communication" by ensuring
342093 - "understanding," ref SDS 13 7777, but it took time to create and time
342094 - to maintain, and it invited errors because duplicate listing of Action
342095 - Items, meant follow up had to be posted in two places, and when this
342096 - was done in the Summary listing, it changed all of the citations to
342097 - the record.
342098 -
342100 -  ..
342101 - SDS Limitation
342102 -
342103 - If we continue to list Action Items twice in a single SDS record, once
342104 - in the body context and again in a Summary, then we need a way to
342105 - create internal links within a single SDS record, so a summary list
342106 - can point to its place of origin elsewhere in the record.
342108 -  ..
342109 - I had this at one time, and then removed the feature because we never
342110 - encountered a situation, scenario or use case where the application
342111 - was actually applied, i.e., it was not useful based on the record it
342112 - was not used.  Now we don't have enough code space in the compiler for
342113 - e.exe to create this feature, because other stuff has replaced it.
342114 -
342116 -  ..
342117 - Solution - Avoid Duplicate Listing
342118 -
342119 - This new system will generate the Action Item summary automatically
342120 - from the detail of the SDS record for each subject.  This eliminates
342121 - the duplicate listing in the Summary of the former system, and so
342122 - saves time to assemble and maintain, and will not disturb citations
342123 - into the record.
342124 -
342126 -  ..
342127 - New Approach Uses Subject Context for Primary Control
342128 -
342129 - Consideration of action items began earlier today during development
342130 - of a Subject Index on Communication for the PMI account, reported on
342131 - 950626. ref SDS 18 0001  I needed to figure out how to structure the
342132 - SI so that there is a correlation between a Meeting Agenda and any
342133 - Action Items that might arise from an Agenda item.
342134 -
342136 -  ..
342137 - Want to avoid Subjects for Action Items, and instead simply track
342138 - actions based on subjects.
342140 -  ..
342141 - Separate Subjects for Action Items were used at PG&E.  This was hard
342142 - to implement because more time and attention is required to track
342143 - Action Items and Agenda items separately.  In that case, extra time
342144 - was invested to experiment on discovering an effective system.  Since
342145 - the system proved to be successful, I want to combine these steps so
342146 - there is less to think about and fewer steps to perform.  The goal is
342147 - to save time and reduce potential error, which in turn saves more
342148 - time.
342149 -
342151 -  ..
342152 - This is the POIMS concept of accomplishing organizational needs as a
342153 - by-product of doing personal work, ref OF 1 0858.
342155 -  ..
342156 - One approach would be to identify each Action Item as a sub-element of
342157 - a meeting Agenda.  This would let an SDS record for a meeting start
342158 - out with a set of subjects for the agenda.  Every meeting has an
342159 - agenda, stated or otherwise.  After the meeting occurs, we could
342160 - append to the Agenda SI item, a uniqueness identifier for any Action
342161 - that arises for that subject.
342163 -  ..
342164 - Turns out to be more practical to avoid the uniqueness identifier
342165 - method because it is an extra step after having figured out and
342166 - explained an Action Item.  Once the decision making process occurs,
342167 - SDS will make it simple to assemble a Summary of what has been
342168 - decided, without adding to the Subject Index.  Instead, rely solely on
342169 - the context of the record captured for each Agenda Item to show any
342170 - Action Items that were established.  This is supplemented by the SDS
342171 - Highlight function, which will serve to select particular contextual
342172 - lines as a summary description of the Action Item for reporting
342173 - purposes.
342174 -
342176 -  ..
342177 - Controlled Visibility
342178 -
342179 - This work began to track Action Items on major meetings, but can be
342180 - applied to any SDS record, say a phone call, or any task, like this
342181 - one of creating a new business system.
342183 -  ..
342184 - Need for controlled visibility is explained above. ref SDS 0 2882
342185 -
342186 -      The follow up produced a new SDS record function to assemble
342187 -      Action Items for a single record, ref SDS 20 8562, and another
342188 -      function for a Summary of subjects in an SDS record, ref SDS 21
342189 -      The single record Action Item list supplements the Subject Report
342190 -      version.  It and the Summary of Subjects, offer a faster way to
342191 -      find a part of an SDS record to use for a citation reference.
342193 -       ..
342194 -      [On 970116 discussed with Morris. ref SDS 34 1732.]
342195 -
342197 -  ..
342198 - Function Index for Action Items
342199 -
342200 - To avoid making another Subject Index for Action Items, we will create
342201 - a new class of Management Functions as follows:
342202 -
342203 -      Note
342204 -      ----
342205 -      I thought about using the "Controls" function in section 13 but
342206 -      Action Items are more closely aligned with "managing" in a
342207 -      general way.
342208 -
342210 -     ..
342211 -    Management Functions 0102 Action Items
342212 -
342213 -    010201   Plan              Original entry
342214 -    01020100       Pending  (see "Procedure" below)
342215 -    01020101       Complete
342216 -    010202   Perform           Work done on action item
342217 -    010203   Report            Report on action item
342218 -    010204   Complete          Final entry
342220 -               ..
342221 -           •  Need to automatically change the Function Code from an
342222 -              "initiate" status to a "work" status when a new follow up
342223 -              task is created, so that each Action Item has only a
342224 -              single point of origination.
342225 -
342226 -                  [Did this at ref SDS 20 0660.]
342228 -               ..
342229 -           •  Note that there can be records of work on a completed
342230 -              action item after it is reported as complete.
342232 -               ..
342233 -              We just want a simple way to enter in the record when it
342234 -              appears that an action is complete.  This will also be
342235 -              shown by the SDS linking tools.  The status of Pending
342236 -              and Complete on the original entry will further indicate
342237 -              this.
342239 -               ..
342240 -           •  We will have to manually change the Function code in the
342241 -              original entry of an Action item from ....00 to ...01.
342242 -              This requires going back and changing the Function code
342243 -              of the orginial entry from pending to non-pending when
342244 -              the task occurs that results in flagging an Action Item
342245 -              as complete
342247 -               ..
342248 -           •  We can assemble a report on all action items entered for
342249 -              the first time by capturing at the 010201 code level.
342250 -              This requires modifying SDS macro 061123 so it does not
342251 -              use a fixed length of the entire Function code field.
342252 -
342253 -                [Did this at ref SDS 19 line 39 for Subject reports,
342254 -                and at ref SDS 20 line 108.
342255 -
342256 -
342257 -
342259 -  ..
342260 - Procedure
342261 -
342262 - Let's make "Pending" be "00" at the end of the string, thus:
342263 -
342264 -                        01020100
342265 -                              --
342267 -  ..
342268 - When we change it to "01" the status will be "not pending."
342269 -
342270 -                        01020101
342271 -                              --
342272 -
342274 -  ..
342275 - This change is only a one-time event in the life of each action item.
342276 - ..
342277 - We will adopt a somewhat curious approach of selecting from the
342278 - SI the following to get all Action Items;
342279 -
342280 -                        010201.....
342282 -  ..
342283 - The SDS code will then select from the SDS diary data base all
342284 - records that have;
342285 -
342286 -                   01020100 or 01020101
342287 -                         --          --
342289 -  ..
342290 - To get only PENDING Action Items, we will select from the SI:
342291 -
342292 -                          01020100
342293 -                                --
342294 -      ..
342295 -      There is NEVER an occassion to select on 01020101.  It is
342296 -      just a way to avoid getting non-pending Action Items when we
342297 -      select 01020100.
342298 -
342299 -
342300 -         [Had to modigy this approach, essentially eliminating the
342301 -         distinction between Pending and non-Pending described above,
342302 -         per ref SDS 27 line 52.]
342303 -
342305 -  ..
342306 - Implementation & Evaluation
342307 -
342308 - This seems to permit assigning Action Items to any subject whether it
342309 - is a meeting or not.
342310 -
342311 - However our primary target is Action Items from major meetings.
342313 -  ..
342314 - Meeting "Agenda Items" can have associated Action Items.
342315 -
342316 -     The User has the option of creating specific Action Items in the
342317 -     SI under an Agenda Item, or simply tracking it using the Agenda
342318 -     description.  The latter is adequate if there is only a single
342319 -     action for an Agenda Item, but if there are several or if there is
342320 -     a major Action Item, it can be worthwhile to give it more
342321 -     visibility with a unique SI description.
342322 -     ..
342323 -     Typically, "major Action Items" are identified in a variety
342324 -     of other ways throughout the SI, for example in the Schedule or
342325 -     Budget.
342326 -
342328 -  ..
342329 - This accomplishes the objective of avoiding proliferation of SI codes
342330 - as began to occur on the CDWR job, ref SDS 10 line 108.
342331 -
342332 -
342333 -
342334 -
342335 -
3424 -

SUBJECTS
Morris Ideas on Action Item System
Major Revision to Concept and Implementation
Action Items Ideas for SDS System

3905 -
3906 - 2127
390701 -  ..
390702 - Morris Proposes Ideas on Action Item System
390703 -
390704 - Called Morris.  He feels the following two issues should be considered
390705 - (discussed a week later in another context, ref SDS 23 5839):
390706 -
390707 -         •  Authority
390708 -         •  Priority, ref SDS 0 0510
390710 -               ..
390711 -              [On 950710 article on this subject. ref SDS 25 0001]
390712 -
390714 -     ..
390715 -    Authority - Morris wants separate AI Program without Context
390716 -
390717 -    Morris wants to track authority and responsibility passed to
390718 -    accomplish the actual work.  Often from the date of inception
390719 -    several people will be assigned portions of work to accomplish an
390720 -    agreed action item.
390722 -     ..
390723 -    He would like a report that shows who asked whom to do what and
390724 -    when they will do it.
390725 -
390726 -        SDS tracks this using the Subject Index and other control
390727 -        criteria.
390729 -         ..
390730 -        Morris wants Action Item support in a separate report, without
390731 -        the context in SDS records, so people don't have to learn and
390732 -        use SDS to accomplish the objective.  He recalled SDS was hard
390733 -        to learn, reported on 920215. ref SDS 5 5820
390735 -         ..
390736 -        We reviewed difficulties caused by error setting responsibility
390737 -        without context.  Delegation requires context to understand and
390738 -        follow up on performing the work, which requires effective
390739 -        "listening," noted by Morris on 890809. ref SDS 3 CJ9J
390740 -
390741 -            [On 010720 Morris is using a Microsoft program to manage
390742 -            action items. ref SDS 36 0001
390743 -
390745 -         ..
390746 -        Traditional Reporting Fails
390747 -
390748 -        I commented that simply providing a TQM report screen would be
390749 -        a lot of busy work that takes time to fill out.  People will
390750 -        ignore it or learn to "work the system."  The system Morris
390751 -        envisions would require everyone to use it in order for anyone
390752 -        to benefit.  People will complain about it, and time will be
390753 -        lost when reports are outdated, incorrect and/or misleading.
390755 -         ..
390756 -        On the other hand, a key objective of this entire exercise is
390757 -        to be able to answer the question:
390758 -
390759 -                    What are the pending Action Items?
390760 -
390762 -         ..
390763 -        Context Needs Summary for Perspective to Absorb Details
390764 -        Linking Summary to Details Manages, Rather Than Hides, Context
390765 -        Controlled Visibility Path to Deeper Levels of Context
390766 -
390767 -        Summary should not hide context of cause and effect provided by
390768 -        details, and context should not mask perspective which is the
390769 -        goal of summary, as stated above. ref SDS 0 2882
390771 -         ..
390772 -        We want to dig out of the details an adequate representative
390773 -        summary in order to work efficiently, yet be able to instantly
390774 -        step back into the details to verify context of cause and
390775 -        effect when needed to make correct decisions.
390776 -
390777 -             [On 960326 discussed connecting summary to details in a
390778 -             meeting with Intel, ref SDS 31 9008,
390780 -              ..
390781 -             [On 960410 described Power of Microcosm in meeting with
390782 -             General Hatch. ref SDS 32 0400]
390784 -              ..
390785 -             [On 970116 discussed with Morris. ref SDS 34 3109.]
390787 -         ..
390788 -        Communication Metrics holds that you cannot rely on a computer
390789 -        report to show who is actually doing the work. You have to talk
390790 -        to the person about their understanding of scope, deliverable,
390791 -        time, quality and so on, that cannot be adequately represented
390792 -        in a computer screen.  Someone describes work as "xyz," someone
390793 -        else calls it "xyw" and you think of it as "xwv," per
390794 -        considerations for risk management on 960322. ref SDS 30 7749
390795 -
390796 -             [On 970116 Morris seems to call this "fractionalized
390797 -             subjects. ref SDS 34 1732]
390799 -         ..
390800 -        SDS seems to help solve this problem by showing the person's
390801 -        thinking.  However, you, also, have to check the actual work
390802 -        from time to time to ensure that what seemed like an
390803 -        understanding is supported by action.  SDS supports both of
390804 -        these requirements by enabling the manager to quickly see what
390805 -        is pending, they can open the SDS record to see who was
390806 -        assigned, and they can check that person's SDS Schedule and
390807 -        Diary to see what, if any, work has been done, what is schedule
390808 -        and what problems have been encountered.
390809 -        ..
390810 -        These steps are necessary whether the Action Item is
390811 -        being done by Tom across the hall to plan a Christmas Party, or
390812 -        for Hans to build a generator in Germany.
390814 -  ..
390815 -
390816 -        A major challenge in all of human affairs is deciding the level
390817 -        of detail to identify and track.  Existence is organic and so
390818 -        it is always possible to break down a task into smaller parts
390819 -        of work and responsibility.  The question becomes what level of
390820 -        detail needs to be tracked in order to get things done, as well
390821 -        as to determine who did what, when and with what result. Indeed
390822 -        this is the purpose of SDS.
390824 -     ..
390825 -    Priority
390826 -
390827 -    Morris wants a way to assign a priority level to an action item so
390828 -    if a higher priority action comes in, all other action items are
390829 -    pushed back.
390830 -
390831 -           [On 950710 article on this subject. ref SDS 25 0001]
390833 -         ..
390834 -        I explained my concern about using automation to exercise
390835 -        judgement.
390837 -         ..
390838 -        People can look at their Schedule and if it shows everything
390839 -        that needs to be done, then the assigned dates of action set
390840 -        the priority.
390842 -     ..
390843 -    [See later review of managing priority at ref SDS 25 line 58.  The
390844 -    main problem is organizational drift, later applied to the NWO
390845 -    paper, ref SDS 26 line 49.  Not keeping on course is the problem
390846 -    Morris feels SDS solves, illustrated by a Project Manager sitting
390847 -    on an arrowhead being blown off course by cross winds, ref SDS 12
390848 -    line 222.]
390849 -    ..
390850 -    The drift problem comes from not being able to identify real
390851 -    priority when daily crisis come and go.  SDS solves this.
390853 -  ..
3909 -
3910 -
3911 - Analysis
3913 -    ..
3914 -
391401 - At this time I am not going to worry about priority and authority. The
391402 - latter is shown in the SDS record in the ordinary course. Priority is
391403 - also shown in the SDS record by placement in the Schedule. The big
391404 - concern is visibility.  When that rush job comes in managers are
391405 - unable to intelligently decide what to do and when to do it, because
391406 - everything they are working on is not visible.  Most of their Action
391407 - Items are hidden under paper or crowded out by the constant stream of
391408 - new activity.
391410 -  ..
391412 -  ..
391413 - We need a way to assemble the actual lines in the record that describe
391414 - each particular Action Item.  I had in mind entering these in the SI,
391415 - but this may be too much busy work.  An alternate method is to
391416 - identify them with an SDS highlight flag.
391417 -
391418 - The problem with this is it may be too loose.  Someone may forget to
391419 - create the flag.  I think the ease of creating the thing is the most
391420 - critical.  All it takes is simple volition.  We don't people filling
391421 - out reports all day long.  We want them thinking about their work so
391422 - they can decide whether an action is needed.
391423 -
391424 -    [See follow up on ideas at ref SDS 24 line 55.]
391425 -
391426 -
391427 -
3915 -