Managing Inputs, Not Just Outcomes

No, that is not from a dystopian finance novel. But if you have been in accounting and finance long enough, you have most likely heard some version of the above. So we, the accounting and finance team, are responsible for ensuring profits increase next quarter. Why us? That's right — we are the department that produces the reports that show quarterly profit. If we produce it… we are responsible for it? No, wait.

Take a minute and think about what it takes for your company to "make money." Raise prices? Require your vendors to sell to you cheaper? Lay off someone other than "me"? Close my eyes at the end of the quarter hoping the report shows profit? Should I seek a higher being right now?

It takes everything to go right to be profitable. We all know that. So if we all know that, why do we spend so much time trying to manage the output of something that takes "everything" to go right?

Let's take a deep breath. Luckily for us, we do have a tool that we can use and extend — one that gets us from the output (i.e., profit) to the drivers of that profit (i.e., human behavior). You all know the tool. So let's bring it back… DuPont analysis. From profits to human behavior.

A DuPont analysis reveals why ROI, net income, and gross profit can't be managed — only produced. The real work is defining the upstream behaviors that produce them. And, once found, managing those behaviors. If you successfully manage the inputs, the residuals (i.e., the outputs) will flow positively.

The central problem with how most organizations manage financial performance is that we obsess over outputs — ROI, net income, gross profit, EBITDA, revenue growth — and treat them as if they are levers we can pull. They are not. They are results. They are the scoreboard at the end of the game, not the plays that won it. And no team ever changed the score by staring harder at the scoreboard.

Outputs are lagging indicators by definition

Begin with a distinction that sounds obvious but reshapes everything once you take it seriously: the difference between a lagging indicator and a leading one.

A lagging indicator tells you what already happened. ROI, net income, gross margin, and cash flow are all lagging. I hate to say it, but financial statements are historical documents. They are accurate, auditable, and essential — and they are also, by definition, so yesterday. You cannot manage them directly because there is no dial labeled "net income" anywhere in your operation. Net income is what falls out the bottom after a thousand smaller things go right or wrong.

A leading indicator, by contrast, measures a behavior or condition before the financial result lands. It points forward. It is something a specific person can act on today. And critically, leading indicators are the only things in a business that are manageable, because they are the only things that haven't happened yet.

The failure mode in most management reporting is that we build elaborate, beautiful dashboards composed almost entirely of lagging indicators, then convene meetings to "manage" them. We are, in effect, holding people accountable for outputs while leaving the inputs that drive those outputs unmeasured and unowned. The result is predictable: a lot of pressure, a lot of explanation, and very little change — because the things being discussed are already in the past. And even AI cannot help us at this point.

DuPont is a decomposition, not a ratio

Most finance professionals know the DuPont identity in its classic form: the tidy three-factor split of net profit margin, asset turnover, and financial leverage. It explains why two companies with identical returns can be running entirely different businesses — one earning through fat margins, another through rapid asset turns, a third through balance-sheet leverage. That much is standard.

But the real power of DuPont is not in the three-factor split. It is in what happens when you refuse to stop there. Each of those three factors is itself an output of something more granular. Asset turnover is produced by revenue and the asset base. Revenue is produced by volume, price, and availability. Availability is produced by how quickly assets are made ready and how reliably demand is captured. Keep decomposing, and the tree extends downward — past the financial drivers, into operational inputs, and finally into the human behaviors that produce those operational inputs.

That last layer is the one almost no one maps. We are comfortable decomposing ROI into margin and turnover. We are far less comfortable saying out loud that asset turnover, three or four levels down, traces back to whether a specific technician completed a preventive-maintenance work order on schedule, or whether a counter representative returned a quote within twenty-four hours. Yet that is exactly where the manageable inputs live. The financial output at the top of the tree is the sum of human decisions made at the bottom of it.

The question that finds the input: "What feeds it?"

Take any number you care about and ask one thing of it: what feeds it? ROI is fed by margin and turnover. Turnover is fed by revenue and the asset base. Revenue is fed by volume, price, and availability. Availability is fed by how fast units are made rent-ready and how reliably demand is captured. Ask it again and again, refusing to accept another financial abstraction as an answer, and each pass drags you one layer closer to the ground.

The discipline is knowing when to stop, and the stopping rule is precise: keep asking "what feeds it?" until the answer is no longer a number but a behavior — a specific action taken by a specific, nameable person. That rule draws a line straight through the tree.

