TABLEAU CLOUD
ADMIN SETTINGS
Company: Tableau
Project: Redesign Admin settings in Tableau Cloud
Role: Lead UX Designer
​
The Problem: Architectural Debt and Scaling Blockade
The Admin Console was suffering from severe architectural debt, operating as a feature graveyard that blocked future velocity. The settings area was cumbersome and confusing because there was no unified Information Architecture (IA). This resulted in every new setting being a high-friction decision, eroding the admin experience, and forcing teams to simply append new controls to a long, unmanageable list. The lack of an established IA model was blocking the platform's ability to scale new feature controls efficiently.
Admin settings before the redesign and new IA put in place - partial view of a very long list.
The How: Establishing Foundational Information Architecture
I led a high-leverage, cross-functional partnership (Design, PM, CX, Research) to define the Foundational Information Architecture (IA) for the entire Admin experience. This began by creating the core principles that would guide the platform's future.
​
Utilizing a card sorting session, we systematically organized the existing 55+ settings from chaos into a durable, scalable taxonomy. This process was not just about grouping; it was about establishing the system's architecture. We defined 8 clearly defined main categories with 4-8 subcategories, creating the fundamental IA model that now governs all configuration within the Admin experience and prevents future architectural debt.
Establishing the new IA for settings was multi-step - this shows some of the card sort process.
Showing the before and after IA diagrams and a much improved settings architecture.
Showing quick filter options for the settings search as a setting-specific filter paradigm.
Search as an Architectural Necessity:
Following the establishment of the foundational Information Architecture (the 8 categories), I rapidly translated the strategy into high-efficiency concepts. Through iterative design and competitive analysis, two major improvements emerged that enabled the platform to scale:
​
-
Search as an Architectural Necessity: With over 55 settings, fast retrieval was paramount. Instead of a site-wide search, I defined a settings-specific filter paradigm. This design decision was an architectural choice that validated the new IA and provided the fastest path for administrators to find and act on controls.
​ -
Dynamic State Management: The introduction of toggle switches was a key technical and UX win. This system changed the platform's fundamental behavior by making changes to settings dynamic and immediate. This efficiency gain dramatically improved the administrative workflow and set a new standard for platform responsiveness.
Search functionality allowing for specific letter/word searches within settings.
The Solution: Unlocking Platform Efficiency
The final design was driven entirely by the new, scalable IA model. The new UX paradigm accelerated the user experience and provided a clean visual update aligned with brand guidelines.
Crucially, the introduction of dynamic toggle switches and optimized, settings-specific search filtering directly translates the new architecture into a high-efficiency user experience. This systemic design choice empowered admins to quickly govern the platform, unlocked an immediate operational efficiency gain, and simplified the path for every new setting that the platform will implement in the future.
Final site settings design - re architected
Final site settings showing multi-option settings