A job order, a person who confirms the sequence
All delays or issues begin with requests going off track or no one having the authority to prioritize tasks.
All requests must go through exactly one standardized channel, accompanied by a complete brief. Do not send requests via scattered emails or verbally. The order of priority is agreed upon by both parties, based on clear criteria: business value, real deadlines, effort, and risk. No one gets prioritized for being louder; only the criteria will determine.
- the large volume, many people place orders together
- begin with disputes over order between departments
- A small team still needs a standard brief.
- Accepting work from all directions without a standard brief.
- prioritize according to the loudest voice
You are managing a design team or working with an external studio. The most practical question is where to send requests, who receives them, and who decides which tasks to prioritize. Most of the chaos in daily brand operations stems from these two areas being left open.
Why is a reception point more important than you think?
When requests come from multiple directions, email, personal messages, word of mouth in meetings, no one has the complete picture to schedule correctly. The fall-throughs are not due to a lazy team, but because no one is sure if that task is on the list.
Basic principle: all requests should go through exactly one channel, accompanied by a standardized intake form. Any request that takes shortcuts will not be prioritized. This rule may sound strict, but it actually protects both sides: the requester does not lose track of their requests, and the team does not work with unclear information.
Do not start production until the brief is complete and agreed upon.
Atlassian, Adobe, practical experience
A minimum viable brief should include: the objective of the request, the target audience, the main message, output specifications (size, format, platform), and the real deadline. Missing any of these elements forces the team to guess, significantly increasing the likelihood of rework.
Who decides the order and based on what criteria?
Prioritizing based on who shouts the loudest is the quickest way to make everything "urgent." Without clear criteria, anyone placing a request has a reasonable justification to demand priority. The design team finds itself in a position where it cannot refuse anyone.
A practical criteria scale consists of four factors:
- Business value: does this directly impact revenue, product launches, or commitments to partners?
- Real deadline: A deadline imposed externally (events, campaigns with fixed schedules) or an internal deadline that can be flexible?
- Necessary effort: how many hours will it take, and will it require coordination with many people?
- Backward risk: What are the consequences of delaying by a week?
Score all four factors for each task, prioritize them, and have an authorized person make the final decision on the list. That person must be clearly designated from the start, avoiding two departments negotiating with each other or directly pressuring the execution team.
Hourly cap and exceeding the cap.
An unbounded task list will inevitably disrupt plans. Each month or short work cycle (sprint, usually two to four weeks) needs to have a defined number of available hours. When the total effort of the list exceeds that hour budget, there are two options: push tasks to the next cycle or separate them into a standalone project outside the cycle.
Separate project: suitable when the task is truly urgent and cannot be postponed. Add resources, clearly define the scope and new deadlines. Do not lump it into the ongoing cycle and expect the team to take on more without additional time.
Common errors in practice
- Accepting work from all directions without a standard template leads to falling behind and being unable to trace back.
- The brief is incomplete, the team has to guess the intent, then wait for feedback and redo. An initial round that seems to save time ends up costing more in the end.
- Prioritize based on who speaks the loudest rather than by criteria, causing important tasks to be overshadowed by urgent but unimportant ones.
- No one is responsible for finalizing the list, so everything is "urgent" and the team has no basis to refuse or postpone tasks.
- The definition of "done" is unclear: it's not known how many rounds of revisions are enough, or what format the deliverable should be in to be considered complete.
If you feel that your design team is always busy, yet important tasks remain unfinished, the issue likely does not lie with capability. The problem is that no one is controlling the input.
Decision checklist
Topic: Where to place requests and who decides the order of priority in the backlog. Sinh Vũ's guide, sinhvu.com
Tick each item that applies or that you can already answer, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Asana, How to Manage Creative Requests; Workamajig, The Project Intake Process Explained; Adobe, Project Prioritization Best Practices; Atlassian, Product Backlog, Scrum Guide; Sinh Vũ, O1 operational service documentation.
Frequently asked questions
If the team is small, is a dedicated project management tool necessary?
Not necessarily. A shared spreadsheet or a dedicated chat channel is sufficient, as long as all requests go through that and include a standardized brief. Complex tools are only useful when many people are placing requests and the volume is large enough to require automated tracking.
When two departments urgently discuss their own matters, how do you resolve it?
This is why a scoring criteria ladder is needed, not to make subjective judgments. Both tasks should be scored according to the same criteria: business value, real deadlines, and effort expended. Higher scores take precedence. If scores are still tied, the designated authority makes the final decision, rather than allowing both departments to negotiate with the design team.
If the brief lacks information, can we accept the work first and ask questions later?
You shouldn't. Accepting work when the brief is incomplete is the source of most time-consuming revision cycles. The safe principle is to only start production when the brief is complete and both sides have agreed. Spending an extra session refining the input brief saves many days of rework later on.
This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.