Chapter 045　What Is Enterprise Transformation in the Age of AI?

No term in management has been worn harder than transformation. It appears in every mid-term plan and in almost every message from the chief executive. What it names differs enormously from company to company. Some call a redrawn organization chart a transformation. Others call replacing the core system a transformation. This chapter is about the relationship between transformation and redefinition. The two are not synonyms. The difference decides success and failure in the Age of AI. We rebuild here the working method of transformation. The subject is not what to begin. It is what to continue, and how.

1 The question — why it arises now

Transformation has a clear lineage. In the middle of the twentieth century, Lewin described organizational change in three stages. Unfreeze, change, refreeze. That scheme treated change as an emergency wedged between two periods of stability. Behind it sat an assumption: that a stable state exists before the change and another after it. The 1990s brought the reengineering wave, a method for redesigning business processes from a blank sheet. Change management established itself as a practical discipline at roughly the same time. How to handle resistance. How to bring stakeholders in. Techniques accumulated for turning transformation into a manageable program of work. That accumulation is still valid. We do not reject it. But all of it shares a single assumption. Transformation has a beginning and an end. Because there is a beginning, urgency must be manufactured to move people. Because there is an end, results must be embedded and refrozen. The existing literature on transformation was built with precision on top of that assumption. Does the assumption still hold in the Age of AI? That is the question of this chapter. If it does not hold, the techniques can stay while the working method around them is rebuilt. Use the techniques without rebuilding the method, and the enterprise arrives at the wrong place by the correct procedure. There is a second, practical reason to ask now. Many companies are embarking on their second or third company-wide transformation. The first was the core system. The second was digitization. The third is AI. Executives report the same fatigue. That fatigue is not laziness. It comes from having designed transformation as a thing that ends.

2 Conventional answers and their limits

Three answers about enterprise transformation are widely shared today. All three have practical evidence behind them. All three stand on the same assumption. The first answer: “Transformation begins by creating a sense of urgency” This is the most famous prescription. People do not move while they are satisfied with the present. So make the danger of the present visible. Competitor moves, a shrinking market, technological change. Bring the organization to understand that standing still is the riskier option. The prescription is correct. Organizations carry inertia. Breaking inertia takes force from outside. Many successful transformations did in fact begin with shared urgency. But urgency decays. A transformation raised on urgency stalls the moment the urgency thins out. Urgency also has a side effect. When it runs high, organizations turn defensive. Decisions that avoid loss increase. Decisions that bet on possibility decrease. Urgency works for defending an existing business. It is poorly suited to designing a new future. The second answer: “Transformation has an order that must be respected” The second conventional answer treats transformation as a program of work. The best known version is Kotter’s eight stages. Raise urgency. Build a guiding coalition. Create a vision and strategy. Communicate the vision. Enable people to act. Generate short-term wins. Consolidate gains and produce more change. Anchor the new approaches in the culture. Those eight stages are practical knowledge derived by inverting the patterns of failure. Transformations that skip steps do fail, and that has been confirmed in practice. We accept the value of the sequence. The problem is the last stage. The program closes on “anchor.” Anchoring means creating a new stable state. The eight stages assume the enterprise arrives somewhere. Because there is an arrival point, a schedule can be written. Because a schedule can be written, a budget follows. The third answer: “Transformation is complete once it is embedded” The third conventional answer is the concept of completion. A transformation project has a start date, a target, and a closing report. When it closes, the program office is dissolved and its members return to their old departments. This treatment is rational. Corporate resources are finite. A company cannot hold the attention of the whole organization on one theme indefinitely. Deadlines are what gather resources. But a structural consequence follows. After the transformation ends, the enterprise returns to a state of not changing. Returning is treated as proof of success. So every time the next change arrives, the enterprise starts again from zero. What do the three conventional answers share? All of them treat transformation as an event bounded in time. A beginning, a climax, an end. That assumption holds only in a world where change arrives in discrete pieces.

3 Redefinition — transformation is one interval within

redefinition We set out the relationship redefinition as follows. between transformation and Transformation is the interval in which an enterprise moves from its current design to a different one. Enterprise Redefinition is the continuous organizational process of performing that move repeatedly. Transformation is a subset of redefinition. Not the reverse. Redefinition must never be read as “a bigger transformation.” The two differ not in scale but in their treatment of time.

3.1 Why the assumption stopped holding

