Every company running a monthly close has a hidden cost problem. It just doesn’t show up as a line item.
The costs are spread across four or five departments, filed under “labor,” “admin,” or “overhead,” and no one questions them because the system has always worked this way. The invoices get paid. The reports get produced. Leadership gets a PDF on the 12th of every month.
This is exactly the situation kaizen was designed to fix. Not as a philosophy, but as a systematic method for finding the waste that accounting can’t see. Kaizen surfaces where the waste is; you need root cause analysis to diagnose why it exists.
Why Kaizen Isn’t Just a Factory Tool
Kaizen comes from Toyota’s production system, developed in post-war Japan as a survival mechanism. The premise is simple: waste is not inevitable. Every process has steps that consume time and money without creating value. Your job is to find them, name them, and eliminate them one by one.
Manufacturing adopted it first because waste on a factory floor is visible. You can see the part sitting on a shelf for three days. You can watch the worker walk across the warehouse to get a tool that should be at the workstation.
In a finance or operations team, the waste is invisible. It’s buried in spreadsheets, email threads, and “that’s just how we do it here.” No one measures it. No one names it. It compounds every month.
The gap between kaizen’s popularity as a concept and its application to finance operations is where the money hides.
Toyota’s 8 Wastes – Mapped to Finance Operations
Toyota identified eight categories of waste. Each one has a direct equivalent in any business that processes information, approves spending, or produces reports.
| Waste Type | Manufacturing Definition | Finance / Operations Equivalent |
|---|---|---|
| Transport | Moving materials between workstations unnecessarily | Re-keying data from ERP into Excel, then into slides. Every manual export is a transport event. |
| Inventory | Excess raw materials or finished goods waiting to be used | Slow-moving stock tying up working capital, uncleared AR aging past 60 days, prepaid expenses that never get reviewed |
| Motion | Unnecessary movement by workers to complete a task | Approval chains requiring 4 signatures for a EUR 500 decision, chasing a manager across three email threads to release a PO |
| Waiting | Idle time caused by upstream delays | Month-end close stalled because one department hasn’t sent cost center data. A controller sitting idle for 90 minutes. |
| Overproduction | Making more than the customer currently needs | Reports produced on schedule that no one opens. Dashboards built for stakeholders who left two reorganizations ago. |
| Overprocessing | Doing more work on a part than the customer requires | 47-page monthly reports when leadership reads three pages. Variance analysis calculated at the sub-cost-center level when decisions are made at the department level. |
| Defects | Products that don’t meet quality standards and require rework | Misbooked invoices requiring correction. Data errors that don’t surface until week three of the close. Reconciliation loops. |
| Unused Talent | Not using employee skills, knowledge, or capabilities | A senior controller spending eight hours per month on manual exports. A finance analyst with SQL skills doing copy-paste work instead. |
Run that list against your last month-end close. Count how many categories appear. Most finance teams find five or six without trying hard.
The question isn’t whether the waste exists. It’s whether you’ve ever sized it in euros.
The Finance Gemba Walk
In manufacturing, “gemba” means the actual place where work happens. The factory floor. Toyota managers are expected to go there and observe, not manage from a conference room.
In finance, gemba is the desk of the person running the process.
The finance gemba walk is simple: sit with your controller, your AP clerk, or your FP&A analyst and watch them work for 30 minutes. Don’t suggest. Don’t interrupt. Just observe and note.
What you will see is not what the SOP says.
You will see the spreadsheet with four tabs that consolidates data from three systems because the systems don’t talk to each other. You will see the email they send to three people every Thursday asking for numbers that should pull automatically. You will see the 20-minute detour they take every close to fix the same misallocation that happens every month.
None of that is in any documented process. It exists because someone built a workaround six years ago and it quietly became part of the job.
The process map you draw from observation will never match the process documented in the standard operating procedure. That gap is where your cost reduction lives.
For a broader view of where these inefficiencies show up across the P&L, the profitability analysis framework gives you a structured way to map cost patterns before you start running kaizen events.
What Kaizen Typically Surfaces in Finance Teams
These are not edge cases. They appear in almost every mid-market finance team that runs a process observation exercise.
- Month-end close waste: A five-day close in a EUR 30M company typically contains 40-80 labor hours of manual steps – re-keying, reconciling, consolidating. At EUR 60/hour fully loaded, that’s EUR 2,400 to EUR 4,800 per month in pure waste. EUR 29,000 to EUR 57,000 annualized.
- Report production nobody reads: Track open rates on your monthly reporting package for 90 days. In most companies, 30-40% of the pages produced are never opened by anyone with decision authority. The analyst who built that section spent time that created zero value.
- Approval process friction: A standard purchase order requiring four sign-offs costs roughly 45-90 minutes of total labor time. At EUR 500 average PO value, the approval cost can represent 8-15% of the transaction value for routine purchases. This isn’t control – it’s overhead.
- Inventory carrying costs: The financial mechanics here go deeper than most people realize. Excess stock isn’t just idle capital – it’s a compounding cost. The inventory cash trap breakdown shows how slow-moving stock quietly inflates your working capital requirement month after month.
- Data correction loops: Every misbooked invoice triggers a correction cycle. In a company with 2,000 invoices per month and a 3% error rate, that’s 60 correction events. At 25 minutes each, that’s 25 hours per month of rework – work that exists solely because the original work was done incorrectly.
A Kaizen Event on Your Month-End Close
A kaizen event is a focused, time-boxed improvement sprint. In manufacturing, these run three to five days on a specific production line or process. The same structure works on any repeatable business process.
Here is what a three-day kaizen event looks like when applied to the month-end close.
Day 1 – Map the Current State
Get everyone in the same room who touches the close: the controller, the FP&A lead, the AP and AR team leads, the management accountant. Ask them to walk through every step they personally own, in order, with timing.
Write it on paper. Literally. Post-its on a wall work better than a Visio diagram because everyone can contribute and move things around.
The output is a process map with every step, every handoff, and every wait labeled. For each wait, note: who is waiting, what they’re waiting for, and how long the average wait is. For each handoff, note: how the information transfers (email, shared drive, phone call, re-keyed manually).
By end of day, you should have a map that looks far more complicated than anyone expected. That is correct. That is the current state.
Day 2 – Identify, Classify, and Size the Waste
Go through each step on the map with the eight waste types visible on a whiteboard. For every step, ask: does this create value for the person receiving the output, or is this a step that exists because of how the process was designed?
Classify each waste step. Then size it.
Sizing formula: (hours per occurrence) x (occurrences per month) x (fully loaded cost per hour) = monthly waste cost.
Do this for every waste step you can quantify. Add them up. This is your waste baseline. Write it down as a single number. Make it visible.
A EUR 40M company typically finds EUR 3,000 to EUR 8,000 in monthly waste in its close process alone. The number is rarely less than EUR 1,500 and rarely more than EUR 15,000. Both ends of that range are financially meaningful.
Day 3 – Design the Target State and Assign Actions
You are not trying to build the perfect process on day three. You are designing a realistic next state that eliminates the waste you identified and can be implemented within 30 days without a technology project.
Most month-end close waste can be reduced by 40-60% without buying new software. The fixes are structural: changing handoff mechanisms, eliminating approval steps that add no control value, automating one or two manual exports with a scheduled job or a basic script.
Assign each action to one owner with a 30-day completion date. Schedule a 90-minute check-in for day 30. That check-in is where you measure whether the waste baseline moved.
This connects naturally to how you think about finance reporting automation. Once you’ve mapped the process and eliminated the structural waste, the question of what to automate becomes much clearer. The finance reporting automation guide picks up from that point.
Monday Morning Playbook
What to do Monday morning:
- Pick one finance process that annoys everyone (month-end close, expense reporting, budget cycle).
- Sit with the person who runs it. Watch them do it for 30 minutes. Don’t suggest, just observe.
- Count: how many times do they re-key data? How many systems do they touch? How long do they wait for someone else?
- Map it on paper: [step] – [wait] – [step] – [rework] – [step]. Circle every wait and every rework.
- Calculate: if each rework cycle costs X hours at Y per hour, and happens Z times per month, the annual waste is [number].
- Present: “I observed our [process] and found [X hours/month] in waste from [rework/waiting/manual steps]. Here’s what a streamlined version looks like.”
The observation step is the one most people skip. They go straight to “here’s what I think we should change” based on their experience of the process, not their observation of it. The observation is what gives you specificity, and specificity is what gives you a budget conversation.
The Sentence That Gets You Noticed
“I mapped our month-end close process step by step and found 40 hours per month in manual steps that could be eliminated. That’s half an FTE.”
That sentence does three things at once. It shows rigor (you mapped it, not estimated it). It attaches a number (40 hours). And it translates the number into a term that any CFO or COO understands immediately (half an FTE).
Controllers who speak in process language stay in operations. Controllers who speak in FTE equivalents and annualized cost reductions get promoted into decision-making roles.
Kaizen gives you the methodology to generate that sentence legitimately – not as an estimate, but as a finding from direct observation.
Questions CFOs Ask About Kaizen
Is this different from a cost reduction program?
Yes, in one critical way. A cost reduction program typically starts with a target (reduce costs by 10%) and works backward to find cuts. Kaizen starts with observation and surfaces waste that wasn’t visible before. The result is a cost reduction, but the process is diagnostic rather than arbitrary. You end up cutting waste, not capability.
How long before we see results?
Process waste identified in a kaizen event can typically be addressed within 30-60 days if it doesn’t require a technology implementation. Structural changes to approval workflows, handoff mechanisms, and reporting formats are largely administrative. A three-day kaizen event on the month-end close should show a measurable reduction in close time within two cycles.
What if the waste is in a process I don’t own?
Map it anyway and present the finding. The observation data does the persuasion. “Your department sends us data on day four, and our team sits idle for six hours waiting for it” is a concrete, non-political framing that makes the problem actionable. Most process owners respond to specificity better than they respond to general requests to collaborate.
How does this fit with our budgeting process?
Kaizen and zero-based budgeting are complementary but ask different questions. ZBB asks: should this cost exist at all? Kaizen asks: if this cost should exist, how much of it is waste? Running them together – ZBB to challenge cost categories, kaizen to optimize the processes behind the ones that survive – is the most aggressive cost management combination available to a mid-market finance team.
How Deep to Go: Three Difficulty Levels
Not every situation calls for a three-day event. Here’s how to calibrate.
Level 1 – 30 Minutes (Individual Observation)
Pick one process. Sit with the person who runs it. Watch them work for 30 minutes. Count the manual steps, the waits, and the rework events. Write down three things you observed that weren’t in any SOP. Calculate the cost of one of them.
This is enough to start a conversation with your manager or your CFO. It establishes the habit of process observation before process criticism.
Level 2 – Half Day (Full Process Map with Cost Sizing)
Bring the three or four people who touch a single process into a room for a half day. Map every step together. Classify waste types. Size the three largest waste events in euros per month. Produce a one-page summary with the waste baseline and two or three proposed changes.
This is the right level for a controller who wants to run one meaningful improvement project per quarter.
Level 3 – Three-Day Kaizen Event
Full current-state map across a department or cross-functional process. Waste sizing for every identified step. Target state design. Action register with owners and dates. 30-day check-in scheduled before everyone leaves the room.
This is appropriate for processes that cost more than EUR 50,000 per year in identifiable waste, or any process that repeatedly delays a critical output (close, board reporting, annual budget).
The finance dashboard post covers which metrics to track once you’ve eliminated the structural waste and want to measure the actual performance improvement: finance dashboard design and KPI selection.
Frequently Asked Questions
What is kaizen?
Kaizen is a Japanese business philosophy, originating at Toyota, that focuses on continuous incremental improvement. The word translates roughly to “change for the better.” In practice, it’s a structured methodology for identifying waste in any repeatable process and eliminating it systematically, without large-scale restructuring.
What is a kaizen event?
A kaizen event (also called a kaizen blitz or rapid improvement event) is a focused, time-boxed improvement sprint targeting a specific process. Typically three to five days, it brings together everyone who touches the process to map the current state, identify waste, design an improved future state, and assign concrete actions with deadlines. The goal is measurable results within 30-60 days, not a long-term change management program.
How is kaizen different from Six Sigma?
Kaizen focuses on speed and direct observation. You identify waste through gemba walks and process mapping, then act quickly. Six Sigma uses statistical analysis to identify and eliminate defects, typically over a longer project cycle (DMAIC: Define, Measure, Analyze, Improve, Control). Many organizations use both: kaizen for rapid operational improvements, Six Sigma for complex process quality problems with quantifiable defect rates. For most mid-market finance teams, kaizen is the more accessible starting point.
Does kaizen work in office and service environments?
Yes – and it’s arguably more valuable in office environments than manufacturing, because office waste is invisible by default. In a factory, a pile of unfinished parts is physically observable. In a finance team, the equivalent waste is hidden inside email inboxes, spreadsheet workflows, and approval chains. Kaizen in service environments has a higher discovery yield precisely because no one has looked for the waste systematically before.
I write about the money hiding in company data. One dispatch per month, real findings, no filler.