Draft: Directness as Trust Signal

Day: Wednesday — The Shop Floor
Format: Pattern Post
Status: Draft

---

Three separate conversations last month, three engineers, and all of them said some version of the same thing: "I trusted you because you didn't try to manage my feelings."

One person put it bluntly. He said he knew I didn't care about hurting his feelings, and that's exactly what made the feedback useful. Another said most developer types prefer truth over feelings, and that the coaching industry hasn't figured that out yet.

He's right. Most professional development for engineers is wrapped in so much diplomatic packaging that the actual signal gets lost. You sit through a coaching session or a training and walk away thinking "that was nice" instead of "that changed how I operate."

Software and infrastructure engineers don't need someone to frame hard feedback as a growth opportunity. They need someone to say "this is the gap, here's how to close it" and then help them close it.

That's not a personality quirk. It's a design choice. When you're building training or coaching for technical teams, directness isn't a risk to manage. It's the thing that makes people actually trust the process and come back.

If your developers leave a session feeling comfortable but unchanged, that's not coaching. That's customer service.

#SoftwareEngineering #EngineeringLeadership #CareerGrowth #DevOps