Validation Experiments
Prioritization is a hypothesis, not a conclusion. Juno proposes one validation experiment per recommendation to close its largest evidence gap. You choose which ones to run.
Confirm IdP + SCIM scope with 3 enterprise IT contacts
Hypothesis: Okta + Azure AD + Google cover ≥80% of blocked deals; SCIM deprovisioning is acceptable as v1.
Evidence gap it closes: IdP breakdown across the four blocked accounts.
Instrument first-session activation funnel
Hypothesis: ≥60% of new seats abandon before completing a starter task.
Evidence gap it closes: First-session funnel instrumentation.
Bisect 2.14 asset pipeline against 2.13 baseline
Hypothesis: Regression isolates to the asset pipeline change, not runner drift.
Evidence gap it closes: Whether the slowdown is uniform or concentrated on specific runner configurations.
5-interview validation with indie leads
Hypothesis: ≥3 of 5 indie leads share build reports externally today.
Evidence gap it closes: Whether other indie studios share build reports externally today.
Pull workspace-level notification mute rate
Hypothesis: ≥25% of paid workspaces have muted at least one notification channel.
Evidence gap it closes: Workspace-level notification mute rate.
Top-20 enterprise prospect survey on on-prem vs SaaS
Hypothesis: ≤20% of prospects treat on-prem as a hard requirement.
Evidence gap it closes: The share of blocked enterprise deals that cite on-prem rather than SSO.