I’ve been in a room where a demo was broken, a deadline was slipping, and everyone had an opinion about whose fault it was. Nobody wrote a line of code that afternoon. We just needed to talk to each other.
That is the real engineering work sometimes.
Status updates aren’t vanity
A good status update does three things. It tells people where things stand, what’s blocking them, and what they should do next. If your update needs interpretation, it’s a mystery, not a message.
I write my team’s updates the way I’d write a commit message. Short, honest, and actionable.
Blameless is a practice, not a policy
Blameless post-mortems sound nice, but they only work when you’ve built the trust to support them. That means:
- Leads admit their own mistakes out loud, first.
- Retrospectives focus on systems, not individuals.
- Questions like “what could have caught this earlier?” replace “who did this?”
The emotional update
The hardest communication isn’t technical. It’s emotional. Telling a stakeholder the timeline moved. Telling an engineer their architecture won’t work. Being direct without being harsh is a skill, and like any skill, it needs practice.
Under pressure, the instinct is to pad, hedge, or go quiet. I’ve learned the opposite is stronger. Short, honest, and early beats long, reassuring, and late.
These skills don’t show up in a changelog, but they matter on every project. That’s why I treat communication as part of the work, not something separate from it.