DESIGN OPS › COMMUNITY LEADERSHIP
Building infrastructure for the designers who stay invisible
DESIGN OPS › COMMUNITY LEADERSHIP
Building infrastructure for the designers who stay invisible
The Internal UX Guild was a cross-team initiative I founded to solve a problem nobody had officially named: designers building Indeed's internal tools were operating in silos, quietly reinventing the same solutions.
Role
Lead Facilitator · Head of Guild
Timeline
November 2023 — May 2024
Scope
Cross-functional · Design Ops · Systems
Outputs
Component Audit · Figma Library · Design Standards
CONTEXT
The problem hiding in plain sight
Internal tools at Indeed are dense, data-heavy, and chronically under-resourced relative to consumer-facing products. As a designer working on internal platforms, I kept running into the same friction: components from the Indeed Design System needed constant adaptation to fit the real constraints of internal workflows; and I wasn't the only one doing it.
The workarounds were happening in isolation. Designers across teams were making the same adjustments, reaching out to each other in DMs to share rationale and patterns, and then going back to working alone. There was no shared library, no standards document, no place to put any of it.
That framing mattered. Internal tool designers contribute just as directly to Indeed's mission, they just do it from a less visible position. That invisibility was part of the problem I wanted to fix.
FRAMIING
How might we create shared standards without just duplicating the design system?
The IDS wasn't the problem. The problem was the gap between what IDS provided and what internal tools actually needed: dense tables, complex state management, data-heavy layouts with tight constraints. We needed a layer built specifically for that context, documented and shared, so designers weren't solving the same problems on repeat.
7+
hours in the component audit, reviewing internal tools against IDS
4
structured phases from insight gathering to design system partnership
6 mo.
from inception to launch
1
Figma library built from scratch, with documented components
PROCESS
Four phases, one community
I structured the guild's work in overlapping phases, each one building on what we learned in the last.
ARTIFACTS
From scattered DMs to documented standards
The audit and library gave the guild its tangible output: a shared foundation that could outlast any individual contributor's memory.
IMPACT
What it built, and what it left behind
The guild created something that hadn't existed before: a structured community where internal tool designers could stop solving problems alone. The Figma library reduced duplicated component work across teams. The audit gave the design systems team concrete data on where IDS fell short for internal contexts. And the ambassador program (while not fully launched before the org restructured) established a blueprint that could be picked up again.
The initiative ended earlier than intended due to layoffs and organizational restructuring. That context matters. But the standards we set, the library we built, and the precedent we created for cross-team design collaboration didn't disappear with the headcount.
REFLECTION
What I learned
THE CENTRAL SHIFT
Structured collaboration can create real change faster than individual advocacy. When designers stop solving the same problems separately and start building toward a shared foundation, the gains compound quickly.
BIGGEST WIN
Creating a community where internal tool designers felt seen and supported, and proving that even a short-term collaborative effort can leave a lasting mark on how a team thinks about design standards.
WHAT I'D DO NEXT
A formal ambassador program embedded in each internal tool team, with dedicated partnerships with experience quality functions, so the standards we built would have a structural home rather than depending on individual initiative.