01
Surface problems are rarely surface
When something isn't working, the instinct is to fix what you can see. That's almost always the wrong layer.
A clumsy button, a missing feature, a flow that feels off: that's where everyone looks first, and where the answer almost never is. If what you built actually solved a real problem, people would claw through a bad interface to reach it. So when nothing's working, I don't touch the surface. I go back to the problem and check whether I ever really had it.
02
Silence is not neutral
A gap you don't fill, the other person fills for you. Under pressure, they fill it with the worst version.
Withholding a hard note feels like the kind move. It's the cruel one. The honest sentence I'm afraid to say is almost always smaller than the story someone invents in its absence. So I say the direct thing early, especially to the people I trust most, because trust is what makes directness survivable.
03
Depth across the stack
Better calls happen when strategy, implementation, and the person on the other end all stay within arm's reach.
When whoever decides what to build also knows how it's built and who it's for, the trade-offs stop being guesses. One hand on strategy, one on the keyboard, both pointed at a real person. The technical depth and the human read were never two skills. They're the same one.