Chapter 027　What Is Future Value Management?

A theory that is merely correct does not change a company. An executive understands the definition of Future Value and accepts its ordering against enterprise value. The following Monday he walks into the executive meeting. The papers handed out, the agenda items, the format of the approval requests he signs — all identical to last month. Between a theory and the work of running a company there is a layer that never closes on its own. In this chapter we name that layer the management practice, and we define Future Value Management (FVM) as a new construct in this series. We add nothing to the theory. We lay the route by which the theory reaches Monday’s meeting.

1 The question — why it arises now

Volume III has set out the skeleton of Future Value Theory. What Future Value is. Why the future decides enterprise value. How it differs from present value, and how it relates to revenue. What the VURA Future Index measures. As theory, the account is complete. A completed theory does not move a company. Picture the Monday morning. The agenda is last month’s revenue landing, a first draft of next year’s budget, a personnel approval, and a capital request from an overseas site. Page one is a line chart against the same month last year. The discussion concentrates on why the plan and the result diverged. The theory sits there, still correct. The agenda is arranged exactly as it was last month. This scene is not produced by weak understanding. The executives who accept the theory are the ones most irritated by the gap. Nothing bridges conviction and execution. The reason is simple. Theory and practice answer different questions. Theory answers what is right. The work of running a company turns on who decides what, when, and on which form. The second does not follow automatically from the first. Correctness that has no route does not arrive. We call that route the management practice. It is the whole of the bodies that meet, the calendar they meet on, the forms they fill, the division of roles, and the criteria of appraisal. Almost no company writes it down. Every company has one. Which month budgeting starts. What the first field of an approval request asks for. Whose report opens the executive meeting. That set is the company’s management practice. The history of management theory has divided along this line. Drucker’s thinking about purpose spread across the world once it acquired management by objectives as its practice (Drucker, 1954). Research on performance measurement reached the executive meeting once it acquired the scorecard. Theories that were correct in content but never acquired a practice stayed on the shelf and never reached the floor. Future Value Theory stands at the same fork. The proposition that Future Value precedes enterprise value is hard to dislodge on its own terms. It also changes no approval form. It changes no budgeting unit. It changes no agenda order. So we place a layer beneath the theory. Theory states what is right. The practice states which institutions carry that rightness. Without that division of labor, a management theory stays a reading experience.

2 Conventional answers and their limits — what the

existing methods solved Before describing a practice, describe accurately the practices companies already run. Opening with a rejection would not be fair. Management by objectives (MBO) decomposes higher-level objectives into lower ones and appraises attainment at period end. It moves people by objective rather than by order. Bringing the language of purpose into management was decisive. It remains the base of appraisal systems today. The balanced scorecard grew out of the recognition that financial indicators alone cannot measure management. It sets four perspectives — financial, customer, internal process, and learning and growth — and links them causally. Promoting non-financial measures to formal management indicators was a large contribution. OKR connects company and unit objectives on a quarterly cycle and shares them transparently. As a device for aligning organizational direction quickly, it still works. EVA management asks whether the company earned above its cost of capital. It brought the discipline that capital carries a price. The debate about capital efficiency does not exist without it. The four differ in design and in era. They share three assumptions. The first assumption is that the objective function is supplied from outside. In all four, what to maximize is decided by someone outside the model. MBO does not interrogate the content of an objective. EVA demands a return above the cost of capital and never asks what the excess is for. The second assumption is that value converges on financial results. The scorecard’s causal map is the clearest case. Learning, process, and customer are all positioned as means running toward financial outcomes. That learning is itself a form of capital has no place on that map. The third assumption is that only what can be measured can be managed. An objective must be measurable before it can be written. What is measurable is usually something that already exists. The capability to create value that does not yet exist cannot, by definition, be entered in the objective column at the start of a year. These three assumptions held well enough while the definition of a business stayed stable. All three are now unsettled at once. Here most companies make one mistake. They adopt a new method in order to discard an old one. Drop MBO and install OKR. Abolish the scorecard and replace it with another indicator set. This replacement campaign usually stalls partway. The reason is plain. These methods are wired deep into the accounting system, the personnel system, and disclosure practice. They cannot be removed on their own. Attempt it and the front line ends up keeping two sets of books. What we need is therefore not replacement. We need a layer that stands above the existing methods and gives them direction. A method answers how to measure. A practice answers what the measuring is for. The two do not compete.

3 Redefinition — what Future Value Management is

