Hi there,
Launches are always chaotic.
It feels like there are so many cooks in the kitchen.
And it can feel intimidating to speak up and voice our concerns.
Someone probably already thought of this, we think.
Guess what? Guaranteed almost everyone on the launch team is sitting on a unique someone already probably thought of this insight – and you have no idea until you ask.
P.S. A human will always write Remote Octopus but we’re finding a lot of success leveraging single-turn, fully-specified prompts. This paper does a great deep dive.
⚡ Supercharge of the Week
Remote Octopus recommends checking in with key stakeholders before any major launch to identify their top concerns.
These key stakeholders might include:
The leader accountable for the launch
Cross-functional colleagues who are Contributors on the launch RACI
Your manager — who might have important insights even if they’re not directly involved in the launch itself
Checking in on top concerns is best done over a Zoom call or Slack huddle so you can dig a bit deeper into the concerns if needed. Slack messages can work in a pinch.
⏰ It’s all in the timing. While a team might talk through a pre-mortem exercise together, these pulses are meant to be 1:1 check-ins about 2 weeks prior to the launch. It’s important that you have enough time to gather insights and then take action. Chatting about top concerns 1-2 days before launch will often leave you stuck.
EXAMPLE IN ACTION
Hi Diego – Checking in as we prep for Y launch, do you have any concerns top of mind?
Dig deeper if needed. Try: Tell me more about that. You’re in information-gathering mode as you try to understand the top concerns across cross-functional SMEs.
Once those top concerns are gathered? Synthesize how to best mitigate their concerns. Identify what actions or tasks the team can take now – about 2 weeks prior to launch – that will improve the launch itself. Add these to team documentation.
➡️ Remember: A few days after you chat and before the launch, always follow up 1:1 with those who shared their top concerns. Clearly outline the steps the team will take to mitigate their concerns before launch. Do a quick pulse if anything else is top of mind.
🐙 Remote Octopus Resources
Ready to level up operational excellence for your team? Check out our resources:
