Dataford
Interview Guides
Upgrade
All questions/Execution/Redesign Databricks Workspace Navigation

Redesign Databricks Workspace Navigation

Easy
Execution
Asked at 1 company1RoadmappingTrade-offsScope Management
Also asked at
Databricks

Problem

Project Background

Databricks wants to redesign core navigation across the Databricks Workspace to make it easier for data engineers, analysts, and ML practitioners to move between Catalog Explorer, SQL Editor, Jobs & Pipelines, notebooks, and dashboards. You are the UX/UI Designer leading execution for the design workstream on a high-visibility platform initiative with 1 product manager, 6 engineers, 1 user researcher, and executive review from the VP of Product. Leadership wants a launch-ready design direction in 12 weeks so engineering can begin implementation next quarter.

Key Stakeholders

The PM wants a clear MVP that improves discoverability and reduces navigation friction without delaying roadmap commitments. Engineering wants to minimize front-end rework because the team is already committed to a Unity Catalog permissions update and a Databricks SQL performance release. Leadership wants a cohesive platform direction that can scale across multiple surfaces, while Customer Success is pushing for quick wins for enterprise users who report confusion switching between products.

Constraints

You have a design research and prototyping budget of $45,000, no additional headcount, and 12 weeks to deliver an approved plan. Engineering can support only 2 major navigation changes and 3 minor UI updates in the first release. The redesign must work across desktop web first, with mobile deferred. It must not break existing workflows for top enterprise accounts, and any launch must align with the quarterly release train in Week 14.

Complications

  1. The Unity Catalog team needs shared navigation patterns finalized by Week 6 to avoid blocking their own release.
  2. Leadership is split: one executive wants a bold platform-wide redesign, while another wants a low-risk incremental update.
  3. Early research shows power users and new users want conflicting navigation models.

Your Task

  1. Build a 12-week execution plan from discovery through launch readiness.
  2. Define how you will align PM, engineering, and leadership on scope and trade-offs.
  3. Recommend an MVP versus later-phase roadmap for the navigation redesign.
  4. Identify the top risks, dependencies, and mitigation steps.
  5. Define success metrics and a launch readiness plan for the first release.

Problem

Project Background

Databricks wants to redesign core navigation across the Databricks Workspace to make it easier for data engineers, analysts, and ML practitioners to move between Catalog Explorer, SQL Editor, Jobs & Pipelines, notebooks, and dashboards. You are the UX/UI Designer leading execution for the design workstream on a high-visibility platform initiative with 1 product manager, 6 engineers, 1 user researcher, and executive review from the VP of Product. Leadership wants a launch-ready design direction in 12 weeks so engineering can begin implementation next quarter.

Key Stakeholders

The PM wants a clear MVP that improves discoverability and reduces navigation friction without delaying roadmap commitments. Engineering wants to minimize front-end rework because the team is already committed to a Unity Catalog permissions update and a Databricks SQL performance release. Leadership wants a cohesive platform direction that can scale across multiple surfaces, while Customer Success is pushing for quick wins for enterprise users who report confusion switching between products.

Constraints

You have a design research and prototyping budget of $45,000, no additional headcount, and 12 weeks to deliver an approved plan. Engineering can support only 2 major navigation changes and 3 minor UI updates in the first release. The redesign must work across desktop web first, with mobile deferred. It must not break existing workflows for top enterprise accounts, and any launch must align with the quarterly release train in Week 14.

Complications

  1. The Unity Catalog team needs shared navigation patterns finalized by Week 6 to avoid blocking their own release.
  2. Leadership is split: one executive wants a bold platform-wide redesign, while another wants a low-risk incremental update.
  3. Early research shows power users and new users want conflicting navigation models.

Your Task

  1. Build a 12-week execution plan from discovery through launch readiness.
  2. Define how you will align PM, engineering, and leadership on scope and trade-offs.
  3. Recommend an MVP versus later-phase roadmap for the navigation redesign.
  4. Identify the top risks, dependencies, and mitigation steps.
  5. Define success metrics and a launch readiness plan for the first release.
Your answer
Try one AI text evaluation on us
Get structured feedback, scored against a 4-axis rubric. Premium unlocks unlimited.
0 wordstarget ~200
Up next
DatabricksRedesign Databricks Workspace NavigationEasyDatabricksRedesign Databricks Onboarding FlowEasyDatabricksResolve Notebook Navigation Launch ConflictEasy
Next question