The ten characteristics of wicked problems that engineers need to understand are as follows:
- There is no definitive formulation of the problem itself.
- There is no stopping rule.
- Solutions are not true-or-false, but good-or-bad.
- There is no immediate or ultimate test of a solution.
- Every solution is a "one-shot operation" in that every attempt counts significantly.
- Wicked problems do not have an enumerable set of potential solutions, nor is there a well-described set of permissible operations that may be incorporated into the plan.
- Every wicked problem is essentially unique.
- Every wicked problem can be considered to be a symptom of another problem. (This one is really important. Take urban planning, for instance. Look around your city and you will see countless examples of the unintended consequences of a failure to understand a complex system. Engineering still thinks in terms of the "script" and "silo-planning" - - but never system connections, interfaces, and overlaps.)
- The existence of a discrepancy representing a wicked problem can be explained in numerous ways. The choice of explanation determines the nature of the problem's resolution.
- The [decision maker] has no right to be wrong.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.