A couple days ago, I posted an article on UX Magazine about inexact design. It follows from the way I have been working for a long while, and some presentations I've given, but after reading some other work on electronics design and service availability (and talking with some other smart UX folks) I codified it a bit more.
As far as design goes, it about how we can design better systems by realizing everything is too complex to predict, so not trying to avoid errors, but embracing failure and uncertainty. "How it fails" is as important as "how it
Anyway, as much as I enjoy the praise so far for it, I want to make sure it's a valid thought. What seems misguided, stupid, unclear, etc? I want to know, partly as I am slated to have a more-specifics-centric followup article, so I can work on it and incorporate any feedback.