This reminds me of an article I found recently while trying to explain to a business analyst that the problems we are solving aren't simple.
I think what is bad is confusing complex and complicated things for simple things. If you think a problem is simple, when it is complex or complicated, then you'll expect the solution sooner and you won't think deeply about all the ramifications of the solution. You'll avoid breaking the complexity down into simple parts.
By their nature, complex things are unpredictable. Things that behave unpredictably are complex. It doesn't make them bad, just means they need more attention and thought to understand -- and sometimes accept.
Another good resource I just discovered is the Cynefin framework that breaks it down further:
> obvious, complicated, complex, chaotic, and disorder
> complexity lets you do more complex things, have whatever you are building or rules you are making achieve more complex outcomes, and to better understand and explain things that are complex, which is most things. Complexity is highly useful.
Anyway, I liked the values the author shared. That is values to consider when designing a complex system: Resonance, Chunking, Ramping, Hiding, Emergent. They actually sound like a good way to organize presentations.