You bought the software and still use spreadsheets

The spreadsheet is a diagnosis, not a mess

Open the spreadsheet you keep next to the system and look at the columns. Two or three of them don't exist in the platform: a date you track and it doesn't, an in-between status, a number you work out by hand. Those columns are your actual process. Everything else is a copy of something already stored somewhere else.

Then look at who updates it and when. If it's the same person who enters the data, five minutes after entering it, what's missing is a field. If it's a different person at a different point in the day, what's missing is a whole step: part of the operation never made it into the platform at all.

Nobody keeps a parallel spreadsheet for fun. It costs you double entry, it creates two versions of the same number, and somebody has to remember to update it every week. If it survives anyway, it's because it answers a question the platform doesn't. Find that question before you change anything.

Your process is the problem when nobody can explain the step

Take every column that lives outside the system and ask what it's for. A useful answer sounds like this: "the customer wants the PO number on the invoice," or "I can't bill without it." The answer that gives you away sounds like this: "that's how we've always done it," or "the old office manager wanted it" — and she left two years ago.

The second test is to stop doing it. Pick one step, tell the team it's suspended, and wait one full cycle: in most service businesses that's a month, because it has to include a billing run. If nobody complained and nothing broke, that step didn't belong to the business. It belonged to a constraint that's gone.

Most odd processes were reasonable once. They were built around a paper form, a previous system, or one person who checked everything before it went out. The constraint disappeared and the step stayed. When that's what's happening, the software isn't wrong. It's showing you, in slow motion, something you stopped needing.

The software is the problem when its main object is not yours

Every platform has one central object everything else hangs off: the contact, the deal, the ticket, the order. If your unit of work isn't on that list, you'll spend your life translating. It's the same argument you run into when picking a system in the first place, laid out in when a business needs a CRM and when it doesn't.

The most reliable symptom is the notes field. When statuses, owners or amounts live inside a free-text box, it's because the tool has no concept for them. Check whether two people write the same thing two ways: "waiting on approval," "pending customer OK." That's not sloppiness. It's a status the system doesn't model.

The other clear case is a hard assumption. A system that assumes one currency when you get paid in three, or one job per address when you run five phases on the same house, doesn't get fixed with training or with discipline. There the software is wrong, and it doesn't matter how many stars it has.

What to do in each case, and by what date

If the process is the problem, the spreadsheet closes on a date, not on a request. Pick the day, move the two columns that actually matter into a field in the system, and take away access to the file. With no date it doesn't die, it coexists, and three months later it has ten columns again.

If the software is the problem but the gap is small, a custom field, a secondary object or a small integration that pushes the record where you need it usually covers it. That's hours of work, not months, and it comes before automating anything: automating a step before you know whether the step should exist only makes the mistake arrive faster and more often. The right order is in where a small team should start automating.

If the software is wrong at the center, replacing it isn't the first move. Write one sentence naming your unit of work and what has to hang off it. Test what you already own against that sentence, and only if it doesn't fit do you go look at anything else. Migrating without that sentence written down lands you in the same place six months later with newer data. The spreadsheet, meanwhile, isn't something you ban. It switches off on its own the day its question gets answered somewhere better.