Hi there,
Remember the last time your flight was delayed?
You (likely) had no idea why and you just had to… wait.
It’s a frustrating feeling.
But we all remember that one delayed flight where the agent kept everyone clearly informed of the status. Your flight just took off from San Francisco. Your airline crew just landed in Terminal B and is on their way over.
Be that hero gate attendant for your colleagues.
⚡ Supercharge of the Week
Remote Octopus recommends providing clarity on any unexpected delays in deliverables. Keep it short and sweet.
Delays without clarity lead to unnecessary anxiety and confusion.
When we’re entrenched in the day to day of delivering the work, delays might seem obvious to us. There was an off-site scheduled last minute or marketing re-org’d or a P0 request took priority.
But what seems obvious to us might be completely off the radar for cross-functional colleagues or leadership. All they see is an unexpected delay.
The next time you’re communicating a delay – whether it’s a Slack update or on a call – add in simple context as to why.
EXAMPLE IN ACTION
Our new target launch date is Wed 8/6 [previously Mon 8/4].
Context: Design staffing was shifted 100% to Project Starfish for 2 days last week.
Short, simple, and easy to read at a glance. Calling out the context itself streamlines understanding for colleagues moving quickly.
Added bonus: You’ll have a much more productive afternoon – instead of pausing to answer 10 different follow up Slack messages about why a deliverable is delayed!
👀 ICYMI
🐙 Remote Octopus Resources
Ready to level up operational excellence for your team? Check out our resources:


