Dismiss maturity models
Why you should prefer capability models

I wanted to give you a short break from my “Simplify!” blog series. Well, admittedly, I also needed a little break … ;)
Why you should prefer capability models
I wanted to give you a short break from my “Simplify!” blog series. Well, admittedly, I also needed a little break … ;)
The different types of accidental complexity
In the previous post, I discussed the difference between essential and accidental complexity. While we cannot avoid the essential complexity of a given problem, accidental complexity makes things unnecessarily harder without adding any value to the solution.
Distinguishing essential from accidental complexity
In the first post of this blog series, I described two antagonistic observations: IT has become an indispensable part of everyday business and private life while at the same time the complexity on the IT solution side grows all the time, meanwhile being on the verge of unmaintainability.
How the explosion of complexity affects people
In the previous post, I described two observations:
IT of today becoming indispensable and unmanageable
This little post series will be a bit different from the former ones as it discusses a relatively new train of thought of mine. Hence, in some places the reasoning may still feel a bit rough and not as thought out as in prior posts. If you should encounter such a place, please bear with me – and maybe help improving the reasoning via discussing the topic with me.