Chapter 057　How to Carry Out Enterprise Redefinition

On Enterprise Redefinition we have so far described what gets redefined, dimension by dimension. Business, organization, people, brand, customer value, competitive advantage, the executive, culture, governance, and investment. The content is complete. But content being right and content moving inside a company are two different things. This chapter takes up the movement itself. Who carries it. In what order agreement is built. Where resistance appears. How to hold through the period of pain that arrives before results. And, when it stops, how to start it moving again.

1 The question — why it arises now

Most redefinitions stop for reasons that have nothing to do with content. What we have seen across many organizations is the same scene. A sound policy is carried in by an unsound method, and then quietly dies. The policy document is precise. The analysis is not wrong. Six months later nobody is talking about it. What happened? What happened was a failure of movement. The order of agreement was wrong. The people who should have carried it did not. The kind of resistance was misread. Nothing had been designed to survive the period before results appear. None of these is a problem of content. All are problems of method. Do not read the word method narrowly here. This is not a chapter about building a schedule. Anyone can build a schedule. What cannot be built by just anyone is the design of who is drawn in, and when. An enterprise does not move in the shape of its org chart. An enterprise moves in the shape of its agreements. Where agreement has not been reached, instructions are processed formally and nothing changes in substance. Managing the progress of a redefinition is therefore, in substance, managing agreement. The Enterprise Redefinition Process names the stages that movement passes through. Recognize → Learn → Redefine → Design → Execute → Measure → Redefine Again Recognize asks: what assumptions about our enterprise are becoming obsolete? Redefine asks: what should this enterprise become? Those two questions are the pivots of the cycle. This chapter is about what has to be true inside an organization for the cycle to turn at all. Let us fix the scope. The relationship between transformation and redefinition, and the content of each stage, have already been set out (Vol. V, Ch. 045). So has the time horizon on which the theory is loaded onto an executive’s calendar (Vol. IV, Ch. 037). This chapter takes up only the practice of people, agreement, and resistance.

2 Conventional answers and their limits

Three answers about how to carry a redefinition through are widely shared in practice. Each has some effect. Each stands on the same misreading. The first answer: “Build a strong central team” The first answer is an answer about structure. Create a dedicated unit that owns redefinition for the whole company, staff it with your best people, and place it under the CEO. Give it authority, a budget, and a deadline. There is a reason for this prescription. Work that is nobody’s work does not get done. Naming an owner is the minimum condition for movement. Companies that stand up a dedicated unit start faster than companies that do not. The prescription always produces one side effect. Redefinition becomes that unit’s job. The operating businesses stop carrying it as their own problem. The better the unit is, the sharper the separation, because a capable unit can produce answers by itself. The main body then stops thinking. A body that has stopped thinking stops being the subject of redefinition. What is no longer a subject does not get redefined. The second answer: “Tell the whole company at once” The second answer is an answer about communication. Once the policy is set, announce it quickly, in identical words, to everyone at the same time. Leaving an asymmetry of information breeds speculation. So: simultaneous, and transparent. This is partly right. Speculation is poison in an organization. On anything touching headcount, silence is the worst possible message. The trouble sits in the word simultaneous. The content of a redefinition changes meaning with the listener’s position. To the executive team it is a story about choice. To middle management it is a story about whether their unit survives. To the front line it is a story about their own job. One text is exposed to three different questions. Distribute the same words at the same moment and the most anxious reading becomes the dominant one. This is why, in many companies, the announcement of a redefinition is heard as advance notice of job cuts. The content is not wrong. The order is. The third answer: “Overcome resistance by persuasion” The third answer is an answer about resistance. Explain patiently to those who resist. Understanding produces acceptance. Acceptance produces movement. This premise treats resistance as a shortage of information. But most resistance on the front line does not come from not understanding. It comes from understanding well. People resist because, having understood, they can see what they will lose. There is a further difficulty. Some resistance is correct. The first party to find the flaw in a policy is usually the front line. Management that treats all resistance as an obstacle to be cleared destroys its highest-value information. What do the three answers share? All three treat movement as a problem of communication and execution. Produce the right answer upstream, push it downstream, remove friction. That picture works for problems with Redefinition is not such a problem. one determinate answer.