We now introduce a new concept. Future Value Management is not present in the working papers. It is newly defined in this series. This chapter is its first appearance; later chapters treat it as established. The abbreviation is FVM. The nearest construct in the canon is Future Capital Management, set out in Future Value Theory (Kadowaki, 2026a). We state the relation below. The conclusion first: Future Capital Management is subordinate to Future Value Management. The definition is as follows. Future Value Management (FVM) is the management practice through which Future Value Theory is implemented inside an enterprise. It consists of five implementations: (1) placing Purpose at the origin of management; (2) designing decisions in the order of the Future Value Chain; (3) allocating Future Capital as an integrated whole; (4) separating human and AI responsibilities through Human-on-the-Loop Management; and (5) making Future Value Creation Capability visible through the VURA Future Index. Future Capital Management is the subordinate construct that carries out (3). This definition is not a summary of the theory. It is a translation of the theory into institutions. We take the five implementations in order. For each we state what changes, when, who changes it, and what the change produces. Implementation 1 — Place Purpose at the origin of management What changes. Not the wall poster. The first field of the proposal form. In most companies an approval request opens with “background” or “objective,” and what gets written there is the aim of the item itself. Replace it with: which part of our Purpose does this item advance, and how? When it changes. At drafting. Asking in the meeting is too late. Ask in the meeting and the person who can improvise an answer on the spot wins. Ask on the form and the drafter thinks before drafting. Who changes it. The department that owns the forms, together with corporate planning. The executive meeting approves; the secretariat executes. Leave this to the front line and the form never changes. What the change produces. Not every item needs to connect to Purpose. Equipment renewal and regulatory compliance are necessary too. The aim is a state in which the executive team knows how many items do not connect. A company at 90 percent connection and a company at 20 percent will look different in ten years on the same budget. Implementation 2 — Design decisions in the order of the Future Value Chain What changes. The order of the agenda, and the way each item is framed as a question. The reference order cannot be rearranged. Purpose → Learning → Redefinition → Creation → Enterprise Value Enterprise value comes last. Copy the chain onto the agenda and the design of the meeting itself changes. Classify each item by which of the five positions it belongs to. In most companies the bulk of the agenda gathers in the final two. When the upper three are blank, the company is turning the chain from the downstream end only. When it changes. At every executive meeting. A company on a monthly cycle can begin next month. Who changes it. The chair. The secretariat can reorder the papers, but if the chair first asks where revenue landed, the old order returns. What the change produces. A meeting that began with reports begins with questions. AI can write the reports. The meeting’s human hours go to what AI cannot produce. The questions placed in the upper three positions take a form such as this. Which of our assumptions is going obsolete? When that assumption fails, what should this enterprise become? Neither is answerable by reading the pack. Implementation 3 — Allocate Future Capital as an integrated whole What changes. The unit of budgeting. Capital other than financial capital is given an allocation of its own. The reference is this equation. Future Capital = Financial × Human × Learning × Trust × AI × Knowledge × Ecosystem × Purpose Financial capital is one term of eight. The relation is multiplicative, so if any single term is zero, Future Capital is zero. An abundance of financial capital cannot compensate for absent purpose, and advanced AI cannot compensate for absent trust. A company whose management accounts contain seven of the eight nowhere is running with a zero term in the product. When it changes. At annual budgeting, with a quarterly review of the allocation on top. Who changes it. The CFO and the executive meeting. Of the five implementations, this one meets the strongest resistance. What the change produces. The line between “investment” and “expense” is redrawn. Developing people, building data, accumulating trust — under the accounting standards all three are expenses. A company cannot change the standards. It can place Future Capital accounts alongside them in management accounting. What statutory accounting books as cost is tracked as capital in the management books. That double view is the substance of Implementation 3. Implementation 4 — Separate human and AI responsibilities through Human-on-the-Loop Management What changes. The role table for each task. One point first. Human-on-the-Loop Management is not a doctrine of supervising AI. Human beings sit above the system and design the whole. The objective is better design rather than better control. What gets written down is therefore not an approval flow. For each task, name who chooses the purpose, who sets the criterion, and who is answerable for the result. A task with no human name against those three sits outside Human-on-the-Loop Management. When it changes. Each time AI enters a new task. For existing tasks, take a full inventory once. Who changes it. The executive responsible for that task. Never the IT function. Delegate it there and you get a table of who runs which technology, not a table of who owns which result. What the change produces. Operation shifts from checking AI’s output one item at a time to approving a design. The first breaks down as volume rises. The second grows stronger as volume rises. Implementation 5 — Make Future Value Creation Capability visible through the VURA Future Index What changes. The composition of the standing pack for the executive meeting. Beside the financial pages, a page on Future Value Creation Capability. The VURA Future Index (VFI) assesses an organization’s capacity to create future value rather than its current value. Its design belongs to the previous chapter (→ Vol. III, Ch. 026). When it changes. Twice a year. Not monthly. The time constant of a capability and the length of an accounting period are too far apart. Who changes it. Corporate planning compiles. The executive team assesses itself. Outsource the assessment and the indicator turns from a diagnosis into a score. What the change produces. A missing capability that nobody could see becomes an agenda item. One prohibition belongs here. Never connect the VFI to personnel appraisal. Connect them and the lowest-scoring item stops being reported honestly. A diagnostic tool is used for diagnosis and nothing else.

