Realisation #900: I hate underwire bras.

Well yes, but what I really want to say is

Realisation #901: I wish my team can take a more efficient approach to problem solving.

Let's say there's a muffin-baker and a brownie-baker. Each follows his own recipe and understands generally what the other's job entails.

The muffin-baker encounters a problem in step n of his recipe, but he knows that steps 1 to (n-1) are correct. He asks the brownie-baker for help. The brownie-baker will then ask the muffin-baker everything from steps 1 to n, to find out what went wrong.

The muffin-baker will explain all as requested, but will get frustrated cos nothing is done for step n yet. The brownie-baker will listen and also get frustrated cos there's too much to absorb.

But what I thought will be more efficient was just to ascertain that steps 1 to (n-1) are correct, and then ignore them. Instead, they should just concentrate on the inputs for step n and trace that. It is not necessary for the brownie-baker to learn the whole process on how to bake muffins in order to solve the problem, but time after time, this is what took place.

People can't seem to isolate the problem before solving it.