3 Redefinition — carrying it through means designing

agreement and burden We define the movement of a redefinition as follows. Carrying a redefinition through means designing at which layer of the enterprise, in what order, agreement is built about what — and who bears how much of the resulting burden, for how long. Not communication. Not execution. The design of agreement and burden.

3.1 Why agreement

A redefinition always lets something go. A business, a practice, an authority, a priority in the allocation of resources. The decision to let go cannot be executed by instruction. Instruction can only produce the appearance of letting go. Organizations have a capacity to comply formally while preserving the substance. This capacity does not come from bad faith. It is a normal function by which an organization protects itself. To move the substance, therefore, you need agreement about the substance.

3.2 Why burden

Redefinition costs. Not only in financial terms. The burden we mean here is time, attention, psychological safety, and standing inside the company. Move people into a new business and the sending unit loses strength. Change the format of an approval and the front line loses a familiar routine. Change the axis of appraisal and the people who scored well on the old axis lose rank. Each of these is a real loss, borne by someone specific. Designing movement means the executive team deciding, on purpose, who bears how much of that loss. Decide nothing and the burden collects automatically at the weakest point. In most companies that point is middle management.

3.3 Who carries it — three roles, kept apart

Three roles. Conflate them and the structure collapses. The first role is the owner. The person who decides what is redefined and what is protected. This can be no one but the executive in charge. Why it cannot be delegated has been argued already (Vol. IV, Ch. 037). What we add here is visibility. The owner must not only decide but remain present where the decision is contested. An owner who never appears in the room where people object is not recognized as the owner. The second role is the implementer. The person who actually builds the redefined shape inside their own business. This is the business leader. This is the role most often missing. A structure in which business leaders are not implementers is a structure that has placed redefinition outside the main body. The third role is the secretariat. The people who record, standardize the formats, observe, and make the state of progress visible. They do not judge. The moment a secretariat begins to judge, the structure slides into the proxy pattern. The relationship among the three maps onto the Leadership Formula. Leadership = Purpose × Question Design × Capital Allocation × System Architecture × Trust This is multiplication, not addition. If any single term is zero, the entire product is zero, and no other term compensates. The owner carries Purpose and Question Design, and signs the capital allocations. The implementer carries System Architecture at the level of the front line. Trust arises from the relationship among the three. Zero anywhere and the structure is form without substance.

3.4 Should you create a dedicated unit?

This is the question we are asked most often. Our answer is a conditional yes. You may create one. Only if three conditions hold. First, write the condition for its dissolution at the moment you create it. A date or a state will do. A unit without one begins to treat its own survival as the objective. Second, limit its authority to recording, formats, and observation. Do not let it decide on behalf of the businesses. The moment it does, the main body stops thinking. Third, take people out of the mainstream and put them back into it. A dedicated unit used as a holding pen for surplus staff is treated lightly inside the company. Send in the next generation of business leaders and return them to a business at the end of their term, and those people become live circuitry. Whether a dedicated unit is appropriate also depends on where the enterprise sits on the Enterprise Redefinition Maturity Model (ERMM). In an Improvement Enterprise, standing one up can be the first breach in the wall. In a Continuous Redefinition Enterprise, standing one up signals regression. The same question does not have the same answer. Three notes travel with the ERMM and must be kept in view here. First, progression is not linear: organizations frequently display characteristics of several levels at once, so the model evaluates organizational coherence rather than isolated excellence. Second, maturity is read across all five dimensions in balance; exceptional technology with weak leadership redesign does not produce higher maturity. Third, Level 5 is not a target to be reached as fast as possible — different industries require different levels of adaptability.

4 Structure — the order in which agreement is built

Order has reasons. Copy the order without the reasons and the form is identical while the result is not.

Figure VI-1　. The Enterprise Redefinition Cycle

4.1 The principle behind the order

Two principles. First, build agreement in the order in which burden is borne. Start with the layer that absorbs the largest loss. A redefinition in which the top has absorbed no pain is always refused below. Second, place the irreversible decisions first. What to abandon is irreversible. How to communicate is reversible. A sequence that begins with reversible decisions destroys every agreement it has accumulated the moment an irreversible one appears. From these two, the order follows: the executive team, the board, middle management, the whole company.

