Reflection Shorts - "Win that Communication" - episode #4
How to Post a Status Update that Actually Benefits Others?
A Bad Status Update goes like this:
“I want to give you a status update about Project Kepler which is to implement green carbon emissions tracking software. You know we have been running this project just fine. We have done many things like…XYZ. It was going smoothly until we found scaling issues in service X. The problem needs expert advice on the TCP layer from a seasoned engineer. We want more resources to bring the project back on track and hence I request the leadership to help us here”
This update is misleading on multiple levels:
❌ The first sentence focuses on the writer's “wants,” not the reader's needs.
❌ Saying you’re giving a status update within the status update is redundant. By now, readers have spent 2-5 seconds reading and gained nothing.
❌ The write-up includes too many unnecessary details, causing readers to lose interest due to their short attention spans.
❌ What does "seasoned engineer" mean here? Seasoned in TCP, networking, or just an experienced engineer?
❌ Finally, readers are left confused. What’s in it for them? Should they be worried or happy? Is this an update or just details? Is there an action item for them or the leadership? The term “leadership” is too broad.
Here’s a better way to present the same status update:
On Project Kepler, we have hit a snag.
Action Item: I request Jon to please help us evacuate this situation by providing a seasoned network engineer from the SRE team.
Details of the issue: We hit an issue with dropping packets when making cross-region calls and …
Project Context (for new readers): Project Kepler which is to implement green carbon emissions tracking software. We have been running experiments with…XXX. We have done many things like…XYZ
Why is this status update effective?
✅ It highlights the core issue and grabs the reader’s attention in the first line.
✅ The action item is clear and immediate.
✅ The remaining details are discretionary and placed at the end.
Bonus point, if you want to share good news, it would look like this:
On Project Kepler, we are on track and the good news is that we are running smoothly such that there is no action item on anyone right now.
Context: Project Kepler is to implement…
What’s so nice and great about this update?
😀 It sets up a positive and relaxing platform for the readers.
🕺 Readers won’t even read the rest of the message after the first line. You have given them the power to forget about this and move forward with their work.
🚀 Them not reading the rest of the message is not a failure on your end. Instead, it’s a huge win because you saved them and your time reading and writing long messages.
That’s it for today. If you are wondering “What’s a Reflection Short?” Read here.
References
Shoutouts
How I became a VP of Engineering at Box by Jean-Baptiste Coger
Congratulations Dev Leader on one year of Dev Leader Weekly!
Let’s Connect 🤝
👋 Hey there, I am Gourav. I write about Engineering, Productivity, Thought Leadership, and the Mysteries of the mind!
Use the below links if you want to connect with me.
Sponsorship | Collaboration | LinkedIn | 1:1 Mentoring | Twitter
Informative Post!! 💯
Thanks for the shoutout! 52 issues! 🎉🙂