Skip to main content
Steady at the Top
← All articles

How to reset workloads for the team left after layoffs

Reset workloads after layoffs by removing work before distributing the responsibilities that remain. Bring managers and people who perform the work into a stop-and-transfer workshop. Leave with named owners, explicit service limits, and a visible list of activities the company will no longer perform.

A stop-and-transfer workshop is a working meeting that first eliminates or reduces demand, then assigns the remaining work within credible capacity. This is a practical working term. It applies Daft and Lengel’s (1986) distinction between missing information and unclear interpretation in organizational information processing to a specific operating decision.

Redistribution alone does not establish feasibility. A spreadsheet can allocate every task while leaving every employee with more commitments than available time. Your job is to decide which promises the smaller organization can keep and which promises must change.

For this reset, apply industrial/organizational psychology, the psychology of work and organizations, to the work left behind. Examine assignments, decision authority, and capacity before asking the surviving team to accept its new portfolio.

Acknowledge the operating change

The surviving team may hear that the company must become more efficient. Translate that statement into decisions. Which approvals disappear? Which reports stop? Which customer commitments require a different cadence? If the answers are absent, efficiency remains an instruction to absorb the loss privately.

Workload is the demand placed on a role. Capacity is what the role can deliver under stated conditions. Utilization is how much of that capacity is already committed. These concepts should not collapse into a single count of employees.

A specialized employee may have open hours while lacking the qualification to perform an urgent task. Another may appear available because the calendar omits exception handling. Use the actual work, including coordination and recovery from errors, to build the picture.

Employment counsel should review changed duties, working-time requirements, compensation implications, and other employment obligations. This article offers general operating guidance. It does not determine legal requirements for a particular workforce or jurisdiction.

The stop-and-transfer workshop method

1. Publish the boundaries before the meeting

Explain what is fixed and what remains open. The staffing decision may be complete while service levels, reporting demands, meeting frequency, and work sequencing remain changeable. Do not invite employees to solve a choice they have no authority to influence.

Ask participants to bring recurring work and live commitments. Include work previously done by departed colleagues and work that supported their roles. Ask for frequency, approximate effort, deadline, beneficiary, and consequence of stopping. Estimates should be labeled as estimates.

Make clear that the workshop does not rank colleagues by willingness to endure pressure. You need accurate demand information. People should be able to say an assignment is infeasible without appearing disloyal to the remaining team.

Use How to lead executive exits and restructuring with care for the broader restructuring process. This workshop addresses the operating model after the staffing change. It should connect to the announced business priorities rather than become an isolated exercise in task allocation.

2. Identify obligations before preferences

Separate required work from customary work. A required regulatory submission, a contracted delivery, and a report someone enjoys receiving have different consequences. Verify the obligation with the appropriate owner instead of accepting every claim that a task is mandatory.

For customer commitments, read the agreement and consult the account owner. For legal or safety requirements, use qualified specialists. Do not stop a control because it is time-consuming or because the person who maintained it has left.

Make hidden coordination visible. Updating a customer, answering a colleague’s exception question, and preparing an approval can consume capacity even when no formal project exists. Ask what work arrives unpredictably and what must remain available to receive it.

Write the business reason beside each activity. “We have always done it” is a history, not a current justification. If nobody can identify the recipient or consequence, the activity is a candidate for a controlled stop.

3. Stop, reduce, or defer demand

Apply those options before transferring work. Stop reports no one uses. Reduce a meeting cadence when decisions can safely wait. Defer a low-priority initiative with an explicit restart condition. Record the person authorized to make each choice.

A pause needs a boundary. Specify what stops, for how long, and what would require reconsideration. Otherwise, paused work can return through informal requests while the capacity model still assumes it disappeared.

Tell internal customers what changes. “The custom analysis will now be monthly” is more useful than allowing requests to accumulate unanswered. Where external commitments must change, route the conversation through authorized owners and appropriate contract review.

Keep a protected list for work that cannot stop. That list should be narrow enough to guide decisions. Calling every activity critical makes the workshop unable to remove demand and leaves the conflict with individual employees.

4. Transfer complete responsibilities

Give remaining work a named owner, an agreed output, and a realistic service boundary. Include authority, information access, training, and backup. Assigning the task without these conditions transfers exposure rather than capability.