The assumption that transformation has a beginning and an end holds only when three conditions are met. The first condition is that environmental change is discrete. If change is an event that arrives once every few years, emergency and normality can be separated. But technology, customer expectations, regulation, and the criteria capital markets apply are all moving at once. When change is continuous, the boundary between emergency and normality disappears. The second condition is that a redesigned state stays optimal for some period. This is the premise of refreezing. AI capability, however, is refreshed on a scale of months. Last year’s optimal division of work between people and AI is not next year’s. From the moment a design is frozen, it begins to age. The third condition is that the cause of change sits outside the enterprise. A wave arrives from outside, and when it passes the water settles. But AI is an external wave and, at the same time, the instrument with which the enterprise creates change. When cause and instrument are the same thing, change becomes self-propagating. All three conditions have collapsed. Management that designs transformation as a discrete event is therefore designing on a lost premise.

3.2 The techniques of transformation are not discarded

We want to head off a misreading. The premise has collapsed; the knowledge of change management has not become worthless. Urgency still moves people. A guiding coalition is still necessary. Short-term wins still sustain the organization’s confidence. What must change is not the techniques. It is the working method around them. The difference is whether these techniques are used for a one-time mobilization or built into a mechanism that runs permanently.

3.3 The fault line between Level 3 and Level 4

This difference has a precise location in the Enterprise Redefinition Maturity Model (ERMM). → Vol. V, Ch. 044. Level 3 is the Transformation Enterprise. It recognizes that existing business models require substantial redesign. Enterprisewide initiatives emerge, and purpose begins to evolve. That is already a high standard. But transformation still occurs periodically, and the organization continues viewing redesign as a project rather than a permanent organizational capability. Level 4, the Continuous Redefinition Enterprise, is a qualitative shift. Transformation is no longer an exception. Enterprise redesign is embedded within normal management processes. Continuous strategic sensing. Integrated human-AI collaboration. Adaptive structures. Dynamic capital allocation. Learning-centered leadership. Organizations at this level increasingly redesign themselves before external disruption requires it. The gap between the two is not a gap in skill at transformation. A Level 3 enterprise has the capability to execute transformation projects successfully. The gap is in where transformation is kept. Level 3 keeps it outside the organization. A dedicated program office, a time-limited budget, a special governing body. Level 4 keeps it inside. Redesign happens within the ordinary budget, the ordinary personnel system, and the ordinary meetings. So the move from Level 3 to Level 4 does not happen by accumulating more capability. However many excellent transformations a company runs, repetition alone does not produce Level 4. The move happens only by changing the design of the organization’s ordinary days.

3.4 The five dimensions do not change at the same speed

The five dimensions of redefinition are Purpose, Business, Organization, Capital, and Leadership. They do not change at the same frequency. Core Purpose may remain stable while its expression and realization evolve. Businesses and structures may be rewritten within a few years, and the core still stands. Continuous Redefinition does not mean shaking everything all the time. It means deciding what will not change, and then keeping the rest in motion. Get this wrong and continuous redefinition becomes mere disorder. An organization that keeps changing and an organization that cannot settle are different things. Continuous Redefinition therefore refers to continuous managerial attention and periodic reassessment, not constant alteration of every organizational element. Three notes travel with the maturity model, and all three apply here. Progression is not linear. An organization may possess Level 4 AI capability while remaining Level 2 in leadership. Purpose may operate at Level 5 while Business remains at Level 3. What the model evaluates is organizational coherence rather than isolated excellence. Maturity is assessed across all five dimensions, in balance. Organizations with exceptional technological capability but weak leadership redesign cannot achieve higher maturity. Strong purpose without adaptive organizational systems remains insufficient. And Level 5 is not a target to be reached as fast as possible. Different industries may require different levels of organizational adaptability.

4 Structure — the seven-stage process, and the division

between people and AI Continuous redefinition does not run on exhortation. It runs on structure.

Figure V-3　. The seven-stage Enterprise Redefinition Process

4.1 The seven-stage process

