Work Communication
Speak up in meetings, explain technical ideas to any audience, and handle feedback with confidence — professional communication for analytical minds.
Engineering work runs on communication with a compiler in the middle. Standups, code reviews, estimates, trade-off discussions, and incident updates are where your technical judgment either reaches other people or doesn't, and where quiet, careful engineers most often get underestimated.
These guides give you language for those moments: what to say in a standup, how to write review comments that are direct without being rude, how to explain trade-offs to non-technical stakeholders, how to push back on scope or a deadline, how to tell stakeholders a project is late, and how to write incident updates without assigning blame.
The rest covers career communication: asking for help without looking incompetent, visibility without self-promotion, speaking up in meetings, declining meetings, giving and taking feedback, and asking for a promotion. Many include wording you can adapt, because a good template beats a principle when you are writing the message at 5 p.m.
New here? Start with these
- 1What to Say in a Standup: 25 Examples for Software Engineers
The daily rep: clear updates in under a minute.
- 2How to Explain Technical Trade-Offs to Non-Technical Stakeholders
Getting decisions made by people who don't read the code.
- 3Visibility Without Self-Promotion for Quiet Engineers
Making your work visible without bragging.
13 Guides in Work Communication
What to Say in a Standup: 25 Examples for Software Engineers
Use 25 realistic software-engineering standup examples to share progress, explain blockers, ask for help, and keep your update concise.
Read guide →
How to Write Code Review Comments Without Sounding Rude
Write code review comments that are clear, respectful, and actionable. Includes practical scripts for bugs, design concerns, nits, and disagreements.
Read guide →
How to Explain Technical Trade-Offs to Non-Technical Stakeholders
Explain technical trade-offs in plain language, connect options to business outcomes, and help non-technical stakeholders make informed decisions.
Read guide →
How to Communicate Estimates Without Overpromising
Give software estimates without false certainty. Learn how to communicate ranges, assumptions, confidence, risks, and changes before they become surprises.
Read guide →
How to Push Back on Scope or an Unrealistic Deadline
Practical scripts for pushing back on scope creep and unrealistic deadlines without sounding negative, difficult, or unwilling to help.
Read guide →
How to Ask for Help as a Developer Without Looking Incompetent
Learn when and how to ask for coding help with concise context, useful evidence, and developer-friendly scripts for Slack, pairing, and reviews.
Read guide →
Visibility Without Self-Promotion for Quiet Engineers
A practical visibility system for quiet software engineers: make impact, decisions, and collaboration visible without bragging or becoming performative.
Read guide →
How to Tell Stakeholders a Project Is Late
A practical guide to communicating project delays clearly, rebuilding confidence, and giving stakeholders useful choices instead of vague apologies.
Read guide →
How to Ask for a Promotion as an Engineer
How engineers can build a clear promotion case, start the conversation, and turn vague feedback into concrete expectations without awkward self-hype.
Read guide →
Incident Updates and Blameless Postmortem Language
Practical templates for clear software incident updates and blameless postmortems that preserve accountability, uncertainty, and useful technical detail.
Read guide →
How to Speak Up at Work Without Being Awkward
A practical framework for sharing ideas in meetings, presenting to non-technical people, and finding your voice at work — without the mental gymnastics.
Read guide →
How to Give and Take Feedback Without Making It Personal
A clear framework for giving critical feedback that doesn't sting and receiving it without spiraling, using the OFNR formula and work-from-person separation.
Read guide →
How to Decline a Meeting Without Looking Like a Jerk
Practical scripts and strategies for protecting your focus time by saying no to unnecessary meetings — without burning bridges.
Read guide →Communication Trainer
Reading only gets you halfway
Disagree with your (AI) manager until doing it for real feels boring. Realistic pushback, honest feedback on the transcript.
Explore all topics
Check out our other guides on dating, conversations, friendships, and more.
View All Topics