Rubber Duck Debugging
Explain your problem to an inanimate object.
Explanation
Many programmers keep a rubber duck on their desk and explain their problematic code to it line by line. Surprisingly often, the act of explaining the problem out loud reveals the solution. This works because verbalizing forces you to think sequentially and clearly, often exposing assumptions or gaps in logic that weren't obvious when the problem was just in your head.
Real-World Example
Developer stuck for hours. Explains to duck: 'This function takes user input, validates it, then... oh wait, I'm not validating negative numbers.' Problem solved. Writer with plot hole explains story to teddy bear, realizes timeline doesn't work. Manager explains staffing problem to coffee cup, sees obvious solution.
How to Apply
Get object (duck, plant, anything). Explain problem from beginning. Be detailed—no shortcuts. Say it out loud (important!). When you say 'obviously' or 'somehow'—that's where the problem is. If stuck, explain what you've tried and why it didn't work. Solution often emerges mid-explanation.