Your Spreadsheet Isn't Broken. Your Process Probably Is.
I have looked at a lot of messy spreadsheets. Workbooks with 14 tabs and no clear logic connecting them. Files where three different people paste data into the same sheet on different days using different formats. Revenue trackers that started as a quick Monday morning reference and somehow became the backbone of a company's entire financial reporting.
Every time, the first instinct from the owner is the same: "Can you fix my spreadsheet?" And nearly every time, the spreadsheet is not actually the problem.
How the patchwork happens
Owner-operators build their businesses around what they sell and how they serve their customers. That is where their attention belongs, and it is where their expertise lives. The tools they use along the way, the spreadsheets, the trackers, the scheduling files, those get built to solve the problem right in front of them at the time. Nobody sits down during year one and designs a scalable data architecture for a 12-person company. You open a spreadsheet, you track what you need to track, and you move on to the work that actually pays.
The issue is that this happens dozens of times over the life of a growing business. A new tab gets added when a new product line launches. A separate file gets created when someone needs to track a process that did not exist six months ago. A column gets repurposed because it was easier than restructuring the whole sheet. Each of these decisions makes perfect sense in the moment, and none of them are mistakes. They are rational responses to real needs under real constraints.
But over time, the result is a patchwork. The workbook is not a system anyone designed. It is an accumulation of quick fixes layered on top of each other, and it reflects every stage the business went through to get where it is now. That is why it feels broken. Not because someone wrote a bad lookup formula, but because the tool was never built to do what the business now needs it to do.
The spreadsheet is a mirror
Here is the mental shift that changes everything: the spreadsheet is just a reflection of the process behind it. Whatever is happening in your operations, whether that is how transactions flow, how work gets assigned and completed, how inventory moves, or how customers get invoiced, the spreadsheet is showing you the shape of that process. If the process is messy, the spreadsheet will be messy. If the process has gaps, the spreadsheet will have gaps.
This is actually good news, because it means you do not have to become an Excel expert to fix the problem. You have to understand your own process clearly enough to define what the tool should be doing. The spreadsheet is downstream of that understanding, not upstream of it.
I spent eight years in management consulting before starting Old North Analytics, and the single most transferable skill from that work is not building models or writing formulas. It is looking at how information moves through an organization and identifying where the breakdowns are. In a large enterprise, those breakdowns hide inside complex systems and long approval chains. In a small business, they hide inside spreadsheets. The diagnostic instinct is the same.
What "fixing it" actually means
When I work with a small business owner on a spreadsheet problem, the build itself is usually the shorter part of the engagement. The longer and more valuable part is the conversation about what the tool needs to do and why.
That conversation starts with process. How does the data get into this file? Who touches it and when? What decisions does it support? What questions should it answer that it currently cannot? Most of the time, the owner has never mapped this out explicitly. The process just evolved, and the spreadsheet evolved with it.
Once you have a clear view of the process, you can make real decisions about structure. What data belongs in this workbook and what belongs somewhere else? What is the right level of detail? What calculations matter for the decisions the owner actually makes on a weekly or monthly basis? These are not technical questions. They are business questions with technical answers.
From there, the build is about targeting the right KPIs and structuring the data so it delivers those KPIs reliably. Not a dashboard with 30 charts. Not a report that takes an hour to update every Monday. A clean tool that tracks what matters, surfaces the numbers the owner needs to allocate resources and evaluate performance, and scales as the business adds complexity. That last part is important, because the whole reason the original spreadsheet broke down is that it was not built to grow. The replacement should be.
The formula is never the real finding
I rebuilt a tracking workbook recently for a business that had been running on a spreadsheet originally put together two or three years prior. The owner's complaint was that the numbers "never seemed right" and that reconciling the file at the end of every month took most of a day. When I looked at it, the formulas were fine. Every calculation did exactly what it was written to do.
The problem was that the file had been designed around a workflow that no longer existed. The business had added a service line, changed how it invoiced, and shifted from weekly to biweekly billing cycles, but the spreadsheet still reflected the original structure. Data was getting entered in places that no longer mapped to how the business actually operated, and the monthly reconciliation was essentially the owner manually correcting for the drift between the tool and reality.
We did not fix the spreadsheet. We rebuilt it around the current process, with the right inputs, the right structure, and a few well-chosen metrics that gave the owner a real view of performance across both service lines. The monthly reconciliation went from most of a day to about 20 minutes, not because the new formulas were better, but because the data was finally organized around how the business actually works.
Start with the process
If your spreadsheet feels broken, resist the urge to start troubleshooting formulas or redesigning tabs. Start by writing down, even roughly, the process the spreadsheet is supposed to support. How does information enter the file? What happens to it? What should come out the other end? If you cannot describe that clearly, the spreadsheet will never work well no matter how clean the formulas are.
The tool is just the container. The process is the thing that makes it useful. Get clear on the process first, and the spreadsheet practically builds itself.