Enterprise Redefinition consists of seven stages. Recognize → Learn → Redefine → Design → Execute → Measure → Redefine Again Set this beside the eight-stage account of transformation. The largest difference is at the end. The eight stages close with anchoring. The seven stages open with redefinition. That single point separates a project from a permanent state. For each stage, we separate what people carry from what AI carries. First Principle 4 is the criterion. AI Optimizes. Humans Define. AI optimizes; humans define value, purpose, and direction. Stage one, Recognize. The starting point is noticing that the assumptions supporting the current business model may no longer be valid. Technological shifts, changing customer expectations, geopolitics, regulation, capital market signals, societal change. The central question is one sentence. “What assumptions about our enterprise are becoming obsolete?” AI carries the processing of external information at volume. It can scan more signals than a person can read. People carry interpretation. Telling a passing fashion apart from a structural shift that demands enterprise redesign is a judgment that cannot be delegated. Stage two, Learn. Recognition alone changes nothing. Observation has to be converted into understanding. Learning here is more than acquiring knowledge. It includes experimentation, organizational reflection, scenario analysis, learning from the ecosystem, dialogue with customers, technological exploration, and simulation by AI. Organizations fail here not because information is unavailable. They fail because existing patterns of thought block any meaningful reinterpretation. AI accelerates simulation and the generation of options. People question their own pattern of thought. Learning Is the Ultimate Competitive Advantage. Stage three, Redefine. This is the conceptual center of the framework. Ordinary strategic planning selects among existing options. Redefinition questions the assumptions that produced those options. The first object of questioning is whether the Core Purpose still holds. Then the expression of Purpose, the boundaries of the business, the architecture of the organization, capital allocation, and the responsibilities of leadership. The question is not how to improve the current enterprise. It is “What should this enterprise become?” In the Purpose dimension, redefinition may result in reaffirmation, reinterpretation, or fundamental revision. This is the stage where distinctly human capability contributes beyond AI’s analysis. It takes imagination, strategic judgment, and thinking directed at the future. Stage four, Design. Conceptual redefinition is translated into organizational architecture. Business model, organizational structure, decision structures, governance, human-AI collaboration, capital allocation, performance measurement, and technology infrastructure. The object of design is coherence. Every component must reinforce the future enterprise drawn in the previous stage. AI can test a design for internal consistency. People decide what the axis of coherence is. Stage five, Execute. Conventional management has treated execution as the decisive phase of transformation. Enterprise Redefinition does not. Execution is indispensable, but it is not a terminus. Execution becomes experimentation. It functions as an experiment through which the organization tests redesigned assumptions under real-world conditions. What matters is adaptiveness, not fidelity to the plan. AI carries monitoring and adjustment. People carry the design of the experiment and the decision to stop it. Stage six, Measure. Measurement judges whether the redesign is actually producing Future Value. Conventional measurement has favored backward-looking financial indicators: revenue, operating profit, productivity, shareholder returns. Enterprise Redefinition extends measurement toward forward-looking indicators. Organizational adaptability, AI collaboration capability, innovation capacity, ecosystem influence, learning speed, capability development, and long-term strategic resilience. Financial performance still matters. But past performance alone cannot tell you whether the enterprise is better positioned for the future. AI can compute the indicators. People choose which indicators to compute. Stage seven, Redefine Again. This stage is what settles the difference from conventional transformation theory. Success in execution does not end the process. Each cycle produces new knowledge, and technological conditions and competitive environments keep moving. The organization therefore enters the next cycle of redesign immediately. No organizational design is permanently optimal. Competitive advantage arises from the capability to keep redefining. Enterprise Exists to Redefine Itself.

4.2 The Enterprise Redefinition Cycle

Drawn at a larger scale, in the language of management, the seven stages become the Enterprise Redefinition Cycle. Future Vision → Enterprise Redefinition → Execution → Learning → Future Value → (return to Future Vision) The cycle begins from Future Vision. Conventional management begins from current performance. Enterprise Redefinition begins from a desired image of the future. Future Vision answers three questions. What future should exist? Why is that future desirable? What role should the enterprise play within it? Forecasting predicts the future. Future Vision creates it. Confuse the two and the entrance to the cycle is replaced by prediction. A cycle that begins from prediction merely carries the enterprise in the direction the environment already indicates. The cycle has no final state. The objective is not organizational stability but the continuous creation of Future Value. Each turn changes the enterprise itself. This is evolution, not repetition.

4.3 The cycle compounds capability

