Another webinar that Nick presented the next day: "Why Standard Costing Leads to Poor Operating Decisions - BMA Webinar"
Most CI practitioners have lived through the same conversation. You finish a successful improvement project. The operational metrics moved. The team is energized. You walk into the executive review or the finance meeting to present the result, and the question that comes back is some version of: "How much did this save us?"
The honest answer is usually complicated. The improvement created capacity. The capacity hasn't translated into either revenue growth or headcount reduction yet, so the financial statement doesn't show savings. The finance team labels the benefit as "soft" — meaning unproven, or unfunded, or both. Skepticism builds. The CI program plateaus. Eventually executives lose interest because the numbers they care about aren't moving in the way they expect, even when the work is producing real value.
Nick Katko has spent his career working on this problem. He was the CFO at Bullard during its Lean transformation in the 1990s, where he implemented one of the first complete Lean management accounting systems and eliminated standard costing. He's been President of BMA since 2002, where his firm coaches organizations through Lean accounting transformations across manufacturing, healthcare, software, engineering, and service industries worldwide. He's the author of "The Lean CFO" (second edition, 2023) and co-author of "Practicing Lean Accounting" (2021). His work, alongside Gene Cunningham, Orry Fiume, and Jerry Solomon, was part of what gave the field of Lean accounting its name.
The session walked through how Lean actually works financially, why the traditional financial analysis tools that organizations default to don't fit Lean operations, and what to use instead — particularly the Box Score, a tool that connects operational performance, capacity, and financial outcomes in a single management view. The conversation was practical throughout, with examples from manufacturing and healthcare that translate directly to other industries.
Nick Katko is President and owner of BMA. Since 2002 he has applied his Lean accounting experience to help BMA clients develop, lead, and coach their Lean accounting transformations. His clients have ranged from family-owned businesses to multinational companies across manufacturing, healthcare, software, engineering, and service industries worldwide.
Nick was an early pioneer of Lean accounting. In the 1990s, as CFO of Bullard, he implemented a complete Lean management accounting system in conjunction with Bullard's Lean transformation, including the elimination of standard costing. He is a regular speaker at the annual Lean Accounting Summit and has presented at conferences in the United States, Europe, Asia, and Australia.
He is the author of "The Lean CFO – 2nd edition" (2023), an updated version of the 2013 publication "The Lean CFO." The Lean CFO has been translated and published in Turkish and Italian. He co-authored "Practicing Lean Accounting" (2021), which has also been published in Italian.
Chris Burnham, Senior Director of Lean Strategy at KaiNexus at the time of the webinar, facilitated the Q&A. The session was born out of conversations he had with Mark about how often Lean professionals struggle to translate Lean results into the financial language that executives and finance leaders trust.
Nick opened with what sounded like a familiar point but turned out to anchor the whole session. The conversation isn't really about the numbers. It's about thinking habits.
The pattern he described is a loop. Numbers drive thinking. Thinking drives behavior. Behavior drives decisions. Decisions change the numbers. The loop runs continuously, and people get comfortable with the specific numbers they use to operate within it.
The problem in a Lean transformation is that the comfortable numbers from the pre-Lean operating model may not fit the new environment. Worse, they may actively drive non-Lean behavior. Standard product costing — to take one example Nick returned to repeatedly — produces a single number that lumps fixed and variable costs together and presents the result as if it's all variable. The number drives behavior that makes sense for the model the number assumes, which isn't the model the Lean organization is actually operating under. The behavior fights the transformation. The transformation stalls.
Connecting continuous improvement to the bottom line, in Nick's framing, requires changing the numbers people use. Not because the old numbers are wrong in some abstract sense. Because the old numbers drive the wrong thinking for the operating model the organization has chosen.
Nick called the foundational concept "the economics of Lean," and he was emphatic that everyone in a Lean company — from senior leadership down to line management — needs to understand it. The concept itself isn't complicated. The implication is what matters.
The primary result of any continuous improvement activity, or any series of them, is creating capacity. Or, said differently: creating time. When you eliminate waste, you stop an activity from occurring. The time that activity used to consume becomes available for something else. The financial benefit doesn't come from the elimination itself. It comes from what you do with the capacity you just created.
The capacity can be used three ways. You can serve customers better and deliver more value to existing customers. You can sell more and grow revenue without increasing fixed costs. Or, over a longer horizon, you can use the capacity to achieve real cost reduction by reducing headcount through attrition rather than layoff.
Nick used Bullard as a personal example. The company set a target of 20 percent year-over-year operational improvement. The team realized that hitting that improvement target would create 20 percent additional capacity. Capacity that isn't used to produce or sell something is capacity the company is paying for without benefit. So the marching orders for sales became: grow sales by 20 percent. Not because sales growth was the goal of the improvement work, but because the improvement work was creating capacity that had to be used productively for the company to capture the financial benefit.
The reframing matters. In traditional financial thinking, you set financial targets and tell people to hit them. The financial target is the cause. Operational improvement is supposed to follow. In Lean economics, the cause-and-effect runs the other way. Improved operating performance and better capacity usage are the causes. Improved financial performance is the effect. "If you want to change the financials, you have to change the physical," as Nick put it. Financial engineering — setting financial targets and telling teams to hit them by whatever means — can produce short-term results but doesn't change the underlying capability. Lean does change the underlying capability, but the financial benefit shows up only when the capacity gets used.
Nick listed six ways that Lean operations drive financial performance.
Increase sales without increasing fixed costs. The capacity created by improvement work absorbs incremental volume without proportional increase in payroll, facilities, or other fixed expenses. Revenue grows. Contribution margin grows. Profit grows faster than revenue because the fixed cost base is constant.
Reduce fixed costs as a percentage of sales. Labor is the primary example. Full-time employees are a fixed cost. If improvement work creates capacity such that the organization can grow without proportional hiring, labor as a percentage of sales drops over time even as the absolute labor cost stays flat or grows slowly.
Reduce variable costs and improve contribution margin. Some improvements directly reduce variable costs — better quality reduces scrap and rework material, better inventory management reduces material flowing into work-in-process inventory. The contribution margin per unit goes up.
Increase capacity without paying for it. The fundamental benefit of improvement work that creates capacity is that the capacity exists without requiring additional capital or operating expense. The organization has gained the ability to do more without spending more.
Improve cash flow. The most direct example is manufacturing inventory reduction — when Lean thinking drives down inventory levels, working capital is freed up and cash flow improves. Similar dynamics exist in other industries where excess inventory of any kind ties up cash.
Make better strategic decisions. When leadership can see the relationship between operational improvement, capacity creation, and financial performance, they can make decisions about growth, capital allocation, and investment that fit the operating reality. The visibility itself is a financial benefit because it prevents the wrong decisions.
The six outcomes aren't independent. Most successful Lean transformations produce some combination of them. The Box Score is the tool that makes the combination visible.
The Box Score is a single-page view that connects three categories of information for each value stream: operational performance, financial performance, and capacity. Nick was specific that the Box Score isn't an external reporting tool — it's a management tool used internally to drive thinking and decision-making.
Operational performance is captured through Lean performance measurements. The combination addresses delivery, quality, lead time, productivity, cost, safety, and morale. Lean operating practices and continuous improvement activities make all these categories of measurements move positively over time.
Financial performance is captured through what Nick calls a value stream income statement. The income statement is reorganized by value stream rather than by traditional accounting categories. For each value stream, the team can see the revenue (where applicable), the actual costs incurred by the value stream during the period, and the value stream operating profit. Non-value stream costs are separated out. Cost allocations are not used. The result is a profit number for each value stream that reflects what the value stream actually produced.
Capacity is the third component, and Nick called it the new animal in terms of numbers. Capacity in the Box Score is measured three ways: how much time is being spent on creating value (productive capacity), how much time is being spent on everything else (non-productive capacity), and how much capacity is being created through improvements (available capacity). The capacity numbers aren't the same as ERP system availability metrics. They're a Lean view of how time is actually being used and how the use of time is changing.
The Box Score becomes the tool that lets a management team see what's happening across all three dimensions simultaneously. An improvement event produces changes in some operational metrics, releases some capacity, and may or may not show immediate financial benefit. The Box Score makes all of that visible in one place. The team can then make decisions about what to do with the released capacity — sell more, reduce headcount through attrition, take on new work — based on the operating context rather than on financial targets alone.
The cost management section of the session walked through how Lean changes the way costs should be defined, measured, and managed.
Defining costs. Variable costs change directly with short-term volume changes. The clearest example is material in manufacturing — sell one more unit, incur the material cost; sell one fewer unit, save the material cost. Fixed costs don't vary with short-term volume changes. They're influenced by management decisions. Full-time labor is the canonical example: the cost is fixed because the people come to work and get paid regardless of short-term volume, and the cost changes only when the organization makes a decision to hire or not replace someone.
In Lean thinking, more costs are considered fixed than under traditional cost accounting. The implication runs counter to a lot of conventional cost allocation. Product cost in manufacturing — or cost per patient in healthcare — takes fixed costs and presents them as if they were variable. The number changes when volume changes, which makes the cost appear to vary, but the underlying costs haven't actually changed at all. The denominator in the cost per unit calculation changed. The numerator stayed flat. The picture is misleading.
In healthcare specifically, Nick noted, most costs are fixed. Cost per patient calculations are particularly distorted because the underlying costs don't move when patient volume moves. Improving cost per patient by trying to drive the numerator down is hard because the numerator is mostly fixed. Improving cost per patient by driving the denominator up — seeing more patients with the existing capacity — is the lever that actually exists, but the cost per patient framing obscures that.
Cost savings versus cost avoidance. Nick drew a sharp line between actual cost savings (expenses that go down in the short term) and cost avoidance (costs that don't increase in the future). Continuous improvement produces more of the second than the first. Capacity creation is, by definition, cost avoidance — the organization avoids the future cost of additional headcount, facilities, or capital because the existing resources can handle more work.
The trap many organizations fall into is monetizing time savings. The improvement saved 3.75 hours per changeover. The team multiplies that by a machine rate and presents the result as a dollar savings. The number isn't real in the short term because the costs haven't actually changed — the people and machines that used to do the changeover are still being paid the same amount. The number may become real in the long term if the released capacity is used to grow revenue or to avoid hiring. But the short-term financial statement won't show the savings the calculation implies.
Measuring cost reduction properly. Nick's recommendation is to look at fixed costs as a percentage of sales rather than as absolute dollars. Continuous improvement should produce fixed costs that grow more slowly than sales, which shows up as a declining fixed-cost-to-sales ratio over time. For variable costs, contribution margin (sales less direct costs) is the right metric because it captures both volume and cost dynamics together. Avoid using cost allocation methods to try to measure improvement, because the allocations distort the picture in ways that mask what's actually changing.
The labor cost framing. Nick spent extended time on labor because it's the largest cost in most companies and the area where traditional thinking and Lean thinking diverge most sharply. Conventional financial thinking treats labor as an expense to be controlled and reduced. Lean thinking treats labor as the cost of the organization's most important asset — the people who do the work and, more importantly, do the thinking, problem-solving, and continuous improvement that no software system or methodology can do on its own.
The shift in framing matters operationally. If labor is an expense, the natural management impulse is to reduce headcount when capacity is created. If labor is the cost of capacity, the natural management response is to ask how the released capacity should be used. The first framing produces a Lean program that the workforce learns to fear because every improvement threatens jobs. The second framing produces a Lean program that the workforce supports because improvement creates room for growth, development, and meaningful work.
Bullard's accounting function provides Nick's personal example. The team applied Lean thinking to their own work and over a few years reduced staff by about 40 percent. Nobody was laid off. The team made the decision collectively. When people left, the team examined whether they could absorb the work with existing capacity. A few accounting staff applied for other jobs in the company, which the team supported. The 40 percent reduction happened through attrition and internal mobility, not through reductions in force. The cost reduction was real. The cultural cost that headcount-based reductions would have produced was avoided.
Nick walked through several examples of how an improvement event shows up in a Box Score. The examples are abstract numerically but the patterns generalize.
Quality, delivery, and flow improvements. Three improvements that improve on-time shipments, first-time-through quality, and days of inventory. The Box Score shows reduced material cost (less waste, less inventory carrying), but the bigger effect is in capacity: employee available capacity goes from 19 percent to 37 percent, and machine available capacity goes from 15 percent to 29 percent. The capacity doubled. The question becomes what to do with it. The example assumes the organization uses the capacity to grow sales. Revenue goes up. Material cost (variable) goes up proportionally. Conversion costs (production costs) stay roughly flat — some overtime gets eliminated. Value stream profit goes from $104,000 per month to over $172,000 per month, or from 31 percent to 40 percent of revenue. The performance measures at the top of the Box Score continue improving. The full benefit of the improvement work shows up when the capacity gets used productively.
Hospital surgical instrument flow. Reducing the round-trip time for surgical instruments from the operating room to processing and back from 10.6 hours to 3.6 hours releases seven hours of capacity. Productivity improves. Lead time improves. Non-productive capacity drops. Available capacity rises. In healthcare, surgery is typically the primary profit center of a hospital. Performing more surgeries with the same fixed cost base generates more revenue, more variable cost, and net positive profit impact. The Box Score lets the team see how the operational improvement translates into financial impact if the released capacity is used.
Changeover time reduction. Reducing setup time from four hours to fifteen minutes — a 3.75-hour reduction per changeover — produces operational benefits in productivity, delivery, inventory, and lead time. The Box Score shows substantial capacity creation. If the organization can use that capacity to produce and sell more, the financial benefit is the contribution margin on the additional volume, which is materially larger than any cost savings from the changeover time itself. Multiplying the hours saved by a machine rate would dramatically understate the real financial benefit because the dollar value of the released capacity is determined by what gets done with it, not by the cost of the time that was eliminated.
Quality improvement through error-proofing. Installing an error-proofing device that drops defect rate from 2.7 percent to zero produces positive impact across performance measures and creates capacity (every defect consumes time, so eliminating defects releases time). If the organization can sell the additional capacity, revenue and contribution margin both improve. If not, variable costs go down due to reduced material waste. Either way, the Box Score shows the financial impact in proportion to how the capacity gets used.
Wireless headsets in customer service. Improved ergonomics, staff satisfaction, and shorter hold times for customers. The operational impact is in productivity, safety, and morale. The financial impact in the short term may not be clear. In the long term, if shorter hold times produce more customer purchases, revenue grows. The example illustrates that not every improvement has a clear short-term financial story, but the Box Score discipline still makes the operating and capacity effects visible, which lets leaders make informed decisions about whether and how to expand the practice.
Nick spent the last main section of the presentation on how traditional financial analysis tools — return on investment, net present value, internal rate of return, payback period — interact with continuous improvement work.
The tools are fundamentally sound when they fit the situation they were designed for. They all assume a cash outflow followed by a stream of returns. Capital investment, equipment purchase, R&D spending, marketing investment — these fit the model.
Continuous improvement that creates capacity often doesn't fit the model. There's no cash outflow. The "investment" is people's time spent on improvement work, which is already being paid for. The "return" is capacity, which doesn't show up on a financial statement until something gets done with it. Calculating an ROI for an improvement project requires fabricating an investment number and fabricating a savings number, both of which obscure the actual economics.
Nick's preferred framing: return on effort rather than return on investment. The effort is the time the team spent on the improvement. The return is the capacity released and the operational performance improvement that resulted. Whether the return shows up financially depends on how the capacity gets used. The return-on-effort framing is more honest than a manufactured ROI calculation and more useful for actually deciding whether the improvement work was worth doing.
Cost allocations. Nick reiterated the warning. Allocating a fixed cost to a value stream or a product or a patient produces a number that looks variable but isn't. The allocation doesn't change actual costs. It just moves them around. Using the allocations to measure improvement produces misleading conclusions because the allocations move when the allocation basis moves (volume, headcount, square footage, whatever), not when the actual costs move.
Avoiding the monetization trap. Putting a dollar sign in front of time savings produces a number that feels real but often isn't. When people see a dollar figure attached to an improvement, they expect to see it on the financial statement. When it doesn't appear, trust in the CI program erodes. The honest framing is to track capacity creation in capacity terms and to track financial impact in financial terms, with the explicit understanding that the connection between them depends on management decisions about how to use the capacity.
Nick's closing summary distilled to a short list.
Accounting and finance people need to experience continuous improvement to understand what it actually is. Reading about it isn't enough. The experience changes how they think about the numbers.
They need to understand that continuous improvement leads to financial improvement, not the other way around. The cause-and-effect runs from operational change to financial change, not from financial targets to operational action.
The economics of Lean and the Box Score should be integrated into ongoing analysis and decision-making, not used only for special projects or major events.
Distinguish between short-term and long-term impact. Short-term impact must be actual — costs that have actually been reduced, revenue that has actually been generated. Long-term impact can include the operational improvements that will translate into financial benefit over time as capacity gets used.
And — back to where the session opened — numbers drive thinking. The Box Score drives thinking about Lean relationships. The thinking drives the PDCA behavior of continuous improvement. The decisions that emerge are trying to improve economic value across all six outcomes — not just cutting costs, but growing revenue, improving contribution margin, increasing capacity, improving performance, and improving cash flow. Any event that makes a positive impact on any of those outcomes is producing real value, and the Box Score is the tool that makes the impact visible.
The conceptual framework Nick walked through depends on infrastructure that makes the relevant data visible at the right level of aggregation. The Box Score is a tool that synthesizes operational metrics, financial metrics, and capacity metrics for each value stream. Pulling that synthesis together from disconnected systems — operational data in one place, financial data in another, capacity calculations in spreadsheets — is exactly the kind of administrative overhead that erodes the practice over time.
The platforms that hold improvement work at scale are also the platforms that can support Box Score reporting. The improvement portfolio Nick referenced in his examples — the quality improvements, the changeover reduction, the error-proofing installation — lives in the same operational record as the impact tracking that would inform the Box Score. The connection between the work and the measurement of the work is the value of integrated infrastructure.
The capacity question Nick returned to throughout the session is where infrastructure matters most. Capacity creation is the primary output of continuous improvement work, and capacity isn't a number that most operational systems track directly. The discipline of measuring how much time is being spent on value creation, how much on non-value-added activity, and how much new capacity has been released through improvements requires both the data collection mechanism and the management discipline to use the data. Without infrastructure that holds the data and makes it visible at the value stream level, the capacity question becomes either a manual exercise that doesn't get done consistently or an estimate that doesn't carry the weight needed for executive decision-making.
The relationship between improvement work and financial performance also depends on visibility at the executive level. Nick's recommendation that accounting people experience continuous improvement requires that the improvement work is visible to them — that they can see what's happening, attend reviews, observe the gemba, and develop the intuitions about how operational change translates into financial change. Platforms that make improvement work visible across the organization, including to finance and accounting functions that wouldn't otherwise be in the operational meetings, support the cultural shift Nick described.
The return-on-effort framing Nick advocates also benefits from infrastructure support. The effort in continuous improvement work — the time teams spend on PDCA cycles, kaizen events, A3s — is recorded in the same operational systems that hold the improvement portfolio. The return — the operational performance change, the capacity released — is also tracked in those systems. The ratio between them, and the patterns of what produces high return on effort versus low, becomes visible when the data is integrated. Without integration, return-on-effort analysis becomes another manual exercise that doesn't get done consistently enough to inform decisions.
None of this changes what Nick was teaching. The economics of Lean is what it is. The Box Score is the management tool it is. The cost management discipline is the discipline. What infrastructure does is preserve the integrity of the practice when the practice is being applied at scale across multiple value streams, multiple sites, and over years rather than weeks. The CI lead can't hold all of this in their head. The platform can hold it in a way that makes the analysis routine rather than heroic.
What is Lean accounting and how is it different from traditional accounting? Lean accounting is the practice of organizing financial information and management analysis in a way that aligns with Lean operations and continuous improvement work. The term originated in the late 1980s and early 1990s when CFOs at companies going through Lean transformations — Nick at Bullard, Gene Cunningham, Orry Fiume, Jerry Solomon — recognized that the information generated by traditional cost accounting systems was producing thinking and decisions that fought the Lean transformation rather than supporting it. Lean accounting changes the numbers, the analysis tools (the Box Score, the value stream income statement), and the relationships between operational performance and financial performance to align with Lean thinking. It's less about the accounting function and more about how financial information is structured and used to drive better decisions in Lean organizations.
Why does Nick say improvement creates capacity first, profit second? Because that's how the mechanics actually work. Continuous improvement eliminates waste, which means activities stop happening, which means time becomes available. Time that was previously consumed by waste is now released capacity. What happens to that capacity — whether it's used to grow revenue, used to absorb work without hiring, or simply sits unused — determines whether the financial benefit shows up. Profit isn't an immediate output of improvement work. It's a downstream consequence of how the released capacity gets used. Organizations that expect improvement to produce immediate profit will be disappointed and will lose faith in the practice. Organizations that understand the capacity-first dynamic will make decisions about capacity utilization that produce the profit.
What is a Box Score? A single-page management tool that synthesizes three categories of information for each value stream: operational performance (the Lean performance measurements covering delivery, quality, lead time, productivity, cost, safety, morale), financial performance (revenue and actual costs structured as a value stream income statement), and capacity (productive, non-productive, and available). The Box Score is an internal management tool, not an external reporting tool. The financial component serves as a basis for external reporting but isn't itself external. The purpose of the Box Score is to give management visibility into the relationships between operational change, capacity, and financial outcome so they can make informed decisions about how to use capacity and how to evaluate improvement work.
What's wrong with using cost per patient or cost per unit as performance metrics? They take fixed costs and present them as if they were variable, which produces misleading conclusions about cost movement. Most costs in healthcare are fixed — the staff, the facilities, the equipment, the overhead. Cost per patient changes when patient volume changes, which makes the cost appear to vary, but the underlying costs haven't actually changed. The denominator moved. The numerator stayed flat. Decisions made on cost per patient assume both numbers can move, which leads to wrong decisions about where to focus improvement work. The same issue applies to cost per unit in manufacturing. Nick's recommendation is to track fixed costs and variable costs separately, to measure fixed costs as a percentage of sales over time, and to use contribution margin for variable cost analysis — none of which require cost allocations.
What's the difference between cost savings and cost avoidance? Cost savings are expenses that actually go down in the short term — overtime reduced, materials no longer purchased, a position not replaced. Cost avoidance is future costs that don't get incurred because the organization avoided the need for them — capacity exists so additional hires aren't needed, capacity exists so a facility expansion doesn't have to happen, capacity exists so a project doesn't require new headcount. Continuous improvement produces more cost avoidance than cost savings. Both are real value. They show up differently on financial statements. Cost savings show up immediately as reduced expenses. Cost avoidance shows up as the absence of expense growth that would otherwise have occurred. Tracking and communicating both is part of making the CI program's full value visible.
Why is monetizing time savings a trap? Because the dollar figure produced by multiplying time saved by a labor or machine rate often isn't real in the short term. The people whose time was saved are still being paid the same amount. The machine that runs faster is still owned and maintained at the same cost. Until the released capacity is actually used to produce or sell more, or until headcount actually decreases through attrition, the cost hasn't changed. Putting a dollar sign in front of time savings creates an expectation that the savings will appear on the financial statement, and when they don't appear, trust in the CI program erodes. The honest framing tracks capacity in capacity terms and tracks financial impact in financial terms, with the connection between them depending on management decisions about capacity utilization.
Why is "return on effort" a better framing than "return on investment" for continuous improvement? Because continuous improvement that creates capacity typically doesn't involve a cash outflow that fits the ROI model. The "investment" is people's time spent on improvement work, which is already being paid for. The "return" is capacity, which doesn't show up financially until something is done with it. Calculating a traditional ROI requires fabricating both the investment number and the return number, which obscures the actual economics. Return on effort tracks the effort directly (time spent on improvement) and the return directly (capacity released, operational performance improved) without forcing the situation into a model it doesn't fit. The framing is more honest and more useful for deciding whether improvement work is worth doing.
Does adopting value stream accounting require restructuring the organization? Not necessarily. Value streams are more of a Lean thinking concept than a Lean accounting concept. Creating value streams and managing them doesn't require a full org redesign. What's required at minimum is strong value stream teams that include operational leadership, sales representation, and finance representation. Someone has to manage the value stream — there has to be a value stream manager or a team of people with clear responsibility. The accounting structure follows the operational structure. If the value streams exist operationally, the accounting can be organized to support them without dismantling the existing functional structure.
How do you start moving a finance team off cost per unit toward Lean accounting numbers? Introduce the new numbers and demonstrate how they lead to better decisions. Don't lead by criticizing the old numbers. Most CI practitioners already know that product cost or cost per unit is a problematic metric, but the finance team has reasons for using it — external reporting requirements, internal benchmarking practices, historical analytical habits. Pointing fingers at the old numbers without offering an alternative produces resistance. Building the new analysis tools (the Box Score, the value stream income statement), running them in parallel with the old reporting, and showing how the new tools produce better insights for specific decisions is the path that works. The cost allocations get de-emphasized over time as the new tools become the primary management view.
Can you use Box Scores in shared services or back-office functions? Yes. Shared services and back-office functions have actual costs, performance measures, and capacity. A Box Score for shared services tracks the operational performance of the function, the actual costs incurred, and the capacity. What you don't do is allocate shared services costs into the value stream Box Scores. The allocation distorts the value stream financial picture and gives the value stream team no actual control over the costs they're being charged for. Nick was particularly emphatic about this. Costs belong where they're actually controlled. Driving behavior through allocations produces dysfunction because it tells teams to manage costs they don't have any way to manage.
How does Lean accounting interact with externally reported financial statements? The externally reported statements follow Generally Accepted Accounting Principles (GAAP) and have their own requirements. Lean accounting doesn't replace external reporting. The internal management tools — Box Scores, value stream income statements — can be reconciled to the external statements, but they exist for management decision-making rather than for external reporting. The role of accounting in a Lean company is to maintain both the internal management view and the external reporting requirements, and to be able to interpret between them. When continuous improvement produces operational change, accounting can explain what will show up in the short-term financials, what will show up only in the long-term financials, and what won't show up directly at all (capacity created but not yet used). The interpretive role is one of the most important contributions accounting can make to a Lean organization.
Are Box Scores part of regular monthly management reporting or are they project-specific? Both, but primarily the former. The Box Score is a tool for ongoing management practice — reviewed regularly, used to track trends, used as the context for operational decisions. For major improvement events, the team can use the Box Score to think through expected impact before the event and to verify actual impact after the event. The Box Score itself isn't event-specific. The events are evaluated through the lens of how they affect the standing Box Score for the value stream.
Do finance and CI professionals need to partner on this kind of analysis? Yes. The teams that produce the best Lean accounting outcomes work together to build the Box Scores and the value stream analyses. Finance and accounting professionals bring the financial discipline. Operational professionals bring the understanding of what's actually happening on the ground. Both sides learn from each other when they collaborate — accounting learns what's in the operational numbers they hadn't previously been close to, operations learns about cost structures and financial dynamics they hadn't previously had visibility into. The collaboration is the foundation of the practice working at scale.
.svg)
Copyright © 2026
Privacy Policy