How_to_request_design_work
Send people here instead of answering the same direct message every week. A request that arrives with these six answers can be started; one that does not is a conversation, not a request.
Copy this into a new task
What is it. The deliverable, in one line. "Instagram carousel, 5 slides" beats "something for the launch".
Where does it appear. The actual surface and size. A banner for the site, an app icon at 32px and a 2-metre booth panel are three different jobs.
Who is it for. The audience, not the internal stakeholder.
When do you need it, and why that date. The reason matters more than the date. "Printer cutoff is 16 Jul" is a deadline. "ASAP" is a preference wearing a deadline's clothes.
Who signs it off. One name. Not a team, not a channel.
What already exists. Links to the brief, the copy, the previous version. Every missing input becomes a question later, and questions are what turn three days into two weeks.
What happens next
- The request lands in Intake: not triaged at status Requested.
- It gets a requester, a real date reason and a round number, then either a slot or a no. Saying no here is cheaper for everyone than saying it in round three.
- Work moves through In Design, then Internal Review, which exists so the reviewer's round one is not spent on things the team could have caught.
- Then it goes for approval and appears in Waiting on a decision until somebody decides.
Two rules that keep this honest
Feedback names the change, not the feeling. "Not feeling it" is not a revision request; "the badge sits outside the card at 375px" is. A reviewer who cannot name the change is not ready to review.
Rounds are counted. The Review round field is on every request. Round one is normal, round two is fine, round three means something was wrong with the brief rather than the work, and that is worth fixing upstream instead of drawing it again.