4 Structure — how the five implementations mesh

4.1 The relation to Future Capital Management

Future Capital Management is defined in Future Value Theory (Kadowaki, 2026a). It is management that does not reserve the word capital for financial capital. Eight forms — financial, human, learning, trust, AI, knowledge, ecosystem, and Purpose — are allocated toward the future as one integrated whole. The Future Capital Equation defines what is being allocated. The relation to Future Value Management has to be stated precisely. Future Capital Management is the subordinate construct that carries out implementation (3) of Future Value Management. The two are not synonyms and they are not parallel. Invert the order and the ordering of the whole theory collapses. Why subordinate? Because capital allocation is a powerful instrument that cannot decide its own destination. Which future the capital goes to is decided by Purpose and by the Future Value Chain. Allocation without a settled purpose ends as a pro rata split across departments. A pro rata split copies last year’s structure into next year. Being subordinate does not mean being unimportant. The reverse. Future Value Management without Implementation 3 ends as an exhortation. A transformation in which capital does not move is not a transformation. Of the five, Implementation 3 has the greatest power to change reality, and it is also the slowest to take effect.

4.2 The five implementations are the implemented form of a

management equation The five were not chosen arbitrarily. They correspond one-to-one with the five terms of this equation. Leadership = Purpose × Question Design × Capital Allocation × System Architecture × Trust Implementation 1 carries Purpose. Implementation 2 carries Question Design; designing an agenda is nothing other than designing questions. Implementation 3 carries Capital Allocation. Implementation 4 carries System Architecture. Implementation 5 carries Trust — a company that makes its capability visible, weak points included, accumulates trust inside and outside. This equation is multiplicative. It is not a sum. The five implementations therefore cannot cover for one another by excelling somewhere. The smallest implementation fixes the level of the whole. A company with an advanced Implementation 4 and a blank Implementation 1 is running a directionless optimization at high speed.

4.3 Where the existing methods sit

Once the upper layer is fixed, the existing methods acquire a place. They are not abolished. They are relocated. MBO sits under Implementation 1. The technique of decomposing objectives is kept as it is. What changes is that the top objective being decomposed is connected to Purpose. OKR sits under Implementation 2. It remains an effective device for aligning direction quarterly, with the source of each Objective moved upstream in the Future Value Chain. The balanced scorecard sits under Implementation 5. Measuring across four perspectives is still a fine technique. What is rebuilt is the terminus of the causal map. The map moves from one with finance at the apex to one with Future Value Creation Capability at the apex. EVA management sits under Implementation 3. Keep it as an instrument for measuring the efficiency of financial capital. Use it in the knowledge that it measures one term of eight. Not replacement, but a layer above that supplies direction. Adopt this arrangement and a company can migrate without halting any existing institution. Only a migration that halts nothing ever finishes.

5 What it looks like in practice — where to start, and in

what order The five cannot begin at once. The reason is structural, not motivational. Three of the five touch existing institutions directly: the meeting bodies, the budget, and the personnel system. Touch institutions simultaneously and they seize. Two principles fix the order. First, start at the origin. Second, put the ones requiring institutional amendment last. A standard sequence follows. Stage 0 (before starting, once). Take a simple VFI assessment a single time. This is not the launch of Implementation 5. It is one photograph, taken as a baseline. Skip it and a year later nobody can say what changed. Stage 1 (first three months). Begin Implementation 1. Rewrite the first field of the proposal form. No institutional amendment, almost no cost. Of the five it is the cheapest and the fastest to bite. Stage 2 (months three to six). Begin Implementation 2. Change the design of the agenda. This is in fact the hardest step. Changing the order of the agenda means changing whose report comes first, and that touches the order of precedence inside the organization. At the same time, remove existing items that are reports only. Add without subtracting and the meeting runs long, and the practice is resented. Stage 3 (months six to twelve). Begin Implementation 4. Writing the separation of roles down can run in parallel with AI deployment. It is better run in parallel. Try to separate roles after deployment finishes and you are peeling apart an operation that has already set. Stage 4 (from the next budget cycle). Begin Implementation 3. The budget is bound to an annual calendar. That is exactly why it cannot be started earlier. It also means the start date is known from the beginning. What can be done in year one is preparing the management-accounting accounts in time for the next cycle. Stage 5 (from year two). Move Implementation 5 into standing operation, as a fixed observation every half year. Only here do the five implementations complete one turn. These intervals assume a company whose executive meeting runs monthly. In industries with long business cycles every stage stretches. Speed is not the point. Order is the point. The sequence has one exception. A company already far along in AI deployment moves Implementation 4 forward. When volume rises while roles remain unseparated, the executive team ends up chasing AI’s output. An executive team that is chasing has lost the time to design. A second exception is the company that has just finished writing its Purpose. Do not conclude that Implementation 1 is unnecessary because the writing is done. Writing and implementing are different jobs. Writing produces the words. Implementation connects those words to the first field of an approval request. What most companies lack is not the first. What goes wrong Failed adoptions share a shape. The first is declaring all five at once. The secretariat carries five simultaneous changes of form, and the front line receives five new fields to fill. Within three months nobody fills any of them. The second is starting from Implementation 5. Measurement produces visible results quickly, so it is an attractive place to begin. Measure before deciding what is worth measuring and the measuring becomes the objective. Behavior aimed at raising the indicator starts, and the practice degenerates into one more management method. The third is making the upkeep of the practice nobody’s job. Adoption gets decided; upkeep does not, and a year passes. The forms drift back, and the agenda restores itself to the order that begins with reports. A practice left alone always reverts. The old practice fits that company’s gravity better.

