AI Leadership Transformation: Ascendants or Obsolete?

In the age of AI, businesses will increasingly fall into two categories: the Ascendants and the Obsolete.

That may sound dramatic, but the dividing line is already becoming visible.

For leaders, this is the central challenge of AI leadership transformation: turning technological capability into organizational advantage.

According to Stanford’s 2026 AI Index, 88% of surveyed organizations were using AI in at least one business function in 2025. Yet AI-agent deployment remained in the single digits across almost every business function.

That gap tells us something important.

Using AI is no longer a competitive advantage. Knowing what to do with it is.

The real competition will therefore not be between companies with AI and companies without AI. It will be between organizations that can continuously redesign themselves around new capabilities and organizations that cannot.

And behind those organizations, we increasingly see three types of leaders:

The Makers. The Watchers. The Blamers.

The Makers

Makers do not ask:

“How can we add AI to what we already do?”

They ask a much more uncomfortable question:

“If we created this company today, knowing what AI can do, would we still organize the work this way?”

That distinction is enormous.

A Maker may look at a process that requires ten people, five handovers and three days and discover that AI can reduce the information-processing part to twenty minutes.

But the objective is not simply cutting people.

The interesting question is what those people can now do with the time, intelligence and information suddenly available to them.

Makers redesign workflows.

They connect company knowledge.

They turn historical experience into reusable intelligence.

They automate repetitive reasoning while keeping human judgement where judgement actually creates value.

McKinsey’s research shows exactly why this matters. Although AI adoption has become widespread, only around one-third of surveyed organizations reported scaling their AI programs across the enterprise.

The bottleneck is increasingly not the model.

The bottleneck is the organization.

Organizations that want to lead this change must move beyond experimentation and become AI Makers rather than Watchers.

The Watchers

Watchers are more dangerous than they appear because they do not look conservative.

They attend conferences.

They subscribe to ChatGPT, Claude or Gemini.

They launch an AI committee.

They run pilots.

They ask consultants for presentations about “AI transformation.”

And then very little changes.

The organization continues producing quotations, engineering drawings, reports, purchasing decisions or project documentation essentially as it did five years ago — only now someone occasionally asks an LLM to write an email.

Watchers confuse exposure to technology with transformation.

They keep waiting for the technology to become more mature, more reliable, cheaper or easier to integrate.

But AI will never send them a message saying:

“The technology is now finished. You may safely begin.”

The companies moving fastest are learning while the technology is changing.

That learning compounds.

And compounded learning may eventually matter more than compounded capital.

The Blamers

Then come the Blamers.

They have explanations for everything.

AI hallucinates.

Our data is messy.

Our customers are different.

Engineering is too complex.

Our employees will resist.

Regulation is unclear.

Cybersecurity is a problem.

And, interestingly, many of those objections are perfectly legitimate.

That is precisely what makes the Blamer mindset so seductive.

The mistake is not identifying the risks.

The mistake is using the risks as justification for doing nothing.

A Maker sees an unreliable AI system and asks how to build verification around it.

A Blamer sees the same system and explains why AI cannot work.

Same technology.

Completely different trajectory.

From AI Tools to Organizational Intelligence

This distinction becomes particularly interesting in engineering.

Engineering companies accumulate enormous amounts of intelligence: CAD models, drawings, quotations, specifications, standards, calculations, supplier knowledge, previous design decisions and thousands of solutions to problems that somebody inside the organization has already solved.

Yet much of that intelligence remains fragmented.

AI changes the economics of accessing it.

This is one of the ideas behind AISON AE, the AI engineering environment we are developing.

The goal is not to build another chatbot.

It is to create an engineering intelligence layer capable of combining AI with company knowledge, historical projects and deterministic engineering tools.

Imagine an engineer analysing a new component.

Instead of starting from zero, an AI system can retrieve similar parts previously designed, associated 2D drawings, manufacturing decisions, quotations, technical documents and lessons learned.

