[AI] From Engineers to Managers: Why Organisations Are Rebalancing the Workforce
For much of the technology era, organisations were built around the idea that more engineers meant more innovation. If a company wanted to build faster, it hired more developers, created more teams, and increased its technical capacity.
That model is now being questioned.
Across many organisations, there is a growing shift towards fewer individual engineers and a relatively larger management and coordination layer. At first glance, this can seem counterintuitive. If technology is becoming more important, why would companies need fewer people writing the technology?
The answer lies in a fundamental change in how organisations create value.
The productivity paradox
Modern engineering teams have access to tools that dramatically increase individual productivity. Cloud platforms, reusable software components, automation, low-code tools and, increasingly, AI-assisted development mean that a small number of highly capable engineers can accomplish what previously required much larger teams.
Generative AI is accelerating this trend.
An engineer can now use AI to generate code, write tests, investigate bugs, document systems, translate between programming languages and prototype solutions. The result is not necessarily that engineers disappear. Rather, the amount of engineering output that can be produced by each engineer increases.
When individual productivity rises, organisations have a choice.
They can continue adding engineers and produce substantially more technology, or they can maintain roughly the same technical output with fewer people and redirect resources towards other organisational capabilities.
Increasingly, some companies are choosing the latter.
The work is moving from "building" to "orchestrating"
As engineering becomes more productive, the constraint shifts.
The question is no longer simply:
"How many people do we need to build this?"
It becomes:
"Which things should we build, which should we buy, which should we automate, and which should we stop doing altogether?"
Those are management questions.
A highly productive engineering organisation still needs people who can set priorities, allocate resources, manage dependencies, communicate with stakeholders and make trade-offs across competing initiatives.
This creates a greater need for orchestration.
Managers increasingly become the connective tissue between technology, business strategy, customers, finance, compliance and operations.
In this model, the manager's role is not simply to supervise engineers. It is to make sure that engineering capacity is directed towards the highest-value problems.
Why more managers can make sense
The phrase "more managers" often triggers an immediate negative reaction. Organisations have spent years talking about eliminating bureaucracy and reducing unnecessary layers of hierarchy.
But management and bureaucracy are not the same thing.
A manager can create leverage when their work allows multiple teams to operate more effectively.
For example, one strong manager might:
eliminate duplicated work across several engineering teams;
resolve organisational dependencies;
negotiate priorities with product and commercial teams;
remove unnecessary approval processes;
identify projects that should be stopped;
coordinate the adoption of AI and automation;
develop technical and organisational talent; and
translate company strategy into executable priorities.
If that work enables ten or twenty engineers to become significantly more effective, the manager is not merely an overhead.
They are a force multiplier.
The rise of the "manager of systems"
The management role is also changing.
The traditional manager was often responsible for people: performance reviews, hiring, budgets and team administration.
The modern manager increasingly has responsibility for a much broader system.
They need to understand:
People — Who has the right skills, and where are the capability gaps?
Technology — Which platforms, tools and AI capabilities can increase productivity?
Priorities — Which initiatives deserve scarce resources?
Dependencies — Where can one team's work block another?
Economics — What is the cost of maintaining a system versus replacing or automating it?
Risk — Where are security, regulatory or operational risks accumulating?
Outcomes — Is the organisation actually creating customer or business value?
This is less about managing activity and more about managing complexity.
AI makes coordination more valuable
AI may appear to threaten managers just as much as engineers.
After all, if AI can write reports, analyse data, prepare presentations and summarise meetings, why should organisations need additional management capacity?
The answer is that automation reduces the cost of producing information, but it does not automatically determine what information matters or what decision should be made.
When the cost of creating things falls, the cost of choosing between things becomes relatively more important.
Imagine an organisation where AI allows teams to produce ten times as many prototypes. The organisation does not necessarily become ten times more productive.
It may instead create a new problem: too many things competing for attention.
Someone still needs to decide:
Which prototype should become a product?
Which should be abandoned?
Which creates strategic advantage?
Which introduces unacceptable risk?
Which teams should work together?
What should receive investment?
In other words, AI can increase the value of judgement and prioritisation even as it reduces the value of routine execution.
But there is a danger
The move towards more management is not automatically a good thing.
An organisation can easily interpret "coordination is important" as "we need another layer of management."
That can create exactly the opposite of what was intended.
Too many managers can produce:
slower decision-making;
excessive meetings;
duplicated ownership;
political behaviour;
distance between decision-makers and customers;
excessive reporting; and
a culture where people optimise for internal visibility rather than outcomes.
The distinction is therefore not really between engineers and managers.
It is between execution capacity and organisational leverage.
A company can have too many engineers. It can also have too many managers. The optimal balance depends on where the organisation's bottleneck lies.
The real shift: from headcount to leverage
The most interesting organisational change may therefore not be "fewer engineers, more managers."
It is a shift from measuring organisations by how many people they have to measuring them by how much output each person can enable.
In the industrial era, scale often meant adding workers.
In the software era, scale increasingly came from adding engineers.
In the AI era, scale may come from combining a relatively small number of highly capable technical people with strong product, managerial and organisational systems.
That changes the economics of headcount.
A company might need fewer people to produce the same amount of software, but more people focused on deciding where software should be built and how it fits into the broader business.
What this means for engineers
This does not necessarily mean engineering careers are becoming less important.
Quite the opposite.
The value of engineers may increasingly concentrate around areas that are difficult to automate:
architectural judgement;
systems thinking;
understanding complex business problems;
security and reliability;
technical strategy;
evaluating AI-generated solutions;
working across organisational boundaries; and
making high-consequence technical decisions.
The engineer of the future may write less code but make more important technical decisions.
That is a very different role.
What this means for managers
Managers face an equally significant transformation.
Simply coordinating meetings, tracking tasks and producing status reports will become increasingly difficult to justify when AI can automate much of that work.
The valuable manager will be the one who can create clarity where there is ambiguity.
They will need to answer questions such as:
What should we do?
Why should we do it?
What should we stop doing?
Who should own it?
What constraints matter?
How do we know whether it worked?
The manager's value therefore moves upward—from administration towards judgement, prioritisation and organisational design.
The organisation of the future
The emerging model may ultimately be less about having "more managers" and more about having fewer layers and more leverage.
A small number of highly capable engineers can produce significant technical output.
A small number of highly capable managers can coordinate that output across a complex organisation.
AI increasingly handles routine production and administration.
Humans increasingly concentrate on judgement, relationships, strategy and accountability.
The winning organisation will not necessarily be the one with the most engineers or the most managers.
It will be the one that understands where human effort creates the greatest marginal value.
And that may be the most important reason organisations are beginning to reconsider the traditional engineer-heavy model.
The future of work may not be about replacing engineers with managers.
It may be about replacing execution-heavy organisations with leverage-heavy organisations.
Comments