6 Questions for the executive — the practice is not the

objective The argument, in one line. Future Value Management is the management practice that translates Future Value Theory into the frame of the enterprise — its meetings, forms, calendar, roles, and budget — and then keeps that translation alive. Theory carries correctness. Method carries measurement. The practice joins the two. Remove any one of the three and the company does not move. A practice without a theory becomes clerical procedure. A theory without a practice ends in reading. A practice without method drifts, never tested. Three questions to close. Each can be answered at your next executive meeting. Question 1 — Of the items on next week’s agenda, how many can be explained by their connection to Purpose? Counting is enough. If the answer is zero, Implementation 1 is your starting point. If it is more than half, question the order next. Being explainable as connected and being drafted from the connection are different things. Only the second is implementation. Question 2 — Of the five implementations, which is smallest in your company? Counting the strong ones is pointless. The relation is multiplicative. Identify the smallest and concentrate the next six months there. This is not a matter of preference. It follows from the structure. Question 3 — Who will be maintaining this practice a year from now? The person who decides on adoption and the person who maintains it must be the same. A practice with no named owner for its upkeep is hollow by year two. This responsibility cannot be handed to AI. AI can operate a practice. It cannot doubt the practice itself. One reservation to close on. The practice is not the objective. Five implementations turning perfectly is not proof of good management. The practice is only the vessel in which Future Value is created. Let the vessel harden and it becomes a new bureaucracy. The moment the first field of an approval request starts being filled out of habit, as a box to clear, the practice is dead. So the practice is itself an object of redefinition. If an enterprise exists to redefine itself continuously, the practice that moves it must be rewritten continuously too. Only one thing does not change: the party doing the rewriting is human. AI optimizes. Humans define. Future Value Management is the design that carries that division into Monday’s meeting room.

In brief

This chapter defines Future Value Management, a construct newly defined in this series.
Future Value Management is the management practice through which Future Value Theory is implemented inside an enterprise.
The five implementations — purpose, chain, capital, role separation, and visibility — are joined by multiplication, and the smallest one fixes the whole.
The practice is not the objective. A hardened vessel produces a new bureaucracy, not Future Value.

Key concepts

Future Value Management / Future Capital Management / Future Value Chain / Future Capital / Human-on-the-Loop Management / VURA Future Index (VFI)

The chain of ideas

Purpose → Future Value Chain → Future Capital → Human-on-theLoop Management → VURA Future Index

Related first principles

Principle 1 — Purpose Precedes Profit. Principle 2 — Future Value Precedes Enterprise Value. Principle 4 — AI Optimizes. Humans Define. Principle 9 — Leadership Means Designing the Future.

Related chapters

Vol. III, Ch. 026 “What Is the VURA Future Index (VFI)?” — the design of the indicator used by the fifth implementation
Vol. I, Ch. 009 “How Should Work Be Divided Between AI and People?” — the division the fourth implementation assumes
Vol. IV, Ch. 036 “What Is Management That Creates Future Value?” — the picture of management that lies beyond the practice
Vol. IV, Ch. 037 “How Future Value Theory Is Put into Practice” — the adoption sequence, taken closer to the work itself

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, #084 “How Do You Raise Enterprise Value in the Age of AI?” / #036 “What Does Management That Creates Future Value Look Like?”

Chapter 027 What Is Future Value Management?