- Emergent Complexity - consequence of many small and unrelated decisions and actions.
- Perverse Complexity - consequence of clumsy attempts to reduce complexity.
- Contrived Complexity - consequence of deliberately creation to benefit some stakeholders.
- Irreducible Complexity - consequence of real complexity of the demand environment.
- Emergent Complexity
- Perverse Complexity
- Irreducible Complexity
- Contrived Complexity
- coordination for Simple Problems
- cooperation for Complicated Problems
- collaboration for Complex Problems
- Any method for Chaos to shift to one of the other three complexity domains
So I call that now the EPIC SCAN.
So how do I link this knowledge to GLUE. First of all I look into optimizing or fixing the flows in the GLUE Space. Here applying the right approach to way of working and finding the right skill and mindset is in most cases more important than finding the perfect answer. The people will find the right answer inevitable if their skills and mindset fit to the complexity domain. If the fit is not given then they will try to shift the complexity into another domain or start being frustrated. A typical statement here is: "If X would just understand me".
And unfortunately there is no Silver Bullet to it. Not even Ken Schwaber markets the methodology SCRUM that way. In a recent post he clearly links SCRUM to the complex domain (where the unknown is greater than the known). In spaces where the known is greater than the unknown SCRUM creates more waste than needed and other methods (if applied correctly) will produce results in a less wastefull way. The challenge is to find the right method to maximize Value Add. And for those who are still unsure: the complexity area where I love the Domain Enterprise Architecture most is in the Chaos, no matter where in GLUE.