Marcus Andrey Study
Ler em português Library

Framework · DesignOps & capacity · 2 min read

UX intake

One shared entry point for UX requests that captures the problem, users, impact, deadline and size, so all demand is visible and can be prioritised fairly.

1Domain

Which domain is asking.

e.g. Order management
2Problem

The user problem, not the solution they have in mind.

"What problem does this solve?"
3Users

Who is affected, how many, and how often.

e.g. 40 planners, daily
4Impact

The business or operational value of solving it.

e.g. fewer copy errors
5Deadline

The date, and why that date matters.

"What happens on that date?"
6Dependencies

Other teams, data or systems the work relies on.

e.g. reporting API
7Size

A rough estimate, enough to plan capacity.

S / M / L
Seven intake fields that turn every UX request into a problem you can compare and prioritise.

Use it when

  • Requests reach designers through chat, email and hallway conversations, and nobody sees the full demand.
  • Allocation follows whoever shouts loudest.
  • You want to prepare an allocation review and need comparable requests to score.

How to use it

  1. Create one entry point. One shared request form or board in your work-tracking or wiki tool. Tell all domains that this is the only way in. Output: a live intake form and board.
  2. Ask for the key fields. Requesting domain, problem (not solution), users affected, business impact, deadline and why, dependencies, and a size estimate (S/M/L). Output: a form with these seven fields.
  3. Check the problem and the deadline. When a request names a solution, ask "what problem does this solve, and for whom?" When it has a deadline, ask why that date matters. Output: requests that describe real problems and real deadlines.
  4. Make the queue visible to all domains. Everyone can see every request and its status. This is what makes trade-offs discussable. Output: a shared board with status per request.
  5. Feed it into scoring and the capacity map. Score new requests with your agreed criteria and bring them to the allocation review together with the capacity map. Output: a scored, ranked queue for the next review.

Worked example

An internal operations platform with 6 product teams. Before intake, a product manager writes in chat: "Can we get a new export button on the orders screen by Friday?" With the intake form, the request becomes:

Field Filled in
Requesting domain Order management
Problem Planners copy order data by hand into spreadsheets to share delays with customers.
Users affected About 40 planners, several times a day
Business impact Time lost, and copy errors in customer updates
Deadline and why End of quarter: a customer review meeting uses this data
Dependencies Reporting API from the data team
Size estimate M

The design work turns out to be a shareable delay view, not an export button. The Friday deadline disappears once the real date is known.

Watch out for

  • Side doors. If designers still take requests in chat, the form shows only part of the demand. Redirect politely every time: "Please add it to intake so we can weigh it."
  • Solutions in the problem field. Push back gently until the field describes a user problem.
  • A form that is too long. Every extra field lowers the number of people who use it. Keep to the core fields.
  • A hidden queue. If only UX can see the board, domains can't see why their request waits.

Template

Copy this into your request form or board template.

UX request
Requesting domain:
Problem (not the solution):
Users affected (who, how many, how often):
Business impact:
Deadline, and why that date:
Dependencies:
Size estimate:  S / M / L
Status: New / Scored / Planned / In progress / Done / Not now

Books to go deeper

"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