4.2 The first agreement — the executive team

What the executive team must agree on is not the picture of the future. Pictures of the future attract little opposition and therefore carry no substance. What must be agreed is what will be abandoned. Three items, specifically. Which businesses, practices, or allocations will be cut back. Who loses as a result. Which member of the executive team absorbs that loss. An agreement that skips the third item is not agreement. It is approval. One practice helps here. Each person writes independently, and the writings are then compared. Start with discussion and the group converges on the proposal of the most senior person, leaving dissent off the record. Dissent that never reached the record always returns at the execution stage. Take time over this agreement. Weeks here save years later.

4.3 The second agreement — the board

Next is the board. The reason for placing it ahead of middle management is plain. A redefinition the board has not agreed to always stops partway. What the board needs is not the detail of the plan. It is a request to change the basis of oversight. During a redefinition, financial indicators deteriorate for a time. Keep oversight on the old basis and the board becomes the party that stops the work. State three things explicitly. What will deteriorate, and by how much. How long that period will last. What the board should watch, during that period, to judge progress. A great many executives arrive without the third. Without it, the board has nothing to look at but the existing financials. The governance side of this argument is handled separately (Vol. VI, Ch. 055). What matters here is only the order. The board’s agreement is secured before middle management is briefed.

4.4 The third agreement — middle management

The third layer is middle management. This is the hardest gate. The reason is structural. Managers must translate a policy handed down from above into words their people can act on. Without that translation nothing moves. At the same time, managers are the layer best adapted to the current organization. They hold their positions because they produced results inside the current machinery. Managers are therefore both the executors of the redefinition and the layer with the most to lose. Any method that ignores this doubleness fails. Three things must be said to them. First, not why we are changing, but what changes and how. Second, what your unit lets go of and what it gains. Third, on what basis you yourself will be appraised. Asking for cooperation while leaving the third vague is handing over the burden without the reward. Most managerial resistance starts there. The form matters as well. Brief managers in dialogue, not by circulating a document. Split the sessions if the numbers are large. A briefing that produces no questions is not evidence of agreement. It is evidence that agreement has been given up on.

4.5 The fourth agreement — the whole company