AI proposes.

Company knowledge provides context.

Engineering rules verify.

The engineer decides.

That is a very different model from simply asking ChatGPT a question.

It turns years of accumulated experience into something closer to institutional memory that can actively participate in the work.

And that may become one of the most valuable assets a technical company can possess.

The Real Competitive Advantage

The World Economic Forum estimates that about 39% of workers’ existing skill sets will be transformed or become obsolete by 2030. At the same time, it expects analytical thinking, creativity, resilience, leadership and collaboration to remain critical alongside AI skills.

That combination is revealing.

The future is probably neither “humans versus AI” nor “AI replacing humans.”

It is organizations capable of combining machine intelligence, human judgement and proprietary knowledge better than their competitors.

The strongest companies will therefore not necessarily have the largest AI budgets.

They will have the shortest distance between knowledge and action.

They will learn faster.

Experiment faster.

Reuse knowledge faster.

Make decisions faster.

And improve their systems every time somebody completes a project.

Those are the Ascendants.

The Obsolete may still have good people, respected brands and profitable businesses.

Their problem is simply that the world around them will be learning faster than they are.

So perhaps every leadership team should stop asking:

“What should we do about AI?”

And ask something much more personal:

Are we Makers, Watchers or Blamers?

Because technology will continue to change.

The category we belong to is still a choice.

At Innovation Code, we help organizations move from AI experimentation to practical transformation by redesigning workflows, connecting knowledge, and turning AI into measurable business value. Learn more at www.innovationcode.com.

AI ROI in Engineering: Turning Time Savings into Value

McKinsey estimates that knowledge workers spend around 41% of their time on repetitive activities that could potentially be automated.

Take a company with 1,000 employees earning an average salary of $75,000 per year. The annual payroll is $75 million. If 41% of that working time is spent on tasks that could be automated, more than $30 million of labour capacity is theoretically involved.

If that amount were converted directly into additional operating profit and the company were valued at an 8x multiple, the theoretical increase in enterprise value would be around $240 million.

It is an attractive calculation. But there is a problem: saving time is not the same as saving money, and saving money is not automatically the same as creating value.

That distinction is where a serious AI strategy begins.

The Missing Link in AI ROI

Imagine an engineer earning $75,000 per year. An AI system saves that person two hours per day by reducing repetitive work.

Has the company saved 25% of the engineer’s salary? No.

The salary is still paid. What the company has created is not immediate profit. It has created capacity.

If the engineer simply finishes the same workload earlier, the financial impact may be small. But if the engineer can now manage more projects, support more customers, shorten delivery times or avoid the need for an additional hire, the economics change completely.

A more useful ROI equation is:

Time saved → capacity created → additional output → additional margin → enterprise value

Where the Real Opportunity Sits

Companies often look for the most impressive AI application instead of the most valuable one.

The highest-return use cases are often boring: finding the correct technical document, comparing a new customer specification with a previous project, identifying a similar component designed years earlier, or preparing the first draft of a quotation.

None of these applications will create a spectacular demo. But if 30 or 50 engineers repeat these activities every week, the accumulated economic impact can be substantial.

The right question is not:

“What can AI automate?”

It is:

“Where are we repeatedly using expensive human time for work that does not require expensive human judgement?”.

Why AI Agents Matter

This is where AI agents become more interesting than conventional chatbots.

A chatbot answers questions. An AI agent can interact with tools and systems: search databases, retrieve documents, compare information, call APIs, analyse data and execute parts of a workflow.

A chatbot can help an employee write something faster. An agent can help a company execute a process faster.

For example, an agent connected to engineering documentation could retrieve relevant drawings, identify similar past projects, summarise key differences and prepare information for a technical review.

It is not replacing the engineer. It is removing friction around the engineer.

Engineering Is a Natural Candidate

Engineering companies already possess enormous amounts of valuable knowledge: CAD models, drawings, calculations, standards, bills of materials, customer specifications, test reports, quotations, and project histories.

