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 with a sufficiently detailed brief, not through scattered emails or verbal requests. The order of priority is determined by both parties based on clear criteria: business value, real deadlines, effort, and risk. No one argues louder than anyone else; only the criteria speak.
- the large volume, many people place orders together
- begin with disputes over order between departments
- A small team still needs a standard brief template.
- accepting work from all directions without a standard brief
- prioritize according to the loudest voice
Are you managing a design team or working with an external studio, and the most practical question is not "what to do" but: where to send requests, who receives them, and who decides what to prioritize. Most of the chaos in daily brand operations stems from these two areas being overlooked.
Why a reception point is 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 must go through exactly one channel, accompanied by a standardized intake form. Any request that takes shortcuts will not be prioritized, with no exceptions. This rule may sound strict, but it actually protects both sides: clients do not lose their requests, and the team does not work with unclear information.
Do not start production before the brief is complete and agreed upon.
Atlassian, Adobe, Sinh Vũ practical experience.
A minimal brief should include: the objective of the request, the target audience, the main message, output specifications (size, format, platform), and a real deadline. Missing any item means the team has to guess, significantly increasing the chances of needing to redo.
Who decides the order and based on what criteria?
Prioritizing based on the loudest voice is the quickest way for everything to become "urgent." Without clear criteria, everyone has a reasonable justification to prioritize their own needs, and the design team finds it hard to refuse anyone.
The practical criteria scale that Sinh Vũ applies includes 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.
List of tasks without a cap means every period will exceed the plan. Each month or sprint (short work cycle, usually two to four weeks) needs a defined number of available hours. When the total effort of the list exceeds that hour budget, there are two options: postpone the tasks to the next period or separate them into a standalone project outside the package.
Separate projects: suitable when the need is truly urgent and cannot be postponed. Add resources, clearly commit to the scope and new deadlines. Do not combine it into last month's package for 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.
- With an incomplete brief, the team has to guess the intent, create, wait for feedback, and redo. An initial attempt to save time can end up costing double at 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 is not known how many rounds of revisions are enough, nor what format of file delivery constitutes completion.
The viewpoint of Sinh Vũ
Sinh Vũ operates on a monthly cycle with a single intake channel. Clients place requests through that channel, accompanied by a standard brief. At the beginning of each cycle, both parties sit down to finalize the order based on value and deadlines, not on who emailed first. The team only begins work when the brief is complete and the order has been confirmed.
The hourly retainer has a clear cap. Exceeding the cap is communicated early, not discovered at the end of the period. This approach ensures that the deliverables remain on standard and on time, and both parties are aware of their status.
If you feel that the design team is always busy but important tasks are not getting done, it’s likely that the issue lies not in capability but in a lack of control over input.
Decision checklist
Topic: Which channel to assign tasks through and who decides the priority order in the backlog. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, 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 there and include a standard brief. Complex tools are only useful when many people are placing orders 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 you accept the job and ask questions later?
You should not. Taking on work when the brief is insufficient is the source of most time-consuming revisions. Sinh Vũ adheres to the principle that production only begins when the brief is complete and agreed upon by both parties. Spending an additional session refining the brief can save many days of rework later.