Last comes the company. Only at this point does a simultaneous announcement mean anything. If the three layers above have agreed, employees hear the same account from their own manager. Consistency between the executive message and the manager’s explanation is what trust is made of. Two disciplines govern the company-wide message. First, do not present the undecided as decided. Say that what is open is open. One assertion later reversed erases the credibility of everything said before it. Second, do not dodge the employment question. The first thing an employee thinks after hearing about a redefinition is what happens to their own job. An announcement that does not touch this reads, by not touching it, as an answer. We have treated that question elsewhere (100 Questions on Management in the Age of AI, #046).

4.6 The order is not one-way

We have set out four layers in sequence. Movement is not one-way. If dialogue with managers exposes a flaw in the plan, go back to the executive agreement. If a board comment changes what will be abandoned, run the order again. Going back is not failure. A process that cannot go back is the dangerous one. A process that starts ignoring reality in order to protect what was already announced has stopped learning from that point on. Learning Is the Ultimate Competitive Advantage.

5 What it looks like in practice — resistance, the valley,

and restarting

5.1 Resistance divides into three

Resistance must not be handled as one thing. We divide it into three, because the responses are entirely different. The first type is resistance from vested interest. People who benefit from the current machinery act to protect it. Budget authority, influence over appointments, standing inside the company. None of this is stated openly. The stated reason always wears different clothing. “It is premature.” “The front line will be thrown into confusion.” “Customers will leave.” There is a test. If changing the conditions does not change the conclusion, the resistance is vested interest. Where a concern is real, addressing the concern moves the conclusion. Where it does not move, the stated concern was a pretext rather than a reason. The second type is resistance from anxiety. I do not know what becomes of me. I am not confident I can acquire the new capability. Perhaps decades of experience are about to become worthless. This is the most common resistance in any organization, and the most often misread. Anxious resistance frequently takes the form of indifference. Nothing is said against the plan; nothing moves. People wait for instructions and process exactly what they are given. Reading this state as a lack of motivation is a mistake (100 Questions on Management in the Age of AI, #044). The third type is resistance as legitimate concern. The plan has a real flaw and the person who found it first is speaking up. Equipment constraints, regulatory requirements, customer contracts, dependencies in existing systems. This is information invisible to those upstream. The three arrive mixed together, in the same meeting, in the same words. They can only be told apart by structure, not by content.

5.2 How to meet each of the three

Meet vested interest with design, not persuasion. More discussion will not move the conclusion. What moves it is the structure of the interest being protected. Change the unit of budgeting. Change the axis of appraisal. Change the route of approval. Change the structure and the same person’s rational behavior changes. But do not treat it as a defect of character. Protecting a vested interest is behavior the existing system has rewarded. Management that blames individuals for what the system rewarded will not have its next system respected either. Meet anxiety with speed of resolution, not volume of information. The source of anxiety is not change. It is the persistence of an unresolved state. Communicate what has been decided, in the order it was decided, quickly. For what has not been decided, say when it will be. Then give a concrete path on capability. What capability does the new work require. Where can it be acquired. How will appraisal work in the meantime. An abstract call to keep learning does not reduce anxiety. Meet legitimate concern by revising the plan. This is not resistance. It is information. The process to be suspicious of is the one in which no legitimate concern appears. Nobody points out a flaw not because the plan is flawless, but because the organization has learned that pointing it out is futile. So create one instance early. Change the plan because the front line said so, and publish the fact that you changed it. Whether that single instance exists determines the quality of everything you are told afterward. Trust Compounds Faster Than Capital. And it is lost faster still.

5.3 The valley — when the pain arrives first

A redefinition always has a valley. The valley is the period in which the returns of the old machinery have begun to fall and the returns of the new have not yet arrived. Financial indicators deteriorate. Front-line load rises. The mood inside the company turns heavy. From outside, it looks like failure. The valley is not failure. It is a structural consequence. The reason is simple. The decision to let the old go is executed first, and the new takes time to stand up. If both happened at once there would be no valley. They do not happen at once. The depth and length of the valley vary widely by industry and by the scope of the redefinition. Do not import another company’s timeline. What matters is that the valley is declared before it arrives. Deterioration that was declared in advance is received as part of the plan. Deterioration that was not is received as a failure of management. The same numbers carry opposite meanings depending on whether they were declared.

5.4 Four supports for holding through the valley

First, prepare grounds for judgment other than financial ones before you enter. As long as you watch only financial indicators, withdrawal always looks rational inside a valley. Decide what you will look at in order to continue, before you go in. Second, identify where the load concentrates and thicken resources there alone. Valley load is not distributed evenly. It concentrates in the units running the old machinery and the new one at the same time. If that point breaks, movement stops. Third, produce one small result early. This is a question of evidence, not morale. One piece of evidence that the new machinery can work changes the quality of the argument inside the valley. Without evidence, the argument becomes a contest of beliefs. Fourth, the executive does not disappear during the valley. Many executives reduce their external communication in this period, because they would rather not explain bad numbers. Inside the company, that silence is read as preparation for withdrawal. Visibility during the valley must be three times what it is in normal conditions.

5.5 How to make progress visible

The progress of a redefinition cannot be measured by a single indicator. That is not a reason to leave it unobserved. We recommend watching four states side by side. First, the state of decisions. Of the things you decided to abandon, how many have actually stopped? Count what stopped, not what was decided. Second, the state of resources. Have people and budget actually moved to the new side? Third, the state of agreement. How far up the four layers does substantive agreement now reach? Fourth, the state of learning. How many points have been changed from the original plan? The fourth is easily misread. A high number of changes is not evidence that the plan was poor. A process with zero changes is a process that is receiving no information from reality. Put these four on the standing agenda of the executive meeting, every time. Never make them an occasional report. The moment they become occasional, reporting happens only when results are visible.

5.6 How to start it moving again

Redefinitions stop. Designing on the assumption that yours will not is the greater error. Stopping has types. The first type is a stop caused by a change of executive. The work is treated as the predecessor’s initiative and its budget is quietly cut. The guard against this is to detach the work from an individual’s name. Distribute responsibility for maintaining it across several people, and put it on the board’s agenda. The second type is a stop caused by a sharp change in the external environment. A collapse in results, a regulatory change, the loss of a major customer. Attention across the company turns to short-term response. This type cannot be avoided. What must be avoided is ending without a signal to resume once the response is over. If you are suspending, say that you are suspending, and write down the condition for restarting. The third type is a stop caused by fatigue. Nobody objects; the item simply drifts down the agenda. This is the most common and the hardest to notice. Restarting has an order. What you must not do first is announce a new policy. Re-announce without diagnosing why it stopped and the organization hears “here we go again.” A second declaration consumes more trust than the first. The correct order is this. First, record why it stopped, naming names. Second, confirm what changed while it was stopped. If the assumptions have moved, do not resume — redefine again from the start. Then restart with a narrower scope. Never resume a stalled process at its original size. Narrowing the scope is not retreat. It is securing a range in which movement is possible. Enterprise Exists to Redefine Itself. The condition of that existence is not moving far. It is not ending while stopped.

6 Questions for the executive

The argument, in one line. Carrying Enterprise Redefinition through means building agreement in the order in which burden is borne, and dividing resistance into three so that each is handled separately. It means declaring the valley in advance and holding through it — and, when movement stops, narrowing the scope and starting again. Not the design of a structure. Not a technique of communication. The allocation of agreement and burden. And only the person who absorbs the burden first can decide that allocation. Three questions to close. Each can be answered at your next executive meeting. Question 1 — In this redefinition, which member of the executive team loses what? If you cannot answer, you have abandoned nothing yet. A redefinition in which the top loses nothing is a plan to push losses downward. Organizations detect that imbalance with remarkable accuracy. Question 2 — Among the objections raised recently, which were legitimate concerns? If you cannot name one, there are two possibilities. Either the plan has no flaws, or there is no place to say so. The former almost never occurs. Question 3 — When you enter the valley, what will you look at to decide to continue? If you have not decided, you cannot make the decision to continue. Management that enters the valley holding only financial indicators always turns back at the bottom. The grounds for judgment can only be prepared before you go in. None of the three questions asks about the content of the plan. All three ask about the readiness of the people who carry it. The content of a redefinition can be drawn in fine detail with AI’s help. Enumerating options, estimating impacts, organizing the objections you expect — all of it is now fast. AI Optimizes. Humans Define. But deciding who bears the pain is not an optimization problem. And the work of carrying that decision through an organization has no proxy. Agreement forms only in front of a person who has taken on responsibility. However polished the materials handed round the meeting room, nobody stakes their own position on a plan in which it is unclear who is carrying it. Skill in carrying a redefinition through is not a difference of technique. It is a difference in who offered up what, first. Leadership Means Designing the Future. Designing a future requires more than a drawing. It requires the route by which the drawing is carried through. Drawing that route is part of the design.

In brief

Carrying a redefinition through is the design of which layer agrees to what, in what order, and of how the burden is distributed.
Agreement is built in the order in which burden is borne: the executive team, then the board, then middle management, then the whole company.
Resistance divides into vested interest, anxiety, and legitimate concern — met with design, speed of resolution, and revision of the plan.
The valley always comes. Only deterioration declared in advance is received as part of the plan.

Key concepts

Enterprise Redefinition / Leadership Formula / Question Design / Trust / Enterprise Redefinition Maturity Model (ERMM)

The chain of ideas

Purpose → Trust → Design → Execute → Learning

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. IV, Ch. 037 “How Future Value Theory Is Put into Practice” — why the owner’s role cannot be delegated, shown from the practice side
Vol. V, Ch. 045 “What Is Enterprise Transformation in the Age of AI?” — the difference between transformation and redefinition, settled before you begin
Vol. VI, Ch. 054 “What Does It Mean to Redefine Corporate Culture?” — why changes to incentives and procedures generate resistance
Vol. VI, Ch. 058 “The Conditions for Successful Enterprise Redefinition” — the necessary conditions to have in place before movement starts

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, #046 “Before You Cut Jobs with AI: What the Executive Should Think Through First” / #044 “Why Do Employees Wait to Be Told?”

Chapter 057 How to Carry Out Enterprise Redefinition