Pilot readiness · end-to-end validation
Pilot workspace
Everything a first Roblox studio needs to go from connection to a defensible product decision without analyst support.
Pilot checklist
First-value path
1
Connect experience
Use a read-only Roblox analytics key and universe ID.
2
Validate data
Confirm the sync returns observations or a clear empty-data state.
3
Review priorities
Open the top evidence-backed decision and inspect the supporting signal.
4
Build experiment
Generate a KPI, guardrail and decision rule from the supported finding.
5
Weekly review
Use the brief to review changes, experiment status and next focus.
Pilot success criteria
What must work without us
✓ Studio can connect with read-only access
✓ Empty and error states explain the next action
✓ Top priority links to evidence, not a black-box score
✓ Experiment proposal contains KPI + guardrails
✓ Weekly brief closes the loop
Pilot feedback loop
After each decision, capture usefulness from 1–5 plus one short note. Feedback is categorized by onboarding, priority, analyst, experiment or weekly brief so pilot learning maps directly to product work.
Connection-state UX
No dead ends.
DisconnectedNo credentials
Connect a least-privilege analytics key before analysis starts.
Connected · no dataValid connection
Explain that analytics are not available yet and offer retry/demo paths.
ReadyObservations available
Surface priorities, evidence and experiments without extra setup.
DegradedSync needs attention
Keep previous evidence visible and give a precise recovery action.