Lean Process Redesign on a Legacy ERP
The ERP was not going anywhere, and it did not need to. I cut the manual work built up around it so the team could grow without adding headcount.
The situation
A fresh-cut processor was running on a legacy produce ERP, and replacing it wasn’t on the table. Fair enough. The system did its core job, the pain didn’t justify a seven-figure replacement with years of disruption attached, and nobody was interested in a consultant showing up to pitch one.
The real problem was narrower and more expensive than it looked. A process the ERP should have handled, but couldn’t, was being done by hand around it: re-keying between screens and spreadsheets, email chains standing in for handoffs, and side workbooks duplicating what the system already tracked. Every bit of growth meant more manual hours, so headcount was quietly scaling with volume instead of with the business.
What I did
I met them where they were. The engagement started from a plain premise: the ERP stays, so let’s make the work around it stop costing so much.
I began with Lean process mapping, walking the real flow of work from order to invoice rather than the flow in the procedures manual. We traced where information was entered, re-entered, printed, re-typed, and lost. Most of the overhead lived in the gap between what the ERP could do and what the process needed, and in steps that existed because “we’ve always done it that way.”
Then we redesigned the process around that reality. We eliminated the duplicate entry, retired the shadow spreadsheets, and made ownership of every handoff explicit. Where the ERP genuinely couldn’t carry the process, we separated real requirements from habit and covered the short list that remained with configuration and a few targeted reports, built to work with the system instead of against it.
What changed
Order-to-invoice time dropped by a third, and the overhead hours went with it. Data entry errors fell along with the re-keying that caused them, and supervisors got their afternoons back from daily firefighting.
The bigger change was in how the company scales. The same team now absorbs more volume without adding staff, because growth no longer arrives as a stack of manual work. And the ERP decision stayed where it belongs: with the client, on their timeline, for when the pain actually justifies it.