CONTACTS 

SUBJECTS
Wicked Problems Analysis Solution Dialog Mapping Facilitates Meeting
Root Cause Analysis Gary Reports Not Aware SDS Supports Submit Expla
Traceability to Original Sources Provides Context for Understanding
Productivity Meetings Calls Email Management Stream-of-concsious Com
Facilitator, Needs Communication Metrics to Be Effective
Dialog Maps Tedious Hard Work Takes a Lot of Time Requires Work Role
Meetings Listening Intelligence Understanding Follow Up Alignment
C4ISR Command and Control of Project Record Predicate to Building Sy
Problems New Project Similar to Prior Projects that Yielded Counteri
C4ISR Research Complex Project Command Control Progress Success May
Command Control of Work Predicate to Building System of Systems Impr
Proactive Management Gary Plans to Initiate Solutions Take Responsib
Accuracy Verify SDS Record with Notes of Meetings Provide Feedback A
Transformation Steady-as-she-goes Exposure Brings Experience that Tr
Meetings Procedures Good Management Mandatory but Not Performed Subm
Facilitate Meetings Be Prepared Writing Record Organizational Memory
Continual Learning Links Good Management Working Intelligently Trace
Wicked Problems Social Complexity Jeff Conklin

5520 -
5520 -    ..
5521 - Summary/Objective
5522 -
552201 - Follow up ref SDS 6 0000. ref SDS 5 0000.
552202 -
552223 -
552224 -
552226 -  ..
5523 -
5524 -
5525 - Progress
5526 -
552601 - A few days ago received ref DRT 1 0001 dated 041102 from Gary on using
552602 - SDS for deliberative analysis, showing how intelligence support under
552603 - the scope in NWO, ref OF 12 A56M, strengthens traditional practices
552604 - described in his letter.
552606 -  ..
552607 - Gary says in his letter....
552608 -
552609 -    1.  From a paper by Jeff Conklin, "Wicked Problems and Social
552610 -        Complexity".
552611 -
552612 -               http://cognexus.org/id29.htm
552614 -         ..
552615 -    2.  Some problems are so complex that you have to be highly
552616 -        intelligent and well informed just to be undecided about them.
552617 -        --Laurence J. Peter, ref DRT 1 4H5M
552618 -
552619 -           [On 041107 example using SDS to solve difficult problems by
552620 -           explaining the problem, planning solution, reporting on
552621 -           work, and cycling experience into refining the solution.
552622 -           ref SDS 8 UF8N
552624 -            ..
552625 -           [On 041108 discusses challenge of solving difficult problems
552626 -           again that devolve into endless cycles of rework correcting
552627 -           corrections, and cites TOC methods and tools. ref SDS 9 PG4L
552629 -         ..
552630 -    3.  Located the book title. I have it at home and need to look at
552631 -        it again. I *think* it makes that point that there is an entire
552632 -        class of problems that are too many elements to address
552633 -        individually and not enough to treat statistically. ref DRT 1
552634 -        RH6G
552636 -         ..
552637 -    4.  "Wicked Problems, Righteous Solutions: A Catalog of Modern
552638 -        Software Engineering Paradigms" by Peter DeGrace and Leslie
552639 -        Hulet Stahl (Prentice-Hall/YOURDON Press, 1990), ref DRT 1 QF6M
552641 -         ..
552642 -        There is a synopsis at
552643 -
552644 -               http://www.yourdon.com/books/coolbooks/notes/wicked.html
552646 -         ..
552647 -        A brief explanation can be found at
552648 -
552649 -               http://www.poppendieck.com/wicked.htm
552650 -
552652 -         ..
552653 -    5.  WIIFM - What's In It For Me?
552655 -         ..
552656 -        Is there any reason we should care? ref DRT 1 0H9K
552658 -         ..
552659 -    6.  It appears that determining the difference between wicked
552660 -        problem and tame problems involves trying to specify the
552661 -        problem and see if the problem statement changes as solutions
552662 -        are proposed. ref DRT 1 KH8N
552664 -         ..
552665 -    7.  A major point is that wicked problems *cannot* be handled in
552666 -        the same way as tame problems without inviting disaster.
552667 -        ref DRT 1 IH9I
552668 -
552669 -           [On 041107 example using SDS to solve difficult problems by
552670 -           working intelligently -- writing things down, and linking
552671 -           them up -- explaining issues, planning solution, reporting
552672 -           on work, and applying experience to refine the solution.
552673 -           ref SDS 8 UF8N
552675 -            ..
552676 -           [On 041108 discusses challenge of solving difficult problems
552677 -           again that devolve into endless cycles of rework correcting
552678 -           corrections, and cites TOC methods and tools. ref SDS 9 PG4L
552680 -            ..
552681 -           [On 050130 case study yields lessons learned working with
552682 -           Dell to solve "wicked problem." ref SDS 10 344G
552683 -
552684 -
552685 -
552686 -
552688 -  ..
552689 - C4ISR Complex Relationships Dependent Tasks Integrated Components
552690 -
552691 -
552713 -  ..
552714 - Background on challenges developing C4ISR requires research to
552715 - integrate complex systems, i.e., "system of systems" shows that...
552717 -         ..
552718 -        On 030123 report Gary met with Bruce and discussed opportunity
552719 -        for proactive management developing C4ISR. ref SDS 2 KT8L
552721 -         ..
552722 -        On 030506 reviewed opportunity for using SDS for intelligence
552723 -        support that avoids management degrading to entropy, causing
552724 -        delay and failure, by enabling command and control of the work.
552725 -        ref SDS 3 KT5F
552727 -         ..
552728 -        On 030830 Bruce worried project is falling into patterns that
552729 -        caused prior projects to fail; urges efforts to capture the
552730 -        record and connect the dots for recognizing and applying
552731 -        lessons learned; demand grows for using C4ISR to manage the
552732 -        project. ref SDS 4 TY9H
552734 -  ..
552735 - Today, submitted ref DIT 1 0001 responding to Gary's letter dated
552736 - 041102, per above. ref SDS 0 GY4H
552737 -
552738 -    1.  If project staff engage Conklin's ideas, related in your letter
552739 -        on 041102, ref SDS 0 GY4H, a follow up might cite Jeff's letter
552740 -        on 011105 noting effective implementation with SDS "...walking
552741 -        the talk." ref SDS 1 4S6H
552742 -
552743 -           [On 041107 example using SDS to solve difficult problems by
552744 -           working intelligently -- writing things down, and linking
552745 -           them up -- explaining issues, planning solution, reporting
552746 -           on work, and applying experience to refine the solution.
552747 -           ref SDS 8 UF8N
552749 -            ..
552750 -           [On 050130 case study yields lessons learned working with
552751 -           Dell to solve "wicked problem." ref SDS 10 344G
552753 -         ..
552754 -    2.  Woody mentioned the other day on 041004 that many people are
552755 -        aware of difficult problems" but cannot solve them. ref SDS 7
552756 -        LD6G
552758 -         ..
552759 -    3.  Offering a solution recognized by "experts" could garner
552760 -        interest that grows demand for intelligence support,
552761 -        ref OF 12 A56M, enabled by SDS. ref DIT 1 JY6N
552762 -
552763 -           [On 041108 discusses challenge of solving difficult problems
552764 -           again that devolve into endless cycles of rework correcting
552765 -           corrections, and cites TOC methods and tools. ref SDS 9 PG4L
552766 -
552767 -
552768 -
552769 -
552770 -
552771 -
552772 -
552773 -
552774 -
552775 -
552776 -
552777 -
552778 -
552779 -
552780 -
552781 -
552782 -
552783 -
552784 -
5528 -