Google

Product & engineering excellence

An ongoing workstream with front-end engineering to improve usability, accessibility and code health on an internal data security platform.

Problem
The data security platform I was lead on had grown quickly. Features had picked up their own interaction patterns, older components were piling up, and accessibility requirements and the design system kept moving.
My role
Co-led an ongoing workstream with Alexandra (Rexi) Sheredy, the front-end engineer I partnered with most often.
Key decisions
  • Ran UX and accessibility improvements as ongoing work with one central, prioritized list.
  • Shared detailed specs broadly for feedback before implementation.
  • Designed one set of filter components to replace the patterns that had grown across the product.
Outcomes
Unified filter components, a migrated role filter bar, accessibility reviews against company standards, and moving the product from Material 2 to Material 3.

Context

Lead Product Designer · 2023–2025

Services: UX/accessibility · Engineering collaboration · Design systems · Material 3 migration · Component design

This work was on an internal tool, so every screen on this page is a reconstruction with placeholder data. The patterns are real; the names and layout details are not.

data-access-tool / roles

Before: three pages, three filter patterns

RolesTeam ▾Status ▾
PoliciesType to filter…✓ Active only
RequestsMineAllAdvanced search

After: one filter bar everywhere

☰TeamStatusOwner+ Add filterClear filters
Filtering before and after the unified filter components. Reconstructed with placeholder data.

The problem

Internal tools tend to evolve fast. Over time, different sections of this platform had picked up their own ways of doing the same thing, which made the product feel fragmented and asked more of the people using it.

The same speed left behind older code and components that no longer matched the current design system, which slowed development and made maintenance harder. Accessibility requirements and design guidelines kept changing too, so staying current took ongoing attention. And because so many people relied on the platform, every change had to be rolled out carefully.

Engineering time was limited, so UX improvements and technical debt had to be planned alongside new features.

How we worked

Alexandra (Rexi) Sheredy, the front-end engineer I partnered with most often, and I set this up as an ongoing workstream rather than a project with an end date.

  • We met regularly to find pain points, accessibility gaps and chances to improve the experience, and logged every improvement in one shared, prioritized list so the wider team could see it.
  • For bigger changes, we used existing research or ran new sessions, looked at how people were using the feature, and defined the problem and goals before designing.
  • I explored several options for each change and iterated with feedback from engineering and stakeholders.
  • I wrote detailed specs and shared them broadly for feedback before implementation.
  • During builds, Rexi and I worked through issues together as they came up instead of waiting for a formal review.
  • We checked changes against the company's accessibility standards.

What changed

  • Filter audit: I listed every page where the data ownership filter appeared, eight in all, and two more where it was missing but probably belonged.
  • Unified filters: I designed one set of filter components to bring filtering together across the product, which made it more usable and predictable and reduced confusion for the developers using the tool.
  • Multi-select with search: I designed a filter that lets people search within its options and select several, showing each option's path. Research supported this approach.
  • Filter chip rules: I wrote rules for how chips handle long labels, so they behave the same on every page.
  • Role filter bar migration: I led moving the role filters from their own header to the shared filter bar used on the product's list pages, which made them more intuitive and consistent with the rest of the product. All filters showed at once instead of sitting behind a button, and filter options stopped changing based on the current search results.
  • Search bar: as part of that migration, I designed a new search bar with a scope selector, auto-suggest, recent searches, advanced search and a zero-results state, with variations for each type of page.
  • Accessibility and design system: I led accessibility reviews to find and close gaps for people using assistive technology, and redesigned components and interaction patterns as part of the move from Material 2 to Material 3, which also reduced technical debt.
data-access-tool / specs / filter chips

Filter chip labels

Always shorten long labels instead of wrapping them.

Up to 25 characters

Show the full label.

Field operations

Longer label, one selection

Shorten in the middle.

Regional sa...orting team

Longer label, several selections

Shorten before the count, and always keep the count.

Regional sales repor...+3

Two-digit count

Give up one more character for the count.

Regional sales repo...+12
Rules for shortening long filter chip labels. Reconstructed with placeholder data.
data-access-tool / roles
HomeMy accessApprovalsRolesPolicies
Roles ▾Sales|×

Recent

↺ Sales targets

Roles

Regional sales reporting

Finance → Sales → Reporting

Sales forecasts

Finance → Sales → Planning

Sales data analyst

Operations → Field → Analytics

TeamStatusPolicy notesAdvanced search
The search bar with a scope selector, recent searches and auto-suggest. Reconstructed with placeholder data.

Next

The next step was to formalize the workstream with a short brief and add metrics to each launch, so the team could track the effect of this work.