In software development there is the idea of Rubber Duck Debugging.

“Rubber duck debugging
From Wikipedia, the free encyclopedia
In software engineering, rubber duck debugging or rubber ducking is a method of debugging code. The name is a reference to a story in the book The Pragmatic Programmer in which a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by-line, to the duck.[1] Many other terms exist for this technique, often involving different inanimate objects.

Many programmers have had the experience of explaining a problem to someone else, possibly even to someone who knows nothing about programming, and then hitting upon the solution in the process of explaining the problem. In describing what the code is supposed to do and observing what it actually does, any incongruity between these two becomes apparent.[2] More generally, teaching a subject forces its evaluation from different perspectives and can provide a deeper understanding.[3] By using an inanimate object, the programmer can try to accomplish this without having to interrupt anyone else.”

I've been working on how to model projects and I have turtles in my model and I guess I could start talking to them to debug the process.

I started with the cubes. then added arrows and pawns on a dungeons and dragons grid. I am off to a data center next week to review the project ideas and I am ready for them to laugh at my turtles and modeling.

You are probably laughing, but the ideas I am coming up with are pretty good. The purple turtle frequently likes the ideas I tell him. :-)