---
title: "Before You Cut the Manager, Name Who Takes the Work"
description: "Automate routine coordination, then give coaching, conflict and people decisions named owners with enough time to handle them."
author: "Gunner Technology"
published: "2026-11-22"
url: "https://www.gunnertech.com/blog/which-engineering-management-work-can-ai-replace"
---

# Before You Cut the Manager, Name Who Takes the Work

AI can replace routine engineering coordination when the delivery system can track work, route failures and preserve evidence itself. Coaching, conflict and decisions about people still need accountable human owners. Cutting a management role before assigning that work leaves a hole that faster code cannot fill.

## What does the argument against flattening actually say?

It says removing managers can leave essential people work undone, even when delivery appears to keep moving. In [The Engineering Manager's role is under attack (again)](https://www.manager.dev/newsletter/the-engineering-manager-s-role-is-under-attack-again), Manager describes how expanding a manager's responsibilities can squeeze out coaching, career conversations and conflict resolution. That is a warning about capacity and responsibility, rather than a claim that every management layer deserves to stay.

The article describes a cycle: give a manager more people and more technical work, leave less time to manage, then treat the resulting neglect as evidence that management adds little. Its term for the accumulating damage is organizational debt: unresolved problems in how people work together that become harder to repair later.

The article recommends making those problems visible and connecting them to business consequences. A disagreement matters to leadership when it changes what gets built, causes work to be discarded or prevents collaboration. That advice gives a leader something concrete to examine before changing reporting lines. It does not supply a universal staffing ratio.

## Which coordination tasks can leave the calendar?

Status collection, routine assignment and reminders can leave the calendar once the system carries their information and rules. A manager should not need to ask whether a check passed if the work record already contains the result. An agent should not wait for someone to move a ticket when its next permitted step is already defined.

Build that route before removing the person who currently carries it. Define what enters the queue, what evidence moves it forward and where a failure goes. Our post on [replacing delivery ceremony with machinery](https://www.gunnertech.com/blog/the-factory-does-not-need-a-standup) covers that operating change. Automating a meeting summary alone leaves the underlying handoff dependent on a person.

Gunner Technology's position is that roles built entirely around this repeatable relay will go away. A role containing that work alongside coaching and performance decisions needs a different assessment. Saving time on updates does not tell you how much human responsibility the same person can safely absorb.

## Who takes the people work when the role changes?

A named person must take each remaining responsibility, with authority and time to act. Write down who handles career development, performance concerns, interpersonal conflict and workload disputes. Saying the team will handle it is incomplete if nobody can explain who makes the decision when the team disagrees.

Keep this record separate from the delivery board. Tickets can show whether software passed its checks; they cannot settle whether an employee received fair feedback or has a credible development path. Agents can prepare permitted information and handle scheduling. The responsible person still owes the conversation, the decision and the follow-through.

Then check the receiving person's actual commitments. If a technical lead inherits coaching while retaining the same delivery obligations, name which obligation shrinks. If a director takes the work, reserve time and provide a route employees can use directly. An ownership change without a capacity change deserves scrutiny before it becomes the new structure.

## How do you test the plan before cutting a layer?

Test the plan by removing a repeatable coordination duty in a bounded pilot while keeping the existing people responsibilities covered. Choose a product or repository whose work you can observe. State which tasks the factory will take, which decisions remain human and how you will recognize an unowned obligation.

Look at delivery and people work separately. Inspect whether status requests still need manual chasing, failures find an owner and rejected work returns to the right agent. Alongside that, check whether promised feedback happened, conflicts reached someone able to resolve them and employees know where to take a concern. Keep sensitive details in the appropriate private records.

Do not turn the pilot into a score for how many people a manager can absorb. Use it to find which duties actually disappeared and which merely moved. Our discussion of [displacement inside a job title](https://www.gunnertech.com/blog/the-job-title-hides-the-displacement) explains why the task matters more than the label. Change staffing expectations only after you can account for the remaining work.

## What should the new structure make clearer?

It should make clear who chooses the work, who judges the result and who is responsible for the people still doing human work. Those responsibilities can sit with different people. They should remain visible when routine coordination disappears.

The article's warning is useful because a quieter calendar can conceal neglected responsibilities. A working factory should remove the status chase and the manual handoffs. Before you call that a management saving, show where coaching, conflict and career decisions went. If the answer is that someone will pick them up, the reorganization is unfinished.

In response to [The Engineering Manager's role is under attack (again)](https://www.manager.dev/newsletter/the-engineering-manager-s-role-is-under-attack-again) by Manager.

## Quick answers

### Does using AI justify a larger span of control?

Not by itself. Count the responsibilities that remain and the time they require before increasing how many people report to a manager.

### Can a technical lead own people management?

Yes, if the person has the authority, preparation and capacity. Make clear which technical commitments change when that responsibility is added.

### What if the pilot reveals neglected people work?

Restore coverage and fix the ownership or capacity gap before expanding the change. Treat the finding as a problem in the proposed structure.
