MS
Maya Support
If Support isn’t trained before launch, customers are going to wait too long for help.
Launch Readiness
Talk through the launch. Leave with the decision.
Readiness by function, blockers, conditions, and commitments take shape as the discussion unfolds—ready for the team to review and confirm.
Just talk. BigWow keeps up. No special commands or constant note-taking. Have the conversation you were already going to have.
From Maya Risk · needs decision
Support readiness Launch risk Train Support before launch
AL
Ari Decision owner
“Conditional go. Maya will train Support Wednesday; Noah will verify analytics tomorrow.”
Conditional go Confirmed by Ari ✓
Launch decision ✓
Conditional go Requirement Verify production analytics Noah · Tomorrow, 10am
Requirement Train Support for launch Maya · Wednesday
From Maya→Confirmed by Ari
How the template helps
A guide for the conversation—not homework for the team.
The current launch question stays visible while the discussion moves naturally.
What the team leaves with
A launch record people can act on.
The decision, rationale, remaining requirements, owners, dates, and source comments stay together.
Run a launch-readiness reviewAtlas v2 launch Decision record
Conditional goConfirmed outcome Proceed with the September 12 launch
Two requirements must clear before the customer announcement.
Requirement Confirmed
Verify production analytics Noah · Tomorrow, 10am
From Engineering’s readiness signalRequirement Confirmed
Train Support for launch Maya · Wednesday
From Maya’s readiness concern