Blogs / Making Your Design Ops Accessible

Design · 4 min read

Making Your Design Ops Accessible

How an EISA Design Hub helped colleagues understand design’s contributions, navigate services, and find ways to work with us. Written by Fas Lebbie

At Meta, I saw a gap between the work our design team was doing and how easily colleagues could understand it or find a way to engage with us. Making our impact visible was part of the challenge.

Making design easier to work with was the more important task.

I initiated and led the EISA Design Hub, with contributions from my design team. EISA stood for Enterprise Infrastructure, Security, and Analytics: a technical organization where design supported complex internal products and the teams that relied on them.

The leadership thinking behind this work developed across earlier roles at Consumer Reports, Coral, and consulting engagements. The hub was an EISA-specific implementation, not a Meta-wide initiative.

Making design accessible meant helping colleagues find information, understand our contributions, and identify the right way to work with us.

Make your design strategy visible

The hub documented my Scalar Approach, which organized design’s work across three levels: Scale Up, influencing leadership and policy; Scale Wide, building cross-functional partnerships; and Scale Deep, strengthening team capability and culture.

Rather than leaving this thinking in team meetings, we explained what each level meant and how colleagues could engage with us.

Over time, I noticed partners using this language to discuss cross-functional alignment and leadership support. To me, that suggested our approach was becoming useful beyond the design team.

Make it comprehensive but scannable

Comprehensive documentation can be overwhelming. Our hub covered products, processes, research methods, design metrics, design reviews, and roadmap planning.

We made our information scannable with summaries, key personas, stakeholders, and core use cases. The aim was to help colleagues answer common questions without scheduling a meeting.

Documentation should make the next step easier to find, not simply demonstrate how much information a team has collected.

Offer multiple entry points

A VP cared about business impact. An engineer needed technical specifications. They shouldn’t have had to dig through the same content to find what mattered to them.

I organized the hub around four navigation paths:

  • Design Initiatives for strategic overviews.
  • Process for step-by-step workflows.
  • Documentation for detailed specifications.
  • Service Offerings for engagement models.

These paths connected strategy to the details of the work. Colleagues could start with their immediate question and follow the relevant links rather than needing to understand our entire operation first.

Spell out your value proposition

Our Service Offerings page distinguished lighter-touch UI support from integrated design and research, and more comprehensive involvement in product strategy and analytics.

This gave us a clearer basis for conversations about scope. Engineering managers and other partners could understand the support available, while we could discuss what an engagement required without overcommitting.

Sometimes a light-touch engagement was the right call. Other times, deeper involvement offered more value. Making those differences explicit helped move the conversation beyond whether design could take on a request toward what kind of involvement would be useful.

Show the humans behind the work

Our Team Accomplishments section featured photos, roles, and links to designers’ contributions. It helped colleagues see the people and capabilities behind the service.

We also documented learning initiatives such as Design Muscle sessions and Product Teardowns. These showed another part of our practice: developing our craft and sharing insights, not just executing requests.

Knowing who does the work can make approaching a team less abstract.

Connect your work to its consequences

We documented projects through the problems we addressed, our approach, and the outcomes we could substantiate, including product decisions and strategic direction.

Across my professional experience, I have noticed conversations change as colleagues gain a clearer understanding of design. Questions about what design does begin to give way to discussions about where its approach could help.

These moments inform my developing thinking about design currency. When colleagues understand design’s contribution and begin to seek its involvement, I see more than visibility: I see a changing relationship with the design function.

The practical lesson is to make the relationship between design’s work and its consequences understandable. Explain what changed, how design contributed, and what remains uncertain.

Remove barriers to working with you

Our hub included quick-access links for common requests, objectives connected to company goals, and clear touchpoints for involving design.

These details matter because understanding design’s value and knowing how to engage it are different problems.

A colleague may appreciate the work and still be unsure where to start.

Make that first step explicit. Show people where to go, what support is available, and how to begin a conversation about the right level of involvement.

Audit your design accessibility, then start small

Take a hard look at your current state:

  • Can colleagues understand your design strategy?
  • Can they find the right engagement pathway in a few minutes?
  • Are common questions easy to answer?
  • Are service levels and scope clear?
  • Can people understand the contributions behind the work?
  • Do they know whom to contact?

Then pick your most significant pain point: unclear services, confusing processes, or difficulty finding the right person. Start there. Use templates to maintain consistency as you expand.

Plan for upkeep, too. Give pages clear owners and review service descriptions, contacts, and links as responsibilities change.

The work is not finished when the documentation is complete. It matters when a colleague can find the right person, understand the support available, and join a conversation about what design could contribute.

Making design accessible means organizing the work so those encounters are easier to begin.