Project Background
Databricks is redesigning the first-run onboarding flow in Databricks SQL to help new analysts create their first query and dashboard faster. A UX/UI Designer has already shipped a high-fidelity prototype based on the hypothesis that a guided, step-by-step setup wizard would reduce confusion and improve activation. Initial moderated testing and product telemetry now show the opposite: users feel slowed down by the wizard, skip key steps, and are less likely to complete a first query than users in the current experience.
You are the designer responsible for pivoting the solution and driving execution with a cross-functional team of 8: 1 PM, 3 engineers, 1 data analyst, 1 UX researcher, 1 content designer, and you. The VP of Product wants a revised design direction ready for launch planning before the next quarterly release in 8 weeks because Databricks SQL activation is a top company KPI.
Key Stakeholders
- PM, Databricks SQL: wants a measurable activation lift this quarter
- Engineering Manager: wants to avoid major front-end rework and protect release stability
- UX Research Lead: wants additional validation before committing to a redesign
- Sales Enablement Lead: wants a polished demo flow for enterprise prospects at the upcoming field event
- Data Analyst: wants clean instrumentation and a clear success framework
Constraints
- Timeline: 8 weeks to production decision, 6 weeks to design/dev handoff
- Budget: $35,000 for research, prototyping, and content support
- Engineering capacity: 3 engineers, with only 1.5 frontend FTE available
- Dependency: telemetry instrumentation for the current flow is incomplete and needs 1 week to patch
- Release window: only one launch slot this quarter in Databricks SQL
Complications
- The PM has already socialized the wizard concept with leadership and is reluctant to reverse course.
- Research findings are directional but based on only 12 moderated sessions, while telemetry is missing one key drop-off event.
- Sales wants the more polished wizard retained for demos, even if it underperforms in real usage.
Your Task
- Define how you would reassess the problem and decide whether to pivot, iterate, or rollback the design direction.
- Create an execution plan for the next 8 weeks, including research, design, alignment, and launch readiness.
- Recommend the scope of the revised experience for this quarter versus what should be deferred.
- Specify success metrics, decision checkpoints, and a rollback plan if the new direction underperforms.
- Explain how you would align stakeholders with conflicting priorities while keeping the release on track.
