How agencies should prioritise when everything feels urgent
When every client request feels urgent, the answer is not a longer list. It is a shared rule for what gets attention, what waits and what gets refused.

Every client thinks their request is the priority. The team cannot do all of them at once, and pretending otherwise is how a good agency quietly becomes an unreliable one.
Small agencies can hit genuine capacity limits. But overload also becomes chronic when everything is allowed to compete equally for the same people. The practical response is to make trade-offs explicit. Use four questions every week: what needs attention now, what can wait, what should be refused, and what rule decides when several things are genuinely urgent.
Capacity is not always the first problem
When a small agency feels overwhelmed, the instinct is usually to look for more hours, more tools or a faster process. Sometimes that is exactly what is needed. But adding capacity does not solve a system in which every request is allowed to become a priority.
Derek Lidow’s Harvard Business Review discussion of strategic priorities makes the central leadership point: setting priorities means identifying trade-offs and deciding what not to do, not simply ranking everything that could be done.
That discipline matters in an agency because saying yes is deceptively easy. It feels responsive until delivery quality slips, deadlines move and the team absorbs the difference through overtime.
Why ranking everything is not enough
The default response to overload is to build a longer list and rank it. In practice, ranking often collapses as soon as a new client email arrives or a stakeholder escalates. The problem is not the list. It is that nothing has been protected from interruption.
A useful evidence base comes from research on resource-constrained firms. Symeonidou, Leiponen, Autio and Bruneel used longitudinal data from the Kauffman Firm Survey to examine how new ventures allocate scarce resources to functional capabilities. Their analysis covered 2,356 start-ups across 6,748 firm-year observations, with follow-up survey response rates of at least 82%. The firms were not agencies, so the study should not be treated as agency-specific evidence. What it does show is that, under resource constraints, focused capability development was more conducive to sales growth than trying to develop several capabilities simultaneously, with greater founder experience and access to finance reducing the penalty from breadth.
A separate Organization Science study by Cao, Gedajlovic and Zhang examined 122 high-tech firms. It found that actively balancing competing exploration and exploitation demands was more beneficial in resource-constrained firms, while pursuing high levels of both at the same time was more beneficial when firms had greater access to resources. Again, this is not an agency study. The useful strategic principle is narrower: the amount of parallel ambition a business can sustain depends on the resources available to support it.
Reactive prioritisation versus deliberate prioritisation
| Reactive prioritisation | Deliberate prioritisation |
|---|---|
| Whoever asks most recently gets attention | A small number of priorities are agreed in advance |
| Everything is technically “in progress” | Some things are explicitly delayed, on record |
| No client hears “not now” | Clients are told clearly what is and is not happening this week |
| The team absorbs the cost through overtime | The business absorbs the cost through a visible trade-off |
| Priorities live in someone’s head | Priorities are written down and shared |
The right-hand column is not about doing less work. It is about making the trade-offs visible instead of invisible, so they can be managed rather than absorbed by whoever is under the most pressure.
A simple framework: four questions
- What deserves attention now? Not everything marked urgent is genuinely time-sensitive. Attention now should go to work with a real deadline, a real commercial consequence or a client relationship at genuine risk.
- What should be delayed? Delay is not failure. It is a decision, communicated on purpose, rather than something that happens by default because nobody said it out loud.
- What should be refused? Some requests should not happen at all, not this week and not later, because they sit outside scope, outside capability or outside what the relationship can sustainably support.
- What rule decides when several things are genuinely urgent? Without an agreed rule, the loudest voice wins by default. A simple rule, such as weighing commercial impact against the cost of delay, gives the team something to point to instead of relying on gut feel under pressure.
The value is not in the four labels. It is in forcing the same decision process every time, rather than relitigating priorities from scratch whenever pressure rises.
What this means in practice
None of this requires new software. It requires a short, honest conversation, ideally weekly, where the team agrees what is being prioritised and what is deliberately not being touched. Writing it down matters more than the format.
The operating system around that decision still matters. A connected customer record can help a team see genuine commercial priority, such as which opportunities are close to a decision or which client commitments are at risk, rather than relying on memory or whoever emailed most recently. But the system cannot make the trade-off for you. The team still has to decide.
This is also why prioritisation belongs with strategy, not only project management. Strategy is partly the discipline of deciding where scarce attention will create the most value and where it will not be spent.
Clear answers
Why do small agencies struggle with prioritisation?
Small agencies usually have less slack to absorb competing client and internal demands. When priorities are not agreed explicitly, work can default to whoever asks most recently or most loudly rather than what carries the greatest commercial or delivery consequence.
Does prioritisation mean doing less work overall?
Not necessarily. It means making trade-offs visible. That can reduce wasted switching, protect important work and make capacity decisions clearer, but it does not remove genuine capacity constraints.
Is the research in this article specific to agencies?
No. The cited studies examine US start-ups and Chinese high-tech firms. They are used here for the narrower principle that resource constraints change the value of focus and trade-off management. The agency framework itself is a practical application of that principle.
FAQ
What is the difference between delaying work and refusing it?
Delaying means the work still happens on an agreed later timeline and the client is told when. Refusing means the work will not happen within the current engagement because it falls outside scope, capability or sustainable capacity.
How often should agency priorities be reviewed?
Weekly is a useful working cadence for many small agencies because client demands and available capacity can change quickly. The important point is to use one explicit cadence and decision rule rather than reprioritising continuously through interruption.
What if a client refuses to accept “not now”?
That becomes a conversation about scope, consequence and expectations. Make the trade-off explicit: if this moves forward now, what agreed work moves back? Clear scope and change-control language makes that discussion easier before pressure arrives.
Start with what you are choosing not to do.
Most overload conversations start in the wrong place. They ask how to get more done. I would first ask what the agency has consciously decided not to do this week. If there is no answer, capacity is being allocated by interruption rather than strategy.
Once those decisions are written down and shared, pressure becomes easier to manage because the trade-off is visible. The team knows what matters, clients can be given a clear answer, and a new request has to displace something rather than simply joining an endless list.
New RAAJE series
Continue with the launch collection
A strategy question
What are you deliberately not doing this week?
If everything is urgent, the first job is to make the trade-offs explicit. RAAJE can help turn competing demands into a clearer set of commercial priorities.
Start a conversationSources
- Derek Lidow, “A Better Way to Set Strategic Priorities”, Harvard Business Review, 13 February 2017.
- Noni Symeonidou, Aija Leiponen, Erkko Autio and Johan Bruneel, “The origins of capabilities: resource allocation strategies, capability development, and the performance of new firms”, Journal of Business Venturing, 37(4), 2022.
- Qing Cao, Eric Gedajlovic and Hongping Zhang, “Unpacking Organizational Ambidexterity: Dimensions, Contingencies, and Synergistic Effects”, Organization Science, 20(4), 2009, pp. 781-796.