Above the line, everything is math: ratios, allocations, roll-ups, the accurate and auditable arithmetic of results. Below the line is management: the technician who did or did not close the work order, the counter rep who did or did not return the call. Above the line is what already happened. Below is what someone can still do.

That line does double duty, because the behavior line is also the accountability line. A measure that sits above it — a blended margin, an allocated cost, a roll-up rate — is something people can explain, contest, and quietly game, precisely because no one person controls it. A measure that sits below it can only be moved by doing the actual work; you cannot fake a closed order or a phone call that never happened into existence. That is the quiet payoff of decomposing all the way down: the measures you land on are exactly the ones you can fairly hold a named person to, because they are the only ones that person can actually move.

A clean teaching case: equipment rental

To make this concrete, it helps to anchor the discussion in an industry where the cascade is unusually visible. Heavy equipment rental is one of the cleanest examples I know.

Rental is brutally capital-intensive. A dealer's balance sheet is dominated by a fleet of machines, and the entire business model depends on rotating that capital — getting each unit out on rent, earning, coming back, and going out again. Because the asset base is so large and so concentrated, asset turnover isn't one driver among many; it is the driver. And asset turnover in rental is governed almost entirely by a single operational input: utilization. How much of the time is each machine actually earning? And what rate are we receiving while it is earning?

That single fact makes rental an ideal lens. Trace ROI down through the DuPont tree in a rental business and you arrive, with remarkable speed, at utilization. Trace utilization down one more level and you arrive at a short list of operational behaviors — preventive-maintenance compliance, turnaround speed, quote follow-up, delivery reliability — each of which is owned by a specific, nameable person. The chain from a P&L line to an individual's daily habit is short and unbroken. What is true in rental is true everywhere. What is your "utilization" path?

Whatever it is… a real person is controlling it.

The layer no one maps: human inputs

This is where the framework earns its keep. Below every operational input sits a human behavior, and below every human behavior sits a person.

The principle generalizes far beyond rental. In any business, the financial output you are worried about is the downstream sum of behaviors owned by people who have never been told that their daily habit is a financial input. In a clinic, revenue per room runs down to whether the front desk confirms tomorrow's appointments tonight. In a law firm, realization runs down to whether associates enter their time the day they work it, not the week they reconstruct it. On a factory floor, it runs down to whether the line lead logs a changeover correctly. None of these people thinks of the habit as a financial lever — the technician does not picture a maintenance order as ROI, any more than the front-desk clerk pictures a confirmation call as revenue — but each is holding a financial input in their hands. The work of finance, the genuinely strategic work, is to build the map that connects the two, then put the leading indicators in front of the people who own them, every day, in language they can act on.

There is an organizational design implication here that deserves emphasis: if a driver belongs to everyone, it belongs to no one. Every leading indicator on your dashboard needs a named owner. The moment ownership is diffuse, the metric becomes ambient noise — reported, discussed, and never moved.

The inputs behind the inputs

Come on… really? One more layer?

There is a temptation, having finally reached the behavior, to declare victory and start measuring. But a behavior is not a dial you turn directly either. It, too, is produced by something — and if you want it performed reliably rather than occasionally, you have to go down one more layer, into the conditions that determine whether a person actually does the thing, day after day, when no one is watching.

Five conditions do most of the work. Culture: whether people take ownership, whether standards are clear, whether there is accountability without blame. Leadership behavior: how visible the manager is, how often coaching actually happens, whether the standard is modeled rather than merely announced. Training and competence: whether the person even knows how to do the thing well. Information and feedback: whether the technician can see his own PM-compliance rate and the counter rep her own conversion — because a behavior no one can observe is a behavior no one sustains. And incentives: whether the pay plan rewards the input at all, or only the revenue that trails it by a quarter. As we all know, "how it affects your back-pocket is how you behave."

This is the layer that separates a framework from a fad. It is easy to put "PM compliance" on a dashboard and assume the technician will now comply; he will not, unless he can see the number, has been shown what good looks like, works in a culture that treats the standard as real, and is recognized when he hits it. The behaviors at the bottom of the DuPont tree do not float free. They grow out of culture, leadership, training, feedback, and incentives — which turn out to be the most upstream inputs of all, and the ones the finance function is least accustomed to claiming as its own.

Small inputs, outsized leverage

One of the most counterintuitive features of this approach is that the highest-leverage inputs are usually small. They are not reorganizations or new software platforms or strategy offsites. They are modest behaviors that, performed consistently, swing large numbers — and performed inconsistently, bleed value silently. In other words, "sweat the small stuff."

Consider the quote that never gets a follow-up call. A contractor phones in, asks about renting a machine for three weeks, and gets a quote. No callback is scheduled. No follow-up note is made. Forty-eight hours pass; the contractor hasn't heard back, calls a competitor, and rents from them instead. One lost rental — perhaps eight to eighteen thousand dollars in revenue — plus a machine that now sits idle in your yard dragging utilization down. Then multiply that by ten or twenty quotes a week with no systematic follow-up, and the organization is quietly losing a substantial sum every month — none of which ever appears in a report, because lost revenue has no ledger account.

Now consider the fix. It is not expensive or complex. It is a rule: every open quote gets a follow-up call within twenty-four hours, and follow-up conversion becomes a metric reviewed in the daily team huddle. That single behavioral input, managed consistently, can add several percentage points to revenue. Small input. Massive leverage. No capital required.

This is the pattern worth internalizing: the inputs with the most leverage are frequently the ones too small to feel important and too invisible to show up in conventional reporting. They are exactly the inputs a lagging-indicator dashboard will never surface.

Finding the input is the easy part

It would be satisfying to stop there — decompose the tree, find the behavior, name the owner, put the number on a board. But anyone who has tried this in a real organization runs into an uncomfortable truth: building the map is the easy part. The DuPont analysis finds the behavior. It does not tell you how to reward that behavior without deforming it — and that second problem is far harder than the first.

The analysis is arithmetic; it terminates in a right answer. Incentive design terminates in judgment, and it fails in ways the math never warns you about. The moment a clean input metric becomes the thing people are paid on, they start optimizing for the metric rather than the outcome it was standing in for — and a faithful signal quietly hardens into a quota to be filled by whatever route is cheapest. Which is exactly why the strategic work of finance does not end when the map is finished. It begins there.

Goodhart's Law holds that when a measure becomes a target, it ceases to be a good measure. The moment you begin rewarding people on a specific input, the input is liable to distort. Tie a technician's bonus purely to the "number" of PM work orders closed, and you may get work orders closed fast and shallow. Reward quote "volume" and you may get a flood of low-quality quotes. The behavior you measure is the behavior you change — which is the whole point, but also the whole risk.

The discipline, then, is to design incentives around inputs without corrupting the inputs themselves: pair quantity measures with quality checks, balance any single metric against a counter-metric, and keep the human judgment in the loop rather than reducing a behavior to a single gameable number. Managing inputs is powerful precisely because measurement changes behavior. That same power is what makes thoughtless measurement dangerous.

What this means for the finance function

Translating all of this into practice is, fundamentally, a shift in what the finance function is for. The scorekeeper reports outputs after the period closes. The architect builds and runs the system of inputs that determines what those outputs will be. Strategic finance is the second role. A few concrete moves get you there.

Audit your scorecards. Look honestly at what your branch, division, or department reviews. If the reviews center on ROI and revenue, you are managing outputs. Shift the conversation to inputs — utilization, PM compliance, conversion, turnaround — at every level of the organization. And start with one number: take the metric your last review circled in red and ask "what feeds it?" until the answer is a person's name. Run that single trace out loud, once, and the whole room sees what managing an input actually looks like.

Assign ownership of every driver. Each leading indicator gets a named owner. Not a department; a person. Diffuse accountability is the same as no accountability.

Build a daily rhythm of input data. A shift manager running a ten-minute morning stand-up built around three to five leading indicators — ready-to-rent rate, open PM work orders, quotes awaiting follow-up — does more to move financial outcomes than a monthly review of lagging results, because it intervenes while there is still time to act.

Tie compensation to inputs, thoughtfully. Reward the behaviors that produce results, not only the results themselves — while respecting the measurement trap above. A PM-compliance component for technicians, a conversion component for sales, an on-time-delivery component for logistics.

Coach behaviors, not just results. When a financial metric moves, ask which behavior moved with it. When utilization drops, the question is not "why is the number down" but "what did we stop doing." When margin improves, identify the human input that drove it and reinforce it deliberately.

None of this displaces traditional reporting. We still close the books, still report ROI, still owe leadership an honest accounting of results. The shift is in what we do between the closes — building the map from financial output to human input, putting leading indicators in front of the people who own them, and managing the business at the layer where management is actually possible.

The outputs we report are real, but they are downstream. They are the sum of a thousand upstream decisions made by people who, often, have never been shown how their daily work connects to the numbers on the board. Show them. Manage the inputs. The outcomes will follow.