Ambiguity and uncertainty are anathema to approaching problems from the classic engineering mindset. That's not a bad thing when used properly, and it's great i

Ambiguity and uncertainty are anathema to approaching problems from the classic engineering mindset. That's not a bad thing when used properly, and it's great in school where people hand you a stream of problems designed to be interesting in that mentality, but it's not the general-purpose tool for interfacing with all problems, as some imagine. I've worked both as a developer and designer, and with design tasks, you've only got a fuzzy sense of the wrong answers before you manage to craft a right one. Many, if not most engineers find it much easier to assume designers sit around all day moving things about as they fancy rather than imagining what it would take to solve ambiguous problems with no way to determine if you've got a really good solution until many people start interacting with it.