I was reading this Reddit thread about rubber duck debugging (which I had not heard of until just recently) and after finding out what it was, I realized that this problem-solving technique could definitely be applied to many other circumstances as well.

The name comes from a trick software engineers use to debug code. When something isn’t working correctly, the engineer would explain the code/software line by line to an inanimate object (in this case, a rubber duck) until he/she gets to a point where he/she realizes that the code is wrong because the explanation does not compute in words.

The Reddit thread goes into many examples of how this simple technique is effective, even beyond software engineering professions. I like this. :)