The problem is rarely that the information does not exist. The problem is finding it quickly, understanding its relevance and connecting it to the current task.

For specialized AI engineering solutions, visit AISON AE. Click AISON AE to open https://www.aisonae.com

The objective is not to create another generic AI assistant. The more interesting challenge is to connect AI with real engineering knowledge and company workflows, so people can use the experience the organization has already accumulated.

A general-purpose AI may know a great deal about mechanical engineering. But an engineering company needs systems that increasingly understand its products, machines, drawings, standards, customers and previous design decisions.

Growth Without Proportional Headcount

The largest financial benefit of AI may not come from reducing staff.

It may come from allowing a company to grow without increasing headcount at the same rate.

Suppose an engineering department has 100 people and business grows by 15%. Traditionally, management may assume that headcount must grow accordingly.

But if AI removes enough repetitive work, the department may absorb much of that growth with only a few additional hires.

That creates operating leverage: revenue grows faster than organizational cost.

This is an important difference because AI is frequently presented as a cost-cutting technology. In many engineering businesses, its greater value may actually be its ability to support growth without making the organization proportionally larger and more complex.

Speed Can Be More Valuable Than Labor Savings

Simple ROI calculations also miss speed.

If AI helps an engineering team complete a project four weeks earlier, the value may be much greater than four weeks of labor.

The customer can be invoiced earlier. A quotation can reach the customer before a competitor’s. A product can reach the market sooner.

In many companies, the hidden cost is organizational latency: the time required to move from information to decision, from RFQ to quotation, from problem to solution.

Reducing that latency can be extremely valuable.

Consider quotation speed alone.

Two competitors may have almost identical technical capabilities and similar prices. One takes ten days to analyze an RFQ because engineers must manually search previous projects, drawings and cost data. The other uses AI-supported processes and produces a technically sound quotation in three days.

The second company has not simply saved seven days of labor. It has created a commercial advantage.

That difference is much harder to capture in a traditional ROI spreadsheet, but it may ultimately be worth more than the direct cost saving.

Human Attention Is the Scarce Resource

Experienced engineers and managers are expensive because their judgment is valuable, yet organizations routinely use them for low-value tasks such as searching documents, copying information and reconstructing old decisions.

AI does not need to replace them. It needs to remove enough low-value friction so that more of their time is spent on judgment, creativity, problem solving and customer relationships.

This is also why measuring AI success only through headcount reduction is shortsighted.

If a senior engineer spends 30% less time searching for information and uses that capacity to solve a difficult customer problem, improve a design or prevent a costly engineering mistake, the financial return may be considerably higher than the theoretical salary saving.

The Real Question

Can AI create hundreds of millions of dollars in enterprise value? Potentially, yes.

But there is no automatic bridge between “41% of work can be automated” and “41% more profit.”

Management has to build that bridge.

The companies that obtain the best returns will not necessarily be those buying the most AI licenses. They will be the ones who understand where valuable human capacity is being wasted and know how to convert recovered capacity into more output, faster execution, lower structural costs, or higher margins.

The real question is not:

“How much work can AI automate?”

It is:

“What will we do with the capacity that AI gives back to us?”

That is the point where AI stops being an interesting technology experiment and starts becoming a genuine business advantage.

Source: McKinsey Global Institute, The Economic Potential of Generative AI: The Next Productivity Frontier, 2023.

At Innovation Code, we are working on this exact challenge: connecting AI with real engineering knowledge and real industrial workflows. If you want to understand where AI can create measurable productivity and economic value inside your engineering organization, visit www.innovationcode.com.

From AI Hype to Engineering Value: A Practical Guide

Artificial intelligence is moving through one of the most intense phases of technological expectation in recent history. AI agents, multimodal systems, foundation models, and AI-ready data are all presented as technologies capable of radically transforming business.

The shift from AI hype to engineering value

