Every engineer knows rubber duck debugging

You explain the problem out loud to a rubber object. The duck says nothing. And somehow, the answer covers.

When I first discovered this in coaching, it felt like a perfect metaphor. The coach is a rubber duck — a safe, non-judgmental presence where the client can think out loud. But something felt off.

A rubber duck cannot notice the moment your voice shifts. It cannot reflect back the paradox between what you said five-twenty minutes ago and what you just said now. It cannot ask the one question that reframes everything.

Passive presence is not coaching. It is just a comfortable silence.

The real difference is this: debugging looks for what is broken. The work I am learning to do looks for what is not yet built — the feature the person in front of me has not yet imagined for themselves.

That requires full attention. Not just to the words, but to what is moving underneath them.

What is the difference between someone truly listening to you and someone simply waiting for you to finish?

🔗 LinkedIn Profile