M360 Compass

M360 Compass · Management insights

Workload management: make room for the right work

· 6 min

Four colleagues divide a stack of blue folders into smaller groups.

Workload management becomes difficult when every request seems urgent and the trade-offs stay invisible. Counting tasks is not enough. Two assignments can require very different effort, depend on an unavailable colleague or be interrupted repeatedly throughout the day.

A short review can help a small business discuss those constraints before commitments accumulate. The proposed method uses three lists: incoming demands, genuinely available capacity and decisions that need an owner. It focuses on organizing work. The aim is to decide what can move forward, what needs to change and who is responsible for the trade-off, together with the people doing the tasks. It is a planning conversation, not a rating of personal worth.

Workload management starts with comparable demands

List the commitments for the coming week. For each, record the expected result, useful delivery date, owner and estimated effort. Use a unit the team understands: focused half-days, preparation hours or production slots. Explain that estimates will be revised as you learn; they are not exact measurements of an employee’s contribution.

Include activities that frequently disappear from the plan: answering internal requests, helping a new colleague, resolving an irregularity and following up on previous decisions. If you count only project work, you are already assigning capacity people do not actually have.

CCOHS describes workload management measures including clearer expectations, reviewing redundant activities and adjusting deadlines. The review below turns those principles into an operational discussion. It does not diagnose a health condition or establish a regulatory conclusion.

Estimate the capacity that genuinely exists

Start with scheduled work time, then remove known absences, necessary meetings and recurring activities already committed. Keep an explicit allowance for unplanned requests based on recent experience. Do not adopt a universal percentage simply because it sounds reassuring or appears in someone else’s dashboard.

Someone may have four focused half-days available without being able to use them on any assignment. Check required skills, access and dependencies. A task waiting for approval does not become executable just because an empty calendar slot exists.

Discuss fragmentation as well. Three twenty-minute openings do not always replace one continuous hour. When an assignment requires complex preparation, the frequency of interruptions may matter more than the theoretical total number of available hours.

Keep uncertainty visible. “Between one and two half-days” is more useful than an invented precise estimate. Identify what needs to be checked to narrow that range at the next review. Planning becomes more credible when the team can distinguish a known commitment from an assumption that still requires confirmation.

Make four explicit trade-offs before adding work

Put the decision in the file the team will review.

Three decisions to record in the workload review
SituationDecision to record
Urgent work confirmedName the work that moves.
Approval pendingSet the next check-in time.
Effort uncertainSchedule a short trial.

Postpone. Change a date with the person depending on the result. Record the new date and the consequence being accepted. An unannounced delay merely turns one team’s workload problem into another team’s surprise.

Reduce. Find a smaller deliverable that remains useful. Describe what will be included and what is outside scope. Quietly weakening an important control is not a sensible reduction in scope; the changed result needs to be understood by the responsible people.

Reassign. Move part of the work to someone with appropriate skills and available time. Check what they will stop doing to accommodate it. Delegation without removing other commitments can simply transfer the imbalance to another employee.

Remove. Stop an activity that is no longer useful or duplicates another effort. Ask who still uses its result. A weekly report can continue consuming time long after the decision it supported has disappeared.

For each trade-off, name the decision-maker, the person doing the work and anyone who needs to be informed. A task list alone does not explain why commitments changed. A short decision record preserves that context and helps prevent old priorities from returning unnoticed.

Fictional example: a full week before surprises arrive

Fictional example. Riverside Studio is an invented business in Gatineau preparing a delivery week. The numbers and outcomes below are illustrative.

Melanie has ten half-days on the calendar. Two are already reserved for client meetings and one for helping a colleague learn a process. Based on recent requests, the team provisionally keeps another half-day available for interruptions. That leaves six and a half half-days for planned assignments.

Known requests currently total eight half-days. The manager does not simply tell Melanie to “prioritize better.” They examine the purpose of each deliverable together. An internal report no longer has an active user, so they remove it. A client summary can be delivered in two stages, with explicit agreement about what the first version will contain.

Another task appears suitable for reassignment. The proposed colleague has time but is waiting for access. The transfer therefore depends on resolving that issue, and the manager takes responsibility for obtaining a decision on the access request.

Midweek, a new request arrives. The team reopens the priority decision rather than silently adding it to the list. The desired result is a set of commitments consistent with observed capacity. It is not a promise that every week will unfold exactly as planned or that uncertainty can be eliminated.

Check the effect of decisions with the team

Hold a brief review after several days. Ask which commitments moved forward, which interruptions used the allowance and which estimate proved optimistic. Avoid turning the conversation into a defence of every minute. The purpose is to improve the plan and the decisions supporting it.

Compare postponed work with the decisions recorded. If the same assignment slips every week, examine its priority, owner or persistent dependency. A recurring capacity imbalance is unlikely to improve through an endless addition of tracking tools.

M360 Compass RoleAlign connects responsibilities with expectations, decisions and objectives. Those reference points can help identify who owns a trade-off. Performance and development connects feedback and follow-up when a development need is identified with the employee.

This method does not imply that the platform automatically measures available capacity or diagnoses overload. For an M360 Compass demonstration, bring an anonymized list of three commitments and the decision you need to clarify. You can assess the fit against a real management situation rather than an abstract list of features.

For a related management tool, explore a useful one-on-one meeting. Use it to clarify a separate question, while keeping this method focused on the situation described here.

Frequently asked questions about team capacity

Do we need to time every task?

No. Begin with simple, comparable estimates and adjust them through experience. Collect information that supports a decision. Detailed measurement without a clear purpose can create extra work and imply more accuracy than the estimates justify.

How much capacity should remain for surprises?

Review recent weeks and the requests that actually interrupted the plan. Choose a provisional allowance suited to your context, then revise it. No single proportion fits every team, type of work or reporting period.

Who decides when two requests are urgent?

Identify someone authorized to compare consequences and decide the order. That person needs to understand dependencies and inform requesters. An employee should not be left to satisfy two incompatible commitments without an explicit priority decision.

What if the imbalance returns every week?

Review recurring activities, expectations and dependencies. Identify what must be removed, simplified or given resources. Check the effect of changes with the team rather than repeatedly relying on additional effort to make an unrealistic plan appear workable.