Fix the Process Before You Buy the Software

I’ve watched companies spend serious money on ERP systems and end up worse off than before — not because the software was bad, but because they installed a powerful tool on top of a broken process. You can’t automate your way out of chaos. You just get faster chaos.

I learned this running ERP rollouts across more than ten companies — billing, accounting, purchasing, warehouse modules — and training staff in over fifty branches. The pattern was always the same: the companies that mapped and fixed their processes first got real results. The ones that skipped that step got expensive frustration.

Why software alone doesn’t fix anything

A broken process has three ingredients: unclear ownership, unnecessary steps, and decisions made by whoever happens to be nearby. Software doesn’t remove any of those — it just digitizes them. Your approval bottleneck becomes a faster approval bottleneck. Your duplicate data entry becomes duplicate data entry with a nicer interface.

When a company says “the ERP didn’t work,” what they usually mean is “we kept doing things the old way, but now we also have a system to blame.”

Map the as-is, honestly

Before selecting anything, document how work actually flows today — not how the procedure manual says it should, but how it really happens on a Tuesday afternoon.

Walk through one real transaction: a purchase order, a customer invoice, a warehouse receipt. Follow the paper trail, the email chain, the spreadsheet someone maintains “just in case.” You’ll find steps that exist because they always have, approvals that delay without adding control, and data entered in three places because nobody designed the handoffs.

This map is uncomfortable. It’s also the most valuable document in the project.

Remove and simplify before you configure

With the map in front of you, ask two questions about every step:

• Does this step add control, or just delay? Some approvals catch real problems. Others exist because someone didn’t trust someone else a decade ago.
• Does this step produce information anyone uses? Reports nobody reads, fields nobody fills correctly, reconciliations that exist to check other reconciliations — cut them.

Then simplify what’s left. Combine steps that belong together. Assign clear owners. Write down the rules — who approves what, at what threshold, in what order. This is the process your software should run. If you can’t describe it in plain language, you’re not ready to configure a system.

Then select and configure the system

Now you’re choosing software to match a designed process, not hoping software will create one. This changes the evaluation entirely:

• You can test whether the system handles your actual workflows instead of being impressed by demos.
• You configure what’s needed, not everything the vendor shows you.
• You know which customizations are worth paying for and which are adapting the software to habits you should have dropped anyway.

During my ERP rollouts, the companies that arrived with a clean process map finished configuration in weeks. The ones still arguing about how things “should work” took months and ended with compromises nobody liked.

Train on the process, not just the screens

Users who understand the process learn the software in days. Users who memorize button sequences forget them by Friday.

Train people on why the process works the way it does — then show them which screens execute their part. When something goes wrong, they’ll understand what broke instead of just knowing that the thing they usually click isn’t working.

A warning about scope

Once you start mapping, you’ll find more broken processes than you can fix in one project. That’s fine — it’s actually the healthy outcome, because it means you’re seeing the operation clearly for the first time. Resist the urge to fix everything at once. Pick the two or three processes that cost the most in errors, delays, or cash, fix those, and let the rest wait their turn. An ERP rollout scoped to a few clean processes succeeds; one scoped to the whole company’s chaos becomes a multi-year hostage situation.

Where to start

1. Pick your most painful process — usually purchasing or invoicing.
2. Map it as-is with the people who actually do the work.
3. Remove steps that don’t add control or useful information.
4. Assign owners and document the rules.
5. Then evaluate software against the clean version.

The companies that get real value from ERP aren’t the ones with the biggest budget or the fancier system. They’re the ones that did the boring work of understanding their own operation before asking software to run it.

If you’re considering a system and something feels off about the process it would run — trust that instinct. Fix the process first.