skip to content

Back to work: 4 prioritisation mistakes that exhaust teams

Back to work: 4 prioritisation mistakes that exhaust teams
contents

The return to work in September often means a faster pace. Projects that slowed down over the summer pick up again, new requests appear and year-end targets draw closer. At the same time, managers have to work around remaining leave and an operational capacity that is still fluctuating.

This tension is particularly strong when the team has to keep its business running while hiring for vacant roles and onboarding new joiners. Hiring is then not a side issue: it sits squarely among the trade-offs of the September return.

All of these matters are legitimate. The problem arises when they all become priorities at the same time.

Employees then jump from one project to another, attend more meetings and struggle to make progress on tasks that need concentration. Poor prioritisation therefore produces more than delays: it multiplies changes of direction and creates a state of permanent urgency.

To avoid exhausting teams from September onwards, the manager's role is less to accelerate than to make the trade-offs.

Mistake 1: assuming everything can be a priority

In September, the matters that built up over the summer all become visible again at the same moment. Every team wants to restart its projects and every stakeholder naturally regards their own requests as important.

The list of priorities then grows longer while the resources available stay the same.

Yet a new priority cannot simply be stacked on top of the previous ones. It requires a choice: if one matter has to move forward immediately, another must be postponed, scaled back or dropped.

To keep a clear view of the roadmap, three levels may be enough:

  • Immediate priority: the item must move forward this week.
  • Planned priority: the item is important, but it can be scheduled.
  • On hold: no action is expected for now.

Each priority should then be linked to an owner, a deadline and an expected outcome. Without these, it remains a general intention.

The number of immediate items must also stay limited. When ten projects are presented as urgent, the team often ends up dealing with the most visible requests, or those pushed by the most insistent stakeholders.

For every new request, the manager should therefore ask a simple question: if we decide to deal with this item now, which other one do we have to postpone in exchange?

Mistake 2: setting objectives without assessing real capacity

A roadmap can look realistic on paper and still be impossible to execute.

In September, a team's theoretical capacity rarely matches its real capacity. Some employees are finishing their holidays, some roles may be vacant and managers are sometimes tied up with hiring or with the onboarding of new arrivals.

Before setting objectives, you therefore need to take into account:

  • leave still scheduled;
  • vacant roles;
  • the time spent on hiring and onboarding;
  • deadlines already committed to.

This analysis avoids spreading the workload as if the team were immediately at full strength and fully operational.

A credible plan must also keep a margin for the unexpected. Committing all available capacity from the start of the month turns every new request into an emergency and forces the team to work in permanent catch-up mode.

Priorities should therefore be set on the basis of the resources actually available, not those the manager would like to have.

Mistake 3: treating hiring and onboarding as peripheral time

Hiring and onboarding new colleagues are sometimes treated as parallel activities, with no effect on the team's operational workload.

Yet hiring takes time: defining the need, talking to recruiters, interviews, debriefs and decision-making. Onboarding then draws on the manager, but also on the colleagues responsible for passing on information, introducing the tools and supporting the first assignments.

This time has to be factored into the plan.

A new hire does not immediately make up for a lack of resources. During the first weeks, their arrival can even temporarily reduce the team's capacity. This phase is a necessary investment to make a lasting ramp-up to autonomy possible.

The manager may therefore need to:

  • temporarily adjust some operational objectives;
  • clearly designate the people responsible for guiding the newcomer;
  • share out the handover time;
  • postpone projects that are not essential.

Underestimating this workload risks putting the team and the newcomer under pressure at the same time. Employees have to keep their own work going while handing over knowledge, while the new hire may feel they must be fully operational straight away.

Anticipating this period, on the other hand, protects the quality of the integration and prevents hiring, which is meant to strengthen the team, from becoming an additional source of tension.

Mistake 4: handing the trade-offs over to the team

Some changes are unavoidable. A customer request, a change of strategy or a delay can force a rethink of priorities.

The problem arises when these changes are not explained, or when employees have to decide on their own which requests to handle first. They can then find themselves facing contradictory expectations from several managers or teams.

This situation is particularly exhausting: it shifts responsibility for the trade-off without giving employees the authority they need to refuse or postpone certain requests.

The manager has to act as a filter. When a priority changes, it is up to them to make clear:

  • why the decision is changing;
  • what impact it will have on other projects;
  • what is kept, postponed or dropped;
  • how long this new arrangement is meant to last.

This transparency does not remove the constraints, but it makes them understandable. It also prevents the work already done from being seen as pointless, and decisions from seeming arbitrary.

A short, regular check-in can then be used to see what is moving, what is stuck and what should be deprioritised. The aim is not to control every task, but to protect the team from an accumulation of incompatible requests.

Building prioritisation that lasts

Good prioritisation is more than a single back-to-work meeting. It has to be regularly tested against the reality of the business.

A weekly or fortnightly check-in can confirm that the choices made are still relevant. But this meeting should not be used to add new items as a matter of course.

For each new request, three questions help preserve the balance:

  • What result are we actually expecting?
  • Why does this item need to be dealt with now?
  • What are we choosing to postpone in exchange?

These questions make the trade-offs more explicit and stop work from piling up silently.

Conclusion

In September, exhaustion does not come only from the volume of work. It also results from priorities that are too numerous, too changeable or insufficiently explained.

To protect their team, the manager must start from real capacity, factor in the time spent on hiring and onboarding, then own the necessary trade-offs. Prioritising means deciding what can wait as much as what must move forward.

Anticipating hiring needs and cutting the time spent looking for the right profiles also lets the manager keep more availability for their team and their operational priorities.

A team does not become more efficient by working on more items at once. It progresses when everyone knows where to focus their efforts and has the time needed to see their work through.

FAQ

How many priorities should a team have in September?

There is no universal number, but immediate priorities should stay limited. Two or three clearly defined collective objectives are generally more effective than a long list of items presented as urgent.

How do you decide between operational projects and hiring?

The time spent on hiring has to be built into the team's real capacity. If interviews or the integration of a new hire take up a lot of managers' and employees' time, some operational objectives need to be adjusted or postponed.

How should you respond to a new priority requested by management?

It is often more effective to set out the consequences of the trade-off than to give a flat refusal: "We can deal with this item this week, but that means postponing project X. Which choice do we want to favour?" This wording makes the decision explicit and shared.

take action

turn reading into hiring

describe your role, our specialised headhunters take it on. 26 days on average.