Databricks wants to redesign the permissions management experience in Unity Catalog to reduce admin errors and make governance setup easier for workspace admins and data platform teams. You are the UX/UI Designer embedded with a cross-functional team of 1 PM, 1 design lead, 5 engineers, 1 researcher, and 1 QA partner. Leadership wants the redesign included in the next quarterly release because customer feedback shows permissions setup is a top source of support tickets.
The PM wants to launch a meaningful improvement this quarter and is pushing for broad scope. Engineering wants designs that align with existing Databricks design patterns, frontend architecture, and accessibility standards to avoid rework. Security and governance stakeholders care most about preventing misconfiguration, while Customer Success wants a simpler experience for enterprise admins already using the current Unity Catalog flows.
You have 10 weeks until code freeze, a design support budget of $20,000 for research and prototyping, and no additional headcount. Engineering estimates they can support only 2 major workflow changes and 1 new component pattern this quarter. The redesign depends on a backend API update scheduled for Week 5, and the team must preserve compatibility with existing account-level and workspace-level permission models.