Marcus Andrey Study
Ler em português Library

Framework · DesignOps & capacity · 2 min read

Capacity map

A monthly view of who works on what at what percentage, with a 15–20% buffer kept free, so stakeholders can see design supply and the trade-offs behind it.

1Designers

One row per designer, with level. Each row adds up to 100%.

e.g. Designer 1 (Senior)
2Domains

One column per domain. The percentage each designer really spends there.

e.g. Orders 60%
3Practice

Design system and practice work, planned like any domain.

e.g. DS / Practice 20%
4Buffer

Unallocated time for urgencies, practice and learning. Explain it up front.

Keep about 15–20%

Domains + practice + buffer = 100% per designer, reviewed monthly

A capacity map shows where each designer's time goes this month, including a protected buffer.

Use it when

  • Several domains ask for the same designer next month and you need to show what is already committed.
  • Stakeholders say UX capacity and allocation are not transparent.
  • You prepare a monthly or quarterly allocation review with domain leads.

How to use it

  1. Set up the grid. Rows are designers (with level), columns are domains plus a design system / practice column and an "Available" column. Output: an empty map in a shared sheet.
  2. Fill in real allocation as percentages. Write what each designer actually works on this month, not what the org chart says. Each row adds up to 100%. Output: a filled map for the current month.
  3. Keep the buffer free. Leave about 15–20% of each designer unallocated for urgencies, practice work and learning. If a row has no buffer, the next urgency will push out planned work. Output: a buffer visible in every row.
  4. Mark the gaps. Note which domains have no designer and which requests in the intake queue have no capacity. Output: a short list of unmet demand.
  5. Review it monthly with domain leads. Show demand against supply, recommend a change if needed, and let them see the trade-off. Explain the buffer explicitly. Output: an agreed map for next month and any decisions on what stops or waits.

Worked example

An internal operations platform with 6 product teams. The UX lead shares this map in the monthly allocation review.

Designer Orders Planning Billing DS / Practice Available
Designer 1 (Senior) 60% 20% 20%
Designer 2 (Mid) 80% 20%
Designer 3 (Junior) 70% 10% 20%

Unmet demand: the reporting domain has a request with no designer. The lead says: "We can start reporting in two weeks, or now if we pause the billing redesign. Which matters more to you?" The domain leads choose to wait two weeks. The buffer stays intact.

Watch out for

  • Treating the buffer as free capacity. Every stakeholder will see 20% "available". Name what it is for and protect it.
  • Planned instead of real numbers. A map that shows the intended split while people work elsewhere destroys trust. Update it from what is actually happening.
  • Using it to judge individuals. The map shows where capacity goes, not how productive someone is.
  • Making the trade-offs privately. If you rearrange the map alone, stakeholders never see the trade-off. Decide changes in the review.

Template

Copy this into a shared sheet and update it each month.

Capacity map, month: ________

Designer (level)   Domain A  Domain B  Domain C  DS/Practice  Available (15-20%)
Designer 1
Designer 2
Designer 3
(each row = 100%)

Domains without a designer:
Requests with no capacity:
Trade-off to decide in the review:
Decided:

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close