What changes for executives, managers and frontline staff
Most discussions of AI and jobs treat the company as one block. In practice AI changes three layers of the organisation in three different ways, and a plan that addresses only one of them leaves the other two to improvise.
Executives: from running the analysis to holding the purpose
A large share of senior time goes into gathering information, building scenarios and watching the market. Software now does much of that faster and more completely. What remains with the leadership is what cannot be delegated: setting the direction, choosing where capital goes, making the calls that cannot be undone, and answering for the results.
The practical change: fewer meetings to assemble the picture, more time deciding on it. And one new duty, looking regularly for the part of your own business that a newcomer could make obsolete.
Managers: from coordinating to handling exceptions
Much of middle management is coordination: collecting status, routing work, chasing approvals, reporting upward. Most of that can be done by systems that see the whole flow. What remains is the work systems do badly: resolving the cases that fall outside the rules, settling conflicts between teams, and developing people.
This is the layer most at risk of being cut too early, and the one where good redesign pays most. A manager who handles exceptions and grows the team is worth more than one who forwards reports.
Frontline: from doing the task to running the system
Routine execution moves to software: data entry, standard replies, scheduling, first checks. Frontline work becomes supervising that execution, stepping in when something goes wrong, handling the customer relationships that need a person, and improving the process from the inside.
The trap to avoid
Telling people "you are now an exception handler" without changing anything else is not a new role. It is a smaller old one. A real new role comes with training, authority to override the system, a budget where needed, and a path to grow.
For each of the three layers, write down what moves to software, what stays, and what new responsibility is added. If the third column is empty, the plan is a headcount plan, not a redesign.