Framework · DesignOps & capacity · 3 min read
Allocation patterns
Five ways to give a domain design support (dedicated, shared, pool/flex, enablement, tiger team), so you can match the pattern to each domain instead of spreading designers evenly.
One designer stays in the domain long-term and builds deep knowledge.
For: core, complex, high-change domainsOne designer covers two small domains. Never more than two.
For: low-volume domainsDesigners move to where the short-term work is.
For: short projects, peaks, auditsDesign system, guidelines and office hours. Developers build with the system.
For: domains without a designerDesigners from several domains join for one goal and an end date.
For: cross-domain initiativesUse it when
- You have more domains than designers and need to decide who gets what kind of support.
- A domain lead asks "why does that team have a designer and we don't?"
- A cross-domain initiative, such as a new navigation shell, needs people from several teams for a few months.
How to use it
- List every domain and its demand. Use your intake queue and capacity map to see how much design work each domain really has, and how complex and fast-changing it is. Output: one row per domain with volume, complexity and change rate.
- Give core, complex domains a dedicated designer. A designer who stays long-term builds the domain knowledge these domains need. Output: the list of dedicated domains.
- Share one designer across small domains, but cap it at 2. Low-volume domains can share a designer. More than two domains means constant context switching and shallow work. Output: shared pairs, never more than two domains per designer.
- Use enablement where there is no designer. Give these domains the design system, guidelines and regular office hours, so developers can build with the design system. Keep a pool/flex slot for short projects, peaks and audits. Output: enablement domains with office-hour times, and a flex slot in the capacity map.
- Form a tiger team for cross-domain initiatives. Bring designers from several domains together for a fixed period with one clear goal, then return them to their domains. Output: a tiger team with a goal, members and an end date.
- Review the patterns in the allocation review. Show domain leads which pattern each domain has and why, and revisit when demand changes. Output: an agreed allocation table, reviewed monthly or quarterly.
Worked example
An internal operations platform with 6 product teams and 4 designers, plus a design system.
| Domain | Situation | Pattern |
|---|---|---|
| Order management | Core, complex, changes every sprint | Dedicated (Designer 1) |
| Warehouse planning | Core, complex, many user roles | Dedicated (Designer 2) |
| Billing + Reporting | Two small domains, low volume | Shared (Designer 3, two domains only) |
| Admin settings | Mostly forms, few changes, no designer | Enablement: design system, guidelines, weekly office hours |
| Partner portal | Short redesign before a contract renewal | Pool / flex (Designer 4 for six weeks) |
| Navigation shell (all products) | Cross-domain initiative | Tiger team: Designers 1, 2 and 4 for one quarter |
The UX lead shows this table in the quarterly allocation review. The admin-settings lead accepts enablement because the reason is visible: low change, and the design system covers most of their screens.
Watch out for
- Sharing too widely. One designer across three or four domains becomes a ticket service with no depth. Cap shared support at two domains.
- Enablement without real support. "Use the design system" is not enablement. Without guidelines and office hours, those domains drift.
- Tiger teams that never end. Without an end date, the team becomes a hidden new domain and the home domains lose their designers.
- Silent choices. If domain leads don't know why they got a pattern, they will assume it is politics. Make the reasons part of the allocation review.
Template
Copy this into your capacity sheet and fill one block per domain.
Domain:
Demand (volume, complexity, change rate):
Pattern: Dedicated / Shared (max 2) / Pool-flex / Enablement / Tiger team
Who:
Why this pattern:
For enablement: office hours (when), guidelines (link)
For tiger team: goal, members, end date
Review on:
- Team TopologiesMatthew Skelton & Manuel PaisBook · 2019 (Amazon)
- An Elegant PuzzleWill LarsonBook · 2019 (Amazon)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.