The hype-cycle curve helps us interpret this moment. It does not tell us which technologies are useful and which are worthless. Instead, it shows the distance that often exists between early enthusiasm and reliable industrial adoption.

This distinction is particularly important in engineering.

In product development, a convincing demonstration is not enough. An AI system must work with complex CAD models, technical drawings, customer specifications, manufacturing constraints, company standards, and regulatory requirements. It must also produce results that engineers can verify, trace, and trust.

The real opportunity, therefore, is not simply to “add AI” to CAD software. It is to create a new engineering operating model in which human designers collaborate with digital teammates capable of supporting complete workflows.

Why AI agents are approaching the peak of expectations

Figure 1. The AI hype cycle—from early expectations to measurable engineering value.

AI agents differ from conventional software because they are not limited to executing a single predefined command.

An agent can receive an objective, break it into individual activities, collect information, use different applications, compare possible solutions, and prepare an output for human approval.

For example, a traditional CAD automation script might generate a family of components using fixed parameters. An engineering agent could potentially receive a customer request and then:

Retrieve similar projects from the company archive
Analyze the customer’s specifications
Identify missing or contradictory requirements
Open the relevant CAD models
Evaluate alternative configurations
Consult internal standards and design rules
Prepare a preliminary bill of materials
Highlight manufacturing and assembly risks
Generate a technical report for the designer

This is a major evolution. However, it is also the reason why AI agents are positioned close to the peak of inflated expectations.

Many companies imagine that an agent can immediately behave like an experienced engineer. In reality, the agent’s performance depends on the quality of the data, the clarity of the process, the reliability of its integrations and the rules governing its autonomy.

A digital teammate without access to structured engineering knowledge is not an engineer. It is a powerful reasoning system operating with incomplete information.

AI-ready data is the real foundation

The position of AI-ready data near AI agents in the curve contains an important message.

Agents cannot deliver reliable results if engineering information is fragmented across disconnected systems.

In many companies, the 3D model is stored in a PDM system, the drawing is saved somewhere else, the calculation report exists as a PDF, manufacturing feedback remains in emails, and important design decisions are known only by a few senior engineers.

This may be manageable for experienced employees, but it is extremely difficult for an AI system.

To make engineering data AI-ready, companies must connect and structure information such as:

CAD models and their revisions
2D drawings and tolerances
Product configurations
Bills of materials
Materials and treatments
Design standards
Calculation reports
Non-conformities and corrective actions
Manufacturing feedback
Lessons learned from previous projects

The objective is not to place every document inside a single database. It is to create a reliable knowledge architecture through which the AI can understand which information is current, which revision is valid, and how different technical objects are related.

This is where PDM, PLM, knowledge graphs and retrieval systems become essential components of the AI strategy.

CAD will become an environment for collaboration, not merely modeling

CAD systems have already evolved from electronic drawing boards into sophisticated product-development platforms. The next step will be their transformation into collaborative environments shared by designers and AI agents.

The agent will not necessarily replace the engineer at the workstation. It will operate around the CAD system, performing activities that currently consume large amounts of engineering time.

A digital teammate could verify whether a model respects company modeling standards, identify missing metadata, compare geometries across revisions, or check whether standard components have been reused correctly.

It could also analyze design intent.

Two components may look geometrically similar but have completely different functional requirements. An intelligent system should not merely recognize shapes. It must understand the relationships between function, geometry, material, tolerance, and manufacturing process.

This is where multimodal AI becomes especially relevant. Engineering knowledge is rarely contained in text alone. It is distributed across 3D geometry, drawings, tables, diagrams, photographs, simulation results and written specifications.

A useful engineering agent must be able to work across all these formats.

From CAD automation to engineering delegation

Companies have automated CAD activities for decades through macros, templates, configurators and application programming interfaces. These solutions remain valuable, but they normally require predictable inputs and predefined logic.

AI agents introduce a different concept: engineering delegation.

Instead of programming every individual step, the company defines an objective, constraints, and approval rules.

Consider the creation of a manufacturing drawing.

Traditional automation can generate predefined views and dimensions. A more advanced agent could analyze the part’s function and manufacturing process, identify the critical features, retrieve the applicable drawing standard, propose dimensions and tolerances, and highlight uncertain decisions for review.

The engineer would not disappear from the process. The engineer’s role would move from manually producing every element to supervising, correcting, and approving a technically informed proposal.

The same principle could apply to:

Design reviews
Drawing verification
Tolerance analysis
Component classification
Standard-part selection
Engineering change requests
Quotation preparation
Technical documentation
Design-for-manufacturing checks

The value is not merely faster modeling. It is the reduction of repetitive coordination around modeling.

Why generic AI will not be enough

A general-purpose AI model may understand engineering language, but it does not automatically understand how a particular company designs its products.

Every organization has its own standards, preferred solutions, risk tolerances, customer requirements, and accumulated experience.

This means that the most valuable engineering agents will not be generic assistants. They will be connected to company-specific knowledge.

An agent working in packaging machinery should understand machine modules, line speeds, format changes, safety constraints and hygienic design. An agent supporting medical-device development must work within a very different environment involving validation, risk management, traceability and regulatory controls.

Competitive advantage will not come only from access to the most powerful foundation model. Most companies will eventually have access to comparable models.

The advantage will come from combining those models with proprietary engineering data, well-designed workflows and specialist expertise.

Human accountability remains essential

Engineering decisions affect cost, performance, reliability and safety. Therefore, autonomy must always be proportional to risk.

An AI agent may be allowed to classify components, prepare reports or suggest design alternatives autonomously. It should not necessarily be authorized to release a drawing, change a safety-critical tolerance or approve a product configuration without human validation.

AISON AE provides practical guidance for managing AI risks and incorporating trustworthiness into AI systems.

Every agent should have a clearly defined role:

What outcome is it responsible for?
Which systems can it access?
Which decisions can it make?
When must it request approval?
How is its performance measured?
Who is accountable for its output?

The key question is not whether an AI agent can perform an activity.

The key question is under which technical and organizational conditions it should be permitted to perform it.

This is the difference between uncontrolled automation and industrial-grade AI.

The trough of disillusionment will eliminate weak projects

Many AI initiatives will fail after the current phase of enthusiasm.

Some companies will discover that their data are unusable. Others will automate processes that were poorly designed from the beginning. Some will purchase attractive tools that cannot integrate with their CAD, PDM or PLM environments.

This period of disillusionment is not necessarily negative. It will separate demonstrations from real engineering solutions.

Successful projects will normally start from a specific business problem: reducing drawing lead time, improving quotation accuracy, reusing previous designs, detecting design errors earlier, or preserving expert knowledge.

They will also measure concrete results rather than generic “AI adoption”: hours saved, rework avoided, errors detected, development time reduced, and knowledge recovered.

Turning the hype cycle into an engineering roadmap

The chart should not discourage investment in AI agents. It should encourage disciplined investment.

Engineering companies should begin with limited but valuable responsibilities, connect agents to reliable information and maintain human control over high-impact decisions.

The objective is not to create an artificial engineer overnight. It is to progressively build digital teammates that can understand the company’s products, support its designers and improve the continuity of its engineering processes.

The companies that succeed will not be those that experiment with the largest number of AI tools. They will be those that transform their CAD data, engineering knowledge and workflows into an intelligent operating system for product development.

About Innovation Code

Innovation Code is a Thai-Italian engineering and AI company that helps industrial companies bring products to market faster. By combining European engineering expertise, AI-powered development and Asian manufacturing capabilities, we turn ideas into mechanical designs, animated 3D concepts, prototypes and production-ready solutions.

Discover how Innovation Code can help your team accelerate product development and move from concept to production: www.innovationcode.com