A single process improvement does not change profitability uniformly across the business. The same Kaizen touches transactions, products, customers and channels in very different proportions, and only a costing system can show how. With Time-Driven Activity-Based Costing (TDABC) feeding a multidimensional profitability model, one improvement cascades up the levels in front of you: transaction, then product or SKU, then customer, then channel, then business unit, then company. A Lean dashboard or a Six Sigma project charter stops at the activity. This is where the shop floor meets the boardroom.
Why one improvement is not one number
Imagine a Kaizen that shortens an order-handling activity. On the floor, it is a single, clean result: minutes per order fall. But that activity is not consumed evenly. A high-volume customer who places many small orders consumes it constantly. A customer who places a few large orders barely touches it. The same improvement therefore delivers a large effect to one customer’s profitability and almost none to another’s.
Now multiply that across every dimension. The orders run through different products, each with its own mix of activities. The products sell through different channels, each with its own cost to serve. The improvement that looked like one number on the A3 is, in financial reality, dozens of different numbers depending on which slice of the business you stand in. A single average hides every one of them.
The cascade, level by level
TDABC traces cost along the path of the work, so an improvement at the activity level flows naturally upward to every dimension that consumed that activity. The table shows the same Kaizen seen from each level.
| Level | What the same Kaizen reveals here |
|---|---|
| Transaction | The repriced cost of a single order or processing event |
| Product / SKU | Which products absorbed the activity, and by how much their unit cost fell |
| Customer | Which customers became more profitable, and which are still in the red |
| Channel | Whether a high-cost-to-serve channel finally clears its margin |
| Business unit | The aggregate margin shift for the unit that owns the process |
| Company | The total effect on profit, and where freed capacity should go next |
Each level answers a different person’s question. The plant manager cares about the transaction and the product. The commercial director cares about the customer and the channel. The CEO cares about the business unit and the company. One model, one improvement, six audiences, and they finally see the same event in their own language.
Why a Lean dashboard cannot show this
A Lean dashboard is built around the process. Its native objects are the value stream, the cycle time, the takt, the waste category. These are the right objects for improving the work, and the wrong objects for understanding profit, because profit lives in dimensions the dashboard does not carry. A value-stream map has no column for “customer” and no row for “channel.” It was never meant to.
A Six Sigma project charter has the same boundary. It defines a problem, a metric, a defect, a target. It can prove that the process now performs within specification. It cannot tell you that the customer whose orders run through that process is still loss-making at the contribution line, because the customer is simply not in the charter’s field of view. The charter ends where the financial question begins.
This is not a criticism of either tool. It is a statement of scope. Lean and Six Sigma operate on the process; profitability lives across dimensions; and nothing in the improvement toolkit reassembles the second from the first. TDABC does, because it was designed to trace cost along the same paths that revenue and customers and channels run on.
The strategic payoff
When you watch the cascade, you learn things no operational report could tell you. Two findings recur in practice, both illustrative of the pattern.
The first is the quiet win. An improvement lands on a product line that the old cost model had buried below its hurdle rate. With the activity repriced, the line clears. A product you were close to discontinuing is, in fact, profitable, and you nearly killed it on bad cost data. That is a strategic decision reversed by a single Kaizen seen through the right lens.
The second is the uncomfortable one. The improvement works, the product cost falls, the floor celebrates, and the TDABC model shows that the largest customer running through that process is still loss-making. The Kaizen helped, but not enough, because the real cost driver for that customer was never the improved activity at all. It was order frequency, or returns, or special handling that the model now makes visible. The improvement was real and the customer is still unprofitable, and now you know it, and you can act on it: renegotiate, restructure the service, or set a minimum order. Without the cascade, you would have celebrated and lost money in the same quarter.
Putting the cascade to work
The practical move is to stop treating improvement and profitability as separate disciplines owned by separate teams. Run the Kaizen, then run its effect through a TDABC-based profitability model and read it at every level. This is the multidimensional view at the centre of our Lean Six Sigma and TDABC pillar, and it builds directly on converting saved minutes into profit and on the reasons improvement projects fail financially when nobody traces the cascade.
To see what a cascade would reveal in your own business, start with a free Profit Check, read how we work and what a ProfitAudit 360 uncovers, or book a scoping call. The shop floor finds the improvement. TDABC carries it all the way to the boardroom.