Ask what existing work the new owner will stop. If the answer is nothing, test whether capacity genuinely exists. Do not assume that the most dependable employee can absorb another responsibility because that person rarely complains.

Use How to clarify roles when a reorganization creates overlap to distinguish ownership from support. Several people may contribute, but one person needs responsibility for the next decision. A shared inbox can support an owner. It cannot make the decision boundary clear by itself.

Allow a transition period for unfamiliar work. Record which outputs will be slower while the team learns. The organization should carry that adjustment in its promises rather than expect employees to conceal it through unpaid or unrecorded effort.

5. Reconcile the plan with a real week

After the initial assignment, compare planned capacity with actual arrivals. Examine queues, missed handoffs, escalations, and work performed outside the agreed schedule. Use the evidence to revise the plan rather than to punish honest estimates.

Bring Morrison’s 2014 review on employee voice into the workshop design by asking how a team member can dispute an unrealistic transfer estimate. Ask managers to reward early disclosure of overload. A workload plan cannot improve if the only acceptable report is that everything is under control.

Keep a route for urgent tradeoffs. When a new priority enters, an authorized person must choose what leaves or what service boundary changes. Without that rule, every exception becomes an addition and the original reset erodes.

Review whether stopped activities returned through personal favors. A senior executive may bypass the new process by asking a familiar analyst directly. Your own requests must follow the boundaries you asked the team to respect.

A worked redistribution decision

In a hypothetical company, two analysts supported executive reporting, customer exceptions, and a growth initiative. One role is removed. The first draft simply assigns the departed analyst’s activities to the remaining analyst.

The workshop finds that the growth initiative has no current sponsor, several reports duplicate existing data, and customer exceptions need a defined intake route. The company pauses the initiative, removes the duplicate reports, and gives operations responsibility for screening exception requests.

The analyst retains the work requiring specialist judgment. An executive owns decisions about requests beyond the agreed service limit. The team still has difficult tradeoffs, but those tradeoffs now appear in the operating plan.

No efficiency claim is needed to justify this example. It is a hypothetical illustration of changing demand before changing assignments. The result should be tested against actual delivery, not assumed from the elegance of the workshop output.

The private-life composite

A CEO attends a child’s school event while watching internal messages. The same remaining manager answers every question within minutes. At home that evening, the CEO notices the manager is still clearing requests and sends a thank-you note.

This composite shows the temptation to recognize endurance instead of changing the assignment. A better next action is a workload conversation with authority to remove work. Appreciation can accompany that action. It should not serve as the capacity plan.

After a layoff, reduce or reassign unsupported work through the reset process. Keep individual health concerns outside the team capacity discussion. If stress symptoms persist or affect daily life, consult a licensed clinician rather than expecting a revised assignment list to provide clinical care.

Connect workload to recovery

Use How to rebuild morale among employees after layoffs for the wider work of rebuilding morale. Workload is one visible test of whether leadership has accepted the consequences of its own staffing decision. Employees can inspect whether the company reduced demands or merely changed its language.

Use Kramer’s 1999 review as background when checking whether the promised reduction in demand survives an internal customer’s request to restore stopped work. In this setting, let your commitments be specific. Name the work stopped and enforce the service boundary when a powerful internal customer objects.

If the remaining portfolio still exceeds capacity, return to What should a CEO stop doing during a company turnaround?. The answer may require a narrower business plan, approved outside support, or revised delivery commitments. Those are executive decisions. Do not turn an unresolved strategy conflict into a test of employee attitude.

Close each review by naming the tradeoff you accepted. The smaller team needs a smaller or differently designed set of promises. The workload reset is complete when the operating calendar reflects that decision and new requests receive an explicit capacity choice.

Give internal customers a usable boundary

A service limit should explain both the normal offer and the exception route. For example: routine requests enter one queue, receive an initial response on the stated schedule, and move ahead only when an authorized owner accepts the displaced work. Adapt the timing to actual capacity. Do not copy a service promise the team cannot meet.

Keep the queue visible enough for requesters to see that their work competes with other obligations. Avoid publishing individual employee capacity details where they become a tool for informal pressure. The purpose is to govern demand, not invite colleagues to claim every apparent opening.

When you authorize an exception, record the consequence in the same place as the request. Name the delayed output and notify its owner. That small discipline prevents a series of individually reasonable requests from creating an unacknowledged overload.

Sources

Steady at the Top