Hi there,
Oh no, is Gia out today? When will she be back?!
We’re blocked until Rashad is back on Monday.
We’ve all been there. 😵💫
A colleague takes time off + somehow the XFN comms were dropped.
You see a dependency blocked by an OOO.
💡 We see an opportunity to reduce risk.
⚡ Supercharge of the Week
Remote Octopus recommends a quick check in with key XFN collaborators 2-3 days before you are OOO to confirm if there are any impacted dependencies.
Why?
Key collaborators might’ve missed the message that you’re OOO soon – or they might be working so quickly that they forgot the week you’re out is already next week.
A quick double-check will ensure that XFN work moves smoothly while you are out of office. It is an opportunity for risk prevention.
Asking 2-3 days in advance is designed for you to have 2-3 days to address any of their quick requests before you are out. If you wait to ask until a few hours before you log off then you might not receive replies or have enough time to support your team before you hop on that airplane.
When is this double-check most helpful?
If you’ll be OOO 2+ days
If you’ll be OOO any amount of time around a launch or deadline
Consider the current projects you’re supporting + reach out to your top 3-5 XFN collaborators to check in with a quick Slack.
EXAMPLE IN ACTION
Hi Vasha – Quick reminder that I’ll be OOO next week. Is there anything you need on my end before I’m out? You can find my OOO coverage plan here.
Bonus points for preparing + sharing your OOO coverage plan that clearly identifies who to contact about specific projects while you are out.
Focus on over-communication. Did you already share your OOO coverage plan with colleagues a week ago? A quick check in can still reduce risk – a lot can change in one week! Then enjoy your OOO time at ease knowing your team has everything they need while you’re recharging on a beach or mountain. 🌴
🐙 Remote Octopus Resources
Ready to level up operational excellence for your team? Check out our resources:
