How to Avoid the Agile Manifesto Confusion by Explaining Agile from First Principles
That was a great read Maarten. I'm in the same ballpark, though I have to admit to using Cynefin as a crutch. I really like how you linked complex and chaos to goal driven. I often link simple-complicated to plan driven, but for complex and chaos I usually talk about experiments, probes, validating, creating a pocket of stability (that first step on the unbeaten path). Goal driven is much more concise there, I'll be adding that to my toolkit.
As the manifesto goes, I feel the 12 principles are undervalued. A few have become stale, but the bulk of them are solid. Basic stuff, but it's still rare to see companies truly *do* it. The manifesto is old, basic and outdated (according to some), and at the same time few are managing to truly pull that basic stuff off. Don't get me started on people saying "agile is dead" and proceeding to run through the values and principles in slightly different words for "what you instead should do" SMH. No denying Agile as a term does feel very yucky and I try to avoid it or own up to the yuckyness and usually judo that into 'what it's about'.
Final and most important thing: am I alone in seeing an uncanny resemblance between Vom Kriege and Christiaan Verwijs? ; )