In my case, at least, essentially all the time taken to solve the problem was “decoding” it—working out what it was really saying. That is: fnlvat gung jura lbh jevgr n ahzore va onfr o vg raqf va n gjb vf rknpgyl gur fnzr guvat nf fnlvat gung gur ahzore rdhnyf gjb zbqhyb o, naq (vs lbh’er hfrq gb guvf fghss) gb fnl gung vf gb frr gur fbyhgvba.
Never underestimate the utility of properly describing a problem. I’ve found that it’s really amazing how often, by the time you’ve figured out what question you really want to ask to solve the problem, you’re already most of the way to the answer...
Noted. Thanks, this tells me that to someone with some knowledge of mathematics it really is as obvious as it looked.
In my case, at least, essentially all the time taken to solve the problem was “decoding” it—working out what it was really saying. That is: fnlvat gung jura lbh jevgr n ahzore va onfr o vg raqf va n gjb vf rknpgyl gur fnzr guvat nf fnlvat gung gur ahzore rdhnyf gjb zbqhyb o, naq (vs lbh’er hfrq gb guvf fghss) gb fnl gung vf gb frr gur fbyhgvba.
Never underestimate the utility of properly describing a problem. I’ve found that it’s really amazing how often, by the time you’ve figured out what question you really want to ask to solve the problem, you’re already most of the way to the answer...
Yes, I very much agree.
I think this is the basis of good Business Analysis. A field I’m intending to move into.
It’s the very essence of “Hold off on proposing solutions”.