WORK / 03
Role
Information architecture, navigation models, label systems, stakeholder facilitation, usability review, and confidential product-structure decisions.
Problem
Important settings were hard to locate because the structure reflected internal ownership and system logic more than how admins understood the tasks they needed to complete.
Approach
I facilitated a clearer IA model around user intent, common jobs, language patterns, permission complexity, and the decisions admins needed to make safely.
Outcome
The revised structure made routine admin work easier to explain, find, support, and hand off across product, engineering, and customer-facing teams.
Enterprise UX judgment
Reframed complex admin spaces around user intent instead of organizational seams.
This page intentionally omits visuals because the work is confidential. The recruiter signal is senior IA judgment: naming ambiguity, resolving ownership tension, aligning stakeholders, and turning system complexity into a more usable product structure.
Moved conversations from feature ownership toward the tasks admins were trying to complete.
Created a shared language for groups, labels, hierarchy, and settings relationships.
Balanced findability, governance, product constraints, and implementation effort.
How the confidential work is represented
01 Inventory complexity
Audited settings, labels, permissions, and support questions to identify where the structure created confusion.
02 Model intent
Grouped information around what people needed to do, not how the organization or backend described it.
03 Build agreement
Pressure-tested the model with product, support, and engineering so the structure could survive real delivery constraints.
Information architecture
Stakeholder facilitation
Enterprise systems thinking