Which function(s) are you representing in this decision?
- Product Management
- Engineering
- Design/UX
- QA/Testing
- Data/Analytics
- Security/Privacy
- Legal/Compliance
- Sales
- Marketing
- Customer Support/Success
- Finance
- DevOps/SRE
What stage is the initiative currently in?
- Discovery
- Alpha
- Beta
- General Availability (GA)
- Hotfix/Patch
How confident are you in launching on the planned date?
Range: 1 – 10
Min: Not at all confidentMid: NeutralMax: Very confident
If you rated 1–3, what are the main blockers or unknowns to address before launch?
Max 600 chars
What is your current recommendation?
- Go as planned
- Go with minor conditions
- Delay to address issues
- No go (do not launch)
- Need more data
What specific data, tests, or evidence would help you make a clearer recommendation?
Max 600 chars
Based on current evidence, rate readiness for each area.
| Rows | Not ready | Partially ready | Mostly ready | Ready with caveats | Fully ready |
|---|
| Product scope clarity | • | • | • | • | • |
| Engineering implementation | • | • | • | • | • |
| QA/Testing coverage | • | • | • | • | • |
| Security/Privacy review | • | • | • | • | • |
| Observability/telemetry in place | • | • | • | • | • |
| Support/Customer Success readiness | • | • | • | • | • |
| Legal/Compliance approvals | • | • | • | • | • |
| Release packaging and documentation | • | • | • | • | • |
Overall launch risk level (based on the current state).
Scale: 10 (star)
Min: Low riskMax: High risk
Rank the top risks to launch readiness (drag to order).
Drag to order (top = most important)
- Timeline slippage
- Quality defects
- Scope creep
- External dependency
- Limited capacity/resources
- Compliance or privacy risk
Which dependencies could impact the launch if unresolved?
- Backend service/API
- Third-party vendor readiness/change
- Security review / pen test
- Legal review
- App store approval (if applicable)
- Data migration
- Localization/translation
- Support content/training
- Sales enablement
- Analytics instrumentation
Which go-live checks are complete?
- Runbook documented
- Monitoring/alerts configured
- Rollback plan tested
- On-call coverage scheduled
- Communication plan approved
- Support documentation ready
Are day-one success metrics defined and instrumented?
- Yes, fully defined and instrumented
- Partially defined or not fully instrumented
- No
- Not applicable
What rollout strategy do you recommend for this launch?
- Big bang
- Phased rollout
- Feature flag/toggle
- A/B experiment
- Pilot/allowlist
- Not decided
List the most important mitigation steps we should take before launch.
Max 600 chars
Allocate 100 points to where the next 2 weeks of effort should focus.
Total must equal 100
- Product scope clarification
- Engineering implementation
- QA/Testing
- Security/Privacy
- Observability/Telemetry
- Support/Customer Success readiness
- Legal/Compliance
- Release packaging and documentation
Min per option: 0Whole numbers only
Attention check: To confirm you’re reading the questions, please select “No” for this item.
What is your primary region/time zone?
What is your current seniority level?
- Individual contributor
- Manager
- Director
- VP/Executive
- Other
How long have you been with the company?
- Under 3 months
- 3–12 months
- 1–3 years
- 3–5 years
- 5+ years
Have you participated in prior launches of similar scope?
Team or org (optional):
Max 100 chars
Anything else that could change your recommendation in the next week?
Max 600 chars
AI Interview: 2 Follow-up Questions on launch readiness
AI InterviewLength: 2Personality: Expert InterviewerMode: Fast Thank you for your input—your responses will inform the go/no-go decision.