3 ms·
Don't bring me solutions, bring me well-formed problems (that are unsolvable at your level of resource allocation.) But that's far less catchy...
by lifeisstillgood 6y ago
Don't bring me solutions, bring me well-formed problems
(that are unsolvable at your level of resource allocation.)
But that's far less catchy...
- taneq 6y agoExactly. This is the organisational equivalent of the various "how to ask questions" lists that have done the rounds over the years. You don't go to your boss and say "everything's fubar". You go and say "there's a conflict between X and Y that we can't solve because of Z".
- wyattpeak 6y agoI think it's also something that takes a lot of work to teach, and is probably domain-specific. I get it a lot dealing with bug reports. Bug reports without enough information to be reproducible are a well discussed problem, but there are also a subset which have vastly too much detail musing about cause, which are often fairly misguided. In trying to make my job easier, the reporter has spent a lot of time pursuing something unhelpful, because they don't have the knowledge to know what to look for. Writing a truly well-formed bug report requires a reasonable degree of familiarity with bug-finding and -fixing. And I suspect the same is true in many domains.