Framework · DesignOps & capacity · 3 min read
DesignOps three layers
NN/g's way of grouping DesignOps into how we work together, how we get our work done, and how our work creates impact, so you can find the real gaps and fix them with minimum viable standards.
How we work together: team structure, roles, collaboration, rituals.
e.g. cross-domain critiqueHow we get work done: process, tools, workflow, quality, research ops.
e.g. intake board, Definition of DoneHow our work creates impact: measurement, communication, influence, maturity.
e.g. monthly UX updateEvidence of real problems → minimum viable standards → measure DesignOps itself
Use it when
- You are asked to "build a stronger central UX practice" and need to know where to start.
- Designers complain about friction (unclear requests, slow handoff, no shared patterns) and you want to sort the complaints.
- You have to explain to your manager what DesignOps is and what it will cost and deliver.
How to use it
- Collect evidence of the real problems. Ask designers, product managers and developers where work gets stuck. Look at intake, handoff questions and rework. Output: a list of concrete problems, each with an example.
- Sort each problem into a layer. How we work together (structure, roles, collaboration, rituals). How we get our work done (process, tools, workflow, quality, research ops). How our work creates impact (measurement, communication, influence, maturity). Output: problems grouped under the three layers.
- Pick the few that hurt most. Choose 2–3 problems with the biggest cost, across layers if possible. Output: a short, prioritised list.
- Fix each with a minimum viable standard. One shared intake board, a monthly capacity map, a Definition of Done, a bi-weekly cross-domain critique. Small, owned and with a reason. Output: one standard per problem, each with an owner.
- Measure DesignOps itself. Decide how you will know the standard helped (fewer handoff questions, faster intake, team health) and check it after a few months. NN/g's REACH framework gives a structure for this. Output: one measure per standard and a review date.
Worked example
An internal operations platform with 6 product teams and no DesignOps role. The UX lead runs short interviews and sorts what she hears.
| Layer | Evidence | Minimum viable standard |
|---|---|---|
| How we work together | Designers in different domains never see each other's work; duplicate patterns appear. | Bi-weekly cross-domain critique; monthly show and tell. |
| How we get our work done | Requests arrive in chat, email and meetings; nobody sees the full queue. Developers return with missing states. | One shared intake board; a Definition of Done for design. |
| How our work creates impact | Stakeholders don't know what UX delivered last quarter. | A half-page monthly UX update. |
She starts with intake and the Definition of Done, because they cause the most rework, and checks after three months whether handoff questions went down.
Watch out for
- Process before problems. Rolling out standards before you understand the teams makes you the "process zealot". Listen first.
- Only the middle layer. Tools and templates are the easy part. Collaboration and impact problems often matter more.
- Too many standards at once. Each new standard costs attention. Start with the minimum and add only when there is evidence.
- Not measuring it. DesignOps that can't show its own effect is the first thing cut when budgets get tight.
Template
Copy this into a doc and fill it after your first interviews.
Layer 1: How we work together
Problem + evidence:
Minimum standard: Owner: Measure:
Layer 2: How we get our work done
Problem + evidence:
Minimum standard: Owner: Measure:
Layer 3: How our work creates impact
Problem + evidence:
Minimum standard: Owner: Measure:
Start with (top 2-3):
Review on:
- Org Design for Design OrgsPeter Merholz & Kristin SkinnerBook · 2016 (Amazon)
- DesignOps HandbookBattles, Black, Malouf & Whitehead (DesignBetter)Book · 2018 (Amazon)
- Thinking in SystemsDonella H. MeadowsBook · 2008 (Amazon)
- DesignOps 101NN/g (external site)
- 3 Steps for Getting Started with DesignOpsNN/g (external site)
- Measuring DesignOps with the REACH FrameworkNN/g (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.