Why does a permanent state beat a project? The reason is compounding. An organization that has run the cycle repeatedly accumulates strategic knowledge, experience in redesign, working practice in AI collaboration, and a future-oriented culture. Redesign strengthens the capability to redesign. The structure shows up in the formula for Future Value Creation Capability. FVCC = Purpose × Learning × Redefinition × AI Integration × Ecosystem × Capital Allocation × Trust The relationship is multiplicative: weakness in any single capability weakens the whole, so purpose, AI, and capital are each individually insufficient, and Future Value emerges only when all seven reinforce one another. If any single term is zero, the entire product is zero. In an enterprise that treats transformation as a project, the Redefinition term rises for the duration of the program and returns to zero when it closes. The longer the zero periods, the longer Future Value Creation Capability stays at zero. That is the theoretical reason for demanding a permanent state.

5 What it looks like in practice — the structure of

failure, and what has to change

5.1 Why transformations fail

Practitioners have discussed the high failure rate of transformation for a long time. The causes usually named are insufficient executive involvement, resistance on the front line, unclear objectives, and inadequate resources. Each observation is accurate. Each is a symptom of a deeper structure. The structural cause is a skew in resource allocation. Enterprises concentrate resources on execution and spend almost no time on recognition and learning. The reason is simple. Execution can be measured. How many people were assigned, how many items were closed, when it finished. All of it fits on a schedule. Hours spent in a meeting that doubts an assumption are hard to report as an achievement. As a result, many transformations start at stage three. Recognition and learning are skipped, and the conclusion of redefinition is set down directly. The conclusion exists first, and the verification of the assumptions that produced it does not exist at all. Proceed from there into design and execution, and execution runs with precision. The schedule holds. But nothing guarantees that the destination is the right place. A transformation that skipped recognition strays further the faster it runs. There is a second consequence. An enterprise that has not invested in recognition and learning has no forward-looking indicators. So it can only describe results in revenue and profit. The cycle then fails to move to the next turn and is terminated partway. We therefore state the structure of failure this way. Transformations do not fail because execution is poor. They fail because no resources went into recognition and learning, so execution ran without a settled direction.

5.2 What actually changes when transformation becomes

permanent What changes inside the organization when transformation moves from project to permanent state? Four concrete instruments. Budget, personnel, meetings, and appraisal. Until these four change, a permanent state is only a declaration. Budget. Abolish the line item called the transformation budget. More precisely, move it from a time-limited special allocation to a permanent one. In most companies, transformation money is treated as a one-off investment. Special treatment is a declaration that the thing has an end. Put in its place a permanent share of allocation directed at Future Value. Capital Exists to Create Possibility. A budget table is a record of which future the enterprise chose. A budget table nearly identical to last year’s means the enterprise chose last year’s future. Personnel. Dissolve the transformation office, or never create one. Not to weaken the push, but to stop the push from being quarantined in a special place. As long as a dedicated unit exists, the main body will conclude that this is not their job. Put in its place redesign written into the job description of the business heads. The responsibility for running a business and the responsibility for redesigning it sit with the same person at the same time. In an organization where people do not move, assumptions do not move either. Meetings. Change the composition of the executive agenda. In most companies, the bulk of the agenda is reporting and confirmation. AI can produce the reports and can perform the confirmation. There is no longer a reason to spend human hours in a room on reporting. Add one permanent agenda item instead. Which of our assumptions is becoming obsolete right now? This is the central question of Recognize. It must never be an occasional item. Only when it appears at every regular meeting does recognition become an organizational habit. Appraisal. The appraisal system is the last gate. As long as the system rewards the old behavior, people will produce the old behavior. Most appraisal schemes are built on attainment against this period’s targets. That design penalizes time spent on recognition and learning. Two changes are needed. First, include forward-looking indicators in appraisal. Second, stop penalizing failed experiments. If execution is experimentation, failure is information. A system that penalizes the person who brought information back stops the organization from learning. The four instruments are not independent. Change the budget alone and, with appraisal unchanged, the front line will not move. Change the meetings alone and, with personnel unchanged, the discussion is never implemented. Here too, the object of design is coherence.

5.3 What a permanent state looks like

What can be read from public information is the following. One software company moved its center of gravity from selling products to providing cloud services. It also stated explicitly that a culture of trying to learn everything ranks above a culture of knowing everything. Business redesign and a declaration placing learning at the center of value happened together. One video streaming company moved from renting DVDs by mail to streaming, and then to production. What deserves attention is not the sequence but the frequency. At each shift, the previously dominant business contracted. One large IT company has moved its center of gravity repeatedly across more than a century, from building calculating machines to services and then to foundational technology. The same corporate name has carried entirely different business portfolios many times. What these have in common is not skill at transformation. It is that the decision to let something go has been made repeatedly. Redefinition is not the act of adding something new. It is the act of deciding what to protect and what to release. In financial terms, the decision to release almost always shows up as a cost in the current period. Whether an enterprise can make that decision is therefore a question of institutions, not executive nerve. Only companies with all four instruments in place can let go repeatedly. And only companies that can let go repeatedly redesign themselves before external disruption requires it.

6 Questions for the executive

The argument, in one line. Enterprise transformation in the Age of AI is not a project with a beginning and an end. It is running the cycle that returns from recognition to redefinition as an ordinary management process, without stopping. Launch on urgency, manage by program, close by anchoring. That working method belongs to an age when change was discrete. In an age of continuous change, the mechanism that refuses to stop matters more than the technique of starting. Three questions to close. Each can be answered at your next executive meeting. Question 1 — Of the time you invested in your most recent transformation, what share went to recognition and learning? In most companies the share does not reach one tenth. The rest goes to design and execution. If that is your case, the transformation never verified its direction. Check the resources you spent on verifying direction, not on speed. Question 2 — When your current transformation ends, what will you dissolve? If a program office is scheduled for dissolution, the enterprise is treating transformation as a project. That is not in itself an error. Level 3 of the maturity model is already a high standard. But you need to decide now who carries the next act of recognition after the dissolution. Question 3 — Of budget, personnel, meetings, and appraisal, how many have you rebuilt on the assumption of redesign? Zero, and the transformation is at the stage of declaration. One or two, and the instruments are contradicting each other. All four, and redefinition is starting to become ordinary. An organization’s real intent shows up in the design of its systems. None of the three questions asks how to make a transformation succeed. All three ask what remains after the transformation ends. What should remain is not a new organization chart and not a new system. It is the capability to perform the next redefinition faster. We do not reject transformation. Transformation is necessary. But management that tries to bring transformation to an end begins accumulating the next delay the moment it succeeds. Leadership Means Designing the Future. Design is not work that finishes once. Design, test, measure, and design again. Not stopping that cycle is the working method of transformation in the Age of AI. And whether the cycle stops or continues is not decided by AI. It is decided by the executive.

In brief

Enterprise transformation in the Age of AI is not a project with a deadline; it is a cycle kept turning.
Transformation is one interval within redefinition. Not the reverse. Redefinition is not a bigger transformation.
What separates Level 3 from Level 4 is not skill at transformation but whether transformation sits inside or outside the organization.
Until budget, personnel, meetings, and appraisal are rebuilt, transformation goes no further than declaration.

Key concepts

Enterprise Redefinition / Enterprise Redefinition Cycle / Enterprise Redefinition Maturity Model (ERMM) / Enterprise Redefinition Capability (ERC) / Future Value

The chain of ideas

Recognize → Redefine → Execute → Measure → Enterprise Redefinition Capability

Related first principles

Principle 4 — AI Optimizes. Humans Define. Principle 5 — Learning Is the Ultimate Competitive Advantage. Principle 6 — Enterprise Exists to Redefine Itself. Principle 9 — Leadership Means Designing the Future.

Related chapters

Vol. V, Ch. 044 “What Is the Enterprise Redefinition Maturity Model (ERMM)?” — defines Levels 3 and 4 and what the gap between them means
Vol. V, Ch. 042 “Why Are Enterprises Redefined?” — treats in detail the recognition that starts the cycle
Vol. I, Ch. 010 “Which Companies Succeed with AI, and Which Fail” — the patterns by which AI adoption fails on the ground
Vol. VI, Ch. 057 “How to Carry Out Enterprise Redefinition” — the procedure for embedding the cycle in ordinary systems

Papers and companion volumes

Kadowaki, N. (2026a). Future Value Theory: A Management Framework for Enterprise, Capital, and Society in the Age of AI. VURA Working Paper Series. SSRN: https://ssrn.com/abstract=7120980 / Zenodo: https://doi.org/10.5281/zenodo. 21255662
Kadowaki, N. (2026b). Enterprise Redefinition: Toward an Enterprise Evolution Theory for the Age of AI. VURA Working Paper Series. (Published on Zenodo; under review at SSRN)
100 Questions on Management in the Age of AI, #045 “Enterprise Transformation in the Age of AI”

Chapter 045 What Is Enterprise Transformation in the Age of AI?