Management Is a Function. Leadership Is a Skill. AI Is Coming for the Function.

Anthropic published a research paper in March 2026 mapping AI's theoretical capability against every occupation in the U.S. economy. The number for management occupations: 91.3%. Large language models can theoretically handle over nine out of ten tasks that managers currently perform.

The instinctive response to that number is panic. Or dismissal. Both miss what's actually happening.

The 91.3% figure describes management. It does not describe leadership. And the distinction between those two words, which most organizations use interchangeably, is about to become the most consequential sorting mechanism in corporate life.

Kotter drew the line in 1990

John Kotter's framework is 36 years old and has never been more relevant. Management, he wrote, is about coping with complexity. It produces order. Planning, budgeting, organizing, staffing, controlling, problem-solving. These are systematic, repeatable activities that turn ambiguity into process.

Leadership is about coping with change. It produces movement. Setting direction, aligning people, motivating, inspiring. These are adaptive, relational activities that turn process into purpose.

Peter Drucker landed in the same place from a different angle. Management is doing things right. Leadership is doing the right things. In a knowledge economy, Drucker argued, the management function becomes almost irrelevant because any effective knowledge worker is exercising judgment, not following procedure.

Abraham Zaleznik pushed the distinction further. In a 1977 Harvard Business Review article that still gets assigned in business schools, he argued that managers and leaders are psychologically different types. Managers are "once-born," people who followed a stable path, identify with the existing social order, and see themselves as conservators of the organization. They minimize risk and conflict. Leaders are "twice-born," people shaped by some period of personal struggle or inner conflict that detached them from the status quo and gave them the ability to challenge it.

That psychological framing matters because it predicts what happens when AI removes the mechanical work. The once-born manager, whose identity is wrapped up in maintaining order, loses the activity that defined the role. The twice-born leader, whose instinct is to challenge and redirect, gains time and headroom that the coordination overhead used to consume.

All three were writing before AI existed as a practical tool. They were making a conceptual argument. AI is turning it into an operational one.

What management actually consists of

Break the management function into its component tasks and the automation case becomes obvious.

Planning and organizing: setting objectives, creating schedules, allocating resources. A system that can read every meeting transcript, track every commitment, and measure whether decisions closed with enough structural specificity to execute has more planning visibility than any human manager. It doesn't forget. It doesn't get distracted by the loudest voice in the room. It measures whether the planning session produced durable outcomes or just the feeling of progress.

Directing and coordinating: assigning work, managing handoffs, tracking dependencies. This is the core of middle management, making sure the right people are doing the right things in the right sequence. A system that measures Delegation Flow (the probability that delegated work will actually execute, based on whether the delegation left the room with an owner, a next step, and a deadline) replaces the manager's "checking in" function with a structural signal that's available immediately after the meeting.

Controlling and monitoring: tracking progress, measuring performance, course-correcting. The status meeting exists because managers need to know what's happening. A coordination observability system makes the status meeting redundant. It shows which decisions are holding, which are generating rework risk, which topics keep resurfacing as zombie items, and which escalations left without a carrier. The manager's role as information aggregator gets replaced by a dashboard that's more accurate and more timely than any human summary.

Reporting and communication: status updates, stakeholder alignment, upward reporting. Most of what managers report to their managers is a curated summary of coordination state. The system produces that summary automatically, with structural evidence instead of narrative spin.

Growth Wise already does most of this. It scans meeting transcripts for closure signals (was a decision explicitly stated, was an owner named, was a next step defined, was a deadline set). It grades every outcome as Achieved, Partial, or Absent. It tracks Delegation Flow, Rework Risk, Coordination Debt, and Decision Churn across every meeting. It tells you which meetings are producing real coordination and which are performative theater. These are management functions. A system handles them better than a person because a system doesn't have selective memory, doesn't avoid uncomfortable truths, and doesn't optimize for its own career survival when reporting upward.

What leadership actually requires

Now subtract all of that from the manager's job description. What's left?

Deciding what matters. Choosing direction when the data is ambiguous. Aligning people who disagree on where to go. Building trust in an environment where trust has eroded. Having the conversation that everyone is avoiding. Knowing when the process is wrong and having the courage to override it. Developing people by understanding what they need, not what they say they need. Holding the tension between urgency and sustainability.

None of these are systematic. None are repeatable in the procedural sense. All of them require judgment, empathy, relational skill, and the willingness to be wrong in public.

Kotter would call this the leadership function. Drucker would call this doing the right things. AI can't do any of it. AI can tell you that Delegation Flow dropped from 80% to 38% across the last three planning sessions. It cannot tell you that the drop happened because two senior engineers lost trust in the product direction after the reorg, and the way to fix it is a 45-minute conversation over coffee where you listen more than you talk.

The thought experiment

If a system can handle 91.3% of management tasks, and the remaining tasks are all leadership tasks, then the manager role as traditionally defined is a transitional form. It exists because organizations needed a human to do both the mechanical coordination work and the adaptive leadership work, and there was no way to separate them.

AI separates them.

The coordination work (planning, monitoring, directing, reporting) gets absorbed by systems that do it faster, more consistently, and without political distortion. The leadership work (direction-setting, alignment, trust, development) stays with humans, but now those humans are freed from the mechanical overhead that used to consume 80% of their week.

This changes who should be in the role. The current selection criteria for managers over-index on organizational skills, process discipline, and stakeholder management. These are management skills. The people who get promoted are often the people who are best at the mechanical function. The new selection criteria would over-index on judgment, relational intelligence, and the ability to create psychological safety. These are leadership skills. They're rarer, harder to develop, and historically undervalued because they were bundled with the mechanical work that organizations actually needed to keep running.

What this means for coordination observability

A friend recently pointed out that Growth Wise, taken to its logical extension, becomes a mechanism for eliminating the management function entirely. He's right.

Growth Wise instruments the coordination layer. It makes visible whether decisions are closing, whether delegations are landing, whether the same unresolved topics are cycling back week after week. Every one of those visibility functions used to live inside a human manager's head. The manager sat in the meetings, tracked the commitments in a notebook or a spreadsheet, followed up with people who hadn't delivered, and reported the state of play to the next level up. Growth Wise does all of that, structurally, with evidence, without the cognitive load.

But Growth Wise doesn't tell you whether you're building the right product. It won't surface the fact that your best engineer is disengaged because she feels her technical judgment has been overridden three times in a row. It can't read the room and realize that the cross-team conflict isn't about scope; it's about two leaders who fundamentally disagree on company direction and are using the planning process as a proxy war. And it will never tap you on the shoulder and say: slow down, stop optimizing for velocity, and listen.

The tool absorbs the management function. The human who used to perform that function is now freed to do the leadership work that was always more important, was always harder, and was always getting squeezed out by the coordination overhead.

The apprenticeship question

There's a legitimate objection to all of this. If AI absorbs the coordination work that junior managers used to cut their teeth on, where do future leaders learn? The traditional development path runs through the mechanical function: you track commitments, run standups, manage a small project, and gradually develop judgment by handling progressively larger coordination challenges. Remove the mechanical rung of the ladder and you risk "experience starvation," a generation of senior people with no pipeline of developed successors behind them.

But this assumes the only way to develop leadership is through management. There's another path, and organizations that figure it out early will have a serious advantage.

The highest-value leadership skill in a world where AI handles coordination mechanics is the ability to hold a high-quality conversation. Not present at one. Hold one. Facilitation: the discipline of structuring collective sense-making so that the right people reach the right conclusions together. Setting the agenda so it surfaces the real tensions. Managing turn-taking so the quiet expert gets heard before the loud executive closes the discussion. Keeping the group on the question that matters instead of the question that's comfortable. Knowing when the room needs five more minutes of silence instead of another slide.

Junior leaders can learn this by being in the room during the moments that matter, not as note-takers, but as process holders. A senior leadership team working through a product direction disagreement or a reorg decision needs someone holding the conversational structure while they concentrate on the substance. That's a real job, a hard job, and a training ground for exactly the skills that will define leadership once the coordination layer is automated.

The system tracks whether decisions closed. The junior facilitator ensures the conversation had the structural conditions to produce real closure in the first place. The senior leaders focus entirely on the dialogue. Three layers, each developing the next one upward.

The uncomfortable implication

If management is a function and leadership is a skill, and AI absorbs the function, then the uncomfortable question is: how many current managers are actually leaders?

Most organizations have promoted people into management because they were good at the mechanical work. They're organized, reliable, responsive, detail-oriented. They can run a planning process and keep a project on track. These are valuable competencies, and they're about to be automated.

The managers who will thrive are the ones who, once freed from the mechanical overhead, turn out to have the leadership skills that were always there but never had room to develop. They'll use coordination observability tools to handle the coordination layer and spend their newly available time on the work that actually requires a human: building alignment, developing people, making judgment calls in ambiguous situations, and having the hard conversations that no dashboard can have for you.

The managers who won't thrive are the ones whose entire value proposition was the mechanical function. They kept things organized. They tracked things. They reported things. The system does that now. And the leadership skills that would justify their role were never developed because the mechanical work was all-consuming.

This isn't a prediction about the distant future. Anthropic's data shows 91.3% theoretical capability today. Gartner predicts that by 2026, 20% of organizations will use AI to flatten their structures, eliminating more than half of current middle management positions. Deloitte's research on the future of middle management found that by end of 2024, advertisements for middle management roles had already dropped 42% from their 2022 peak. The reorganization of what "manager" means is already underway, and the job market is pricing it in before most organizations have noticed.

The organizations that recognize the management-leadership split and restructure accordingly will develop leaders. The ones that don't will keep promoting coordinators into roles that coordination software is about to make redundant.