Every continuous improvement program starts somewhere, and that somewhere is almost always a spreadsheet.
This makes sense. Excel is already on every computer. People know how to use it. Rows and columns are a logical way to organize a list of improvement ideas. For a small team running a handful of projects, a well-built spreadsheet can work fine for months, even years.
The trouble is that spreadsheets don't fail all at once. They fail gradually, in ways that are hard to see from the inside. A missed follow-up here. A stale status column there. A quarterly report that takes two weeks to assemble because the data lives in 15 different files across six departments. By the time someone says "this isn't working anymore," the program has already been operating below its potential for a long time.
This isn't a knock on Excel. It's a recognition that spreadsheets were designed to calculate and organize data, not to manage a living organizational system with hundreds of participants, shifting priorities, and compounding results. Understanding where that structural mismatch shows up is the first step toward knowing when you've outgrown the tool.
Invisible Work
The most damaging spreadsheet problem is the one nobody talks about in meetings: work that's happening but can't be seen.
When improvement activity lives in spreadsheets -- whether it's a shared Google Sheet, a department-specific Excel file, or a collection of trackers scattered across a SharePoint site -- the only people who know what's happening are the people who remember to open the file and scroll through it. There are no automatic notifications when someone submits a new idea, updates a status, completes a task, or needs a decision.
This passivity is the core design limitation. Spreadsheets store information. They don't move it. They don't alert the right person at the right time. They don't surface what's stalled, what's overdue, or what needs attention. If a frontline worker submits an improvement idea and their manager doesn't happen to check the spreadsheet for two weeks, that idea sits in silence. After a few rounds of that, the worker stops submitting.
At Mohawk Paper, the team recognized this limitation early. As they described it, spreadsheets and Microsoft Access applications weren't enterprise-wide -- they weren't going to be available to everybody. The work existed, but it was invisible to anyone outside the immediate team that created it.
"We found a Microsoft Access template somewhere on the internet and we built it out a little bit, and were using that to track our opportunities for improvement -- capturing them, tracking them, and getting them closed out." -- Tom Whitaker, Mohawk Paper
No Accountability Without Automation
Spreadsheets can assign ownership. You type a name in a column. But there's a vast gap between recording who's responsible and actually creating accountability.
Accountability in CI work requires active follow-up: automated reminders when a task is approaching its due date, escalation when something goes overdue, notifications to coaches and leaders when a team needs support. These aren't optional niceties for a mature program. They're the mechanisms that keep hundreds of improvement activities moving forward simultaneously.
In a spreadsheet, all of this follow-up happens manually. Someone has to review the tracker, identify what's behind schedule, and send emails or Slack messages to the responsible parties. That "someone" is usually the CI team lead, which means a significant portion of their week is consumed by administrative chasing rather than coaching and problem-solving.
Tirlan, a large food and dairy cooperative, experienced this directly. As they scaled their continuous improvement efforts organization-wide, their CI team found themselves constrained by Excel and PowerPoint-based systems. The team was spread too thin, growing tired of chasing down teams to submit updates and manually driving accountability. After enough frustration, they began searching for a digital solution that could handle the follow-up automatically.
"Before KaiNexus, our 3M leads spent countless hours chasing updates and managing spreadsheets; now they can instantly see project and KPI status' and focus on what truly matters. With all the time saved on administrative work, our leaders can finally tackle important continuous improvement initiatives they never had the capacity for before." -- Michael Phelan, Head of Operations & Supply Chain Excellence, Tirlán
KaiNexus replaces that patchwork with a single platform where every improvement -- submitted, in progress, or completed -- is visible to anyone who needs to see it. Leaders don't have to go looking for the work. The work comes to them through smart notifications that surface what needs attention, when it needs it.
The Impact Measurement Gap
Ask a CI leader what keeps them up at night and you'll often hear some version of:
"I know we're making a difference, but I can't prove it with the numbers the CFO needs."
Spreadsheets make this problem almost unsolvable at scale. Here's why.
Impact measurement for CI requires capturing the financial or operational result of each individual improvement, validating that number through a consistent review process, and then aggregating all of those validated results across the organization -- by department, by facility, by strategic objective, by time period. The output should be a defensible number that answers: "What did our improvement program produce this year?"
In a spreadsheet, each of these steps introduces friction and error. Impact data gets entered inconsistently -- one team records annualized savings, another records one-time savings, a third skips the field entirely. There's no built-in validation workflow, so the numbers are whatever someone typed. Aggregation means manually summing across multiple files, hoping the formulas are right, and praying nobody accidentally deleted a row.
Purpose-built CI software handles impact capture at the individual improvement level, with configurable templates that standardize how teams document results. Those results flow through a defined validation process -- finance review, manager approval, whatever the organization requires -- and then aggregate automatically. That's how organizations can report that the average employee-driven improvement generates $25,000 in annualized value, or that their program produced eight figures in documented savings. That number exists because the system was designed to produce it. No spreadsheet was.
Version Control and the Single Source of Truth Problem
Anyone who's managed CI work in spreadsheets has experienced the moment: you open the tracker and realize you're looking at a version from three weeks ago. Or two people edited the same file and one set of changes was overwritten. Or the "gold" copy lives on someone's laptop and they're on vacation.
Cloud-based spreadsheets (Google Sheets, Excel Online) have reduced this problem, but they haven't eliminated it. When improvement data spans multiple files -- a project tracker here, an A3 template there, a separate impact log somewhere else -- there is no single source of truth. Related information lives in different places, maintained by different people, updated on different schedules.
UMass Memorial Health described their pre-software state with clarity: they had Trello boards across the organization, Google Docs, and spreadsheets shared through Zoom or WebEx. The information existed, but it was fragmented across tools and teams. Finding out what was actually happening required assembling pieces from multiple sources -- an exercise that consumed time and still produced an incomplete picture.
A single system of record eliminates this entire category of problem. Every improvement, every status update, every comment, every attached document, every impact number lives in one place. Anyone with the right access can see the current state at any time, without assembling a report from scattered files.
Methodology Without Enforcement
CI practitioners work in structured frameworks -- PDSA, DMAIC, A3 thinking -- for good reason. These methods force disciplined problem-solving: understand the current state before proposing solutions, identify root causes before testing countermeasures, measure results before declaring victory.
A spreadsheet can mirror these frameworks cosmetically. You can label columns with PDSA stages or create tabs that follow A3 sections. But the spreadsheet doesn't care whether someone fills in the root cause analysis before jumping to "implement solution." It doesn't prompt for a measurable target. It doesn't flag when a team skipped the hypothesis step and went straight to action.
This matters because the rigor is the point. Without it, PDSA becomes "we tried something and it seemed to work." DMAIC becomes a project plan with a fancy acronym. The methodology degrades silently, and the only people who notice are the coaches -- who are already stretched thin.
Purpose-built CI software can embed methodology logic into the workflow: require certain fields before advancing to the next stage, prompt for expected outcomes before allowing a test to proceed, flag when a project moves to implementation without documented measurements. The tool doesn't replace coaching, but it creates a structural baseline that prevents the most common shortcuts.
Strategy Alignment That Exists Only on Paper
Most spreadsheet-based CI programs can't answer a simple question: which of our current improvement projects are aligned to our top three strategic priorities?
You might have a column labeled "Strategic Objective" in your tracker. Some people fill it in, some don't. The ones who do may not be using consistent terminology. Rolling it up into a picture of where organizational effort is concentrated relative to strategic priorities means manually categorizing, cross-referencing, and building a separate summary -- usually in another spreadsheet.
Tirlan's experience illustrated this gap. Despite organization-wide participation in their improvement efforts, teams struggled to see the full picture of KPIs and projects across departments through Excel. This led to duplication of effort -- different teams unknowingly working on the same problems in isolation. The Excel templates that had once helped standardize the work became a bottleneck as the program grew.
Purpose-built CI software creates structural connections between individual improvements and strategic objectives, making it possible to see at a glance where effort is concentrated, where gaps exist, and which strategic goals have the most (or least) improvement activity supporting them.
The Culture Tax
There's a cost to spreadsheets that doesn't show up in any budget line: the erosion of engagement.
When someone submits an improvement idea into a spreadsheet, they get nothing back. No confirmation that it was received. No notification when someone reviews it. No update when it moves forward. No recognition when it's completed. No visibility into the impact it created.
This silence is a participation killer. Most organizations running suggestion-style systems see implementation rates around 2-3%. The ideas go in, but nothing visibly happens, so people stop contributing. The system doesn't fail dramatically. It just quietly goes dormant.
Purpose-built CI software creates a feedback loop: submission confirmed, reviewer assigned, status updated, impact measured, results shared. Each touchpoint reinforces the message that the organization takes improvement seriously and that individual contributions matter. That reinforcement loop is the difference between a spreadsheet that collects dust and a system that sustains engagement over years.
When Excel Is Still the Right Tool
To be clear: spreadsheets are great at what they're designed for. If you're a small team tracking a manageable number of projects and you have one person who owns the tracker and keeps it current, Excel can work. If you're running a Kaizen event and need a quick way to capture action items for the week, a shared Google Sheet is fine.
The breakpoint comes when the program grows beyond what one person can manually manage. When you have multiple departments, multiple facilities, hundreds of active improvements, and leaders who need to see the aggregate picture -- that's when the spreadsheet's structural limitations become organizational drag. Not because Excel is bad software. Because it was never designed to manage what a continuous improvement program becomes at scale.
The organizations that have made the transition -- Tirlan, UMass Memorial, Mohawk, and many others -- didn't switch because spreadsheets stopped working entirely. They switched because they recognized that the manual effort required to hold the system together was consuming time that could be spent on actual improvement. The spreadsheet had become the bottleneck.
"KaiNexus is helping us support and sustain a culture of incremental improvements coming from staff, developing our staff to not only do their jobs, but also to make their jobs better." -- Brian Dieter, CEO, Mary Greeley Medical Center
.svg)
Add a Comment