Pre-Launch Futurespective

Pre-Launch Futurespective format

Critical Preparations

What must be done before we can launch?

Critical Preparations are the non-negotiable tasks, checks, and sign-offs that must be completed before the launch can go ahead. This topic helps the team surface any gaps in readiness — from technical prerequisites and documentation to stakeholder approvals and support team training. Encourage participants to think about what would cause the launch to fail or be delayed if it were missing. Prioritize ruthlessly: not everything is critical, so push the team to distinguish between 'must have' and 'nice to have'.

Boosters

What will accelerate our launch success?

Boosters are the actions, assets, and conditions that will amplify the impact of the launch and drive adoption, engagement, or revenue. This topic shifts the team into an energizing, opportunity-focused mindset. Encourage participants to think about marketing activities, internal champions, partnerships, timing advantages, or product features that could create momentum. Ask: 'What could make this launch go from good to great?' Use this topic to ensure the team isn't just focused on risk mitigation but is also investing in what will make the launch shine.

Monitoring & Signals

How will we know if the launch is succeeding or struggling?

Monitoring & Signals covers the metrics, alerts, dashboards, and feedback loops the team will use to track the health of the launch in real time. This topic ensures the team has agreed on what 'good' looks like and has the instrumentation in place to detect problems early. Encourage participants to think about both technical signals (error rates, latency, uptime) and product/business signals (activation rates, support ticket volume, NPS). Ask: 'If something goes wrong at 2am on launch night, how will we know?' This topic often surfaces gaps in observability and alerting that are critical to address before go-live.

Risks & Unknowns

What could go wrong or catch us off guard?

Risks & Unknowns is where the team surfaces the things that keep them up at night — the assumptions that haven't been validated, the dependencies that are out of their control, and the scenarios they haven't fully planned for. This topic is not about being pessimistic; it's about being honest so the team can take proactive steps. Encourage participants to think about technical risks, third-party dependencies, team capacity, and market or customer unknowns. For each risk raised, prompt the group to consider: 'What's our mitigation plan?' or 'Who owns this?'

When to use this retrospective

• Your team is 1–4 weeks away from a significant product or feature launch and wants to ensure nothing critical has been overlooked.
• You're coordinating a cross-functional launch involving engineering, marketing, sales, and support, and need a structured way to align everyone on readiness.
• Your team has experienced a difficult launch in the past and wants to be more intentional and proactive in their preparation this time.
• You're launching into a new market or to a significantly larger audience than before, and the stakes of getting it wrong are higher than usual.
• You want to build a repeatable launch readiness practice within your team and need a consistent framework to run before every major release.

Suggested icebreaker questions

• If your launch were a rocket, what stage of the countdown are you at right now — and is everything go for launch?
• What's the most memorable product launch you've ever witnessed (good or bad), and what made it stick in your memory?

Ideas and tips for your retrospective meeting

• Run this futurespective 1–2 sprints before your target launch date — early enough to act on what you discover, but close enough that the details are real and concrete.
• Invite cross-functional participants including engineering, product, design, marketing, and support. Launch readiness is a team sport, and blind spots often live at the boundaries between functions.
• Use dot voting or priority ranking on the Critical Preparations and Risks topics to ensure the team focuses on the highest-impact items first, rather than trying to solve everything at once.
• Avoid letting the session become a status update meeting. If someone raises a preparation item that's already done, acknowledge it and move on — the goal is to find gaps, not rehearse what's complete.
• Assign clear owners and due dates to every action that comes out of the session before you close. A futurespective without follow-through is just wishful thinking.
• Revisit the Monitoring & Signals topic outputs after launch to run a quick post-launch review — it's a great way to close the loop and build your team's launch playbook over time.