There's a term used when debugging code - "Rubber Ducking". The term refers to the practice of explaining how code should function to some fictional observer (presumably a rubber duck) who has no pre-requisite knowledge. This forces you to slow your thinking down, take a fresh approach, and to clarify your process.
This is why I have Clarence: