The Biological Variable vs. The Widget
The steam from the liming vats is thick enough to swallow a person whole, and Elias is currently drowning in it, though not physically. He is holding a 9-ounce piece of top-grain steer hide in his left hand and a smartphone in his right. On the other end of the line is a support representative named Kevin, who is likely 29 years old and sitting in a climate-controlled office in a zip code that has never smelled the pungent, earthy reality of a working tannery. Elias is trying to explain that a hide is not a ‘widget.’
Kevin, meanwhile, keeps suggesting that Elias should just use the ‘notes’ field for the hide thickness and the specific dye lot number.
[The notes field is where data goes to die.]
⚠️ Category Error Detected
As a debate coach, I spend most of my 39-hour work week teaching students how to identify category errors. A category error occurs when you apply a property to a thing that cannot possibly possess that property-like saying ‘the number 9 is thirsty.’
What we are seeing in the modern enterprise software market is a massive, systemic category error. Developers are building software for ‘businesses,’ but they are defining ‘business’ as a lemonade stand.
The 79 Shades of Red
In the garment and leather industry, the nuance is everything. You cannot simply list ‘Red Leather’ in an inventory system and expect to run a profitable operation. You have 79 different shades of red, each tied to a specific dye lot number that must be tracked against the pH levels of the tanning drums from 39 days ago.
Generic systems flatten these 79 unique requirements into one line item.
If you use a generic system, those 79 shades are flattened into a single line item. When a high-end designer calls wanting to match the specific oxblood finish from the spring collection, the manager has to go running into the warehouse to check physical tags because the $1099-a-month software thinks red is just red. This is the ‘Lemonade Stand’ mentality. It treats the complexity of manufacturing like the simplicity of a transaction.
“
I feel a strange, nagging guilt about this today, mostly because I gave the wrong directions to a tourist this morning. They were looking for the historical museum, a 9-minute walk to the north, but I pointed them toward the old wharf, which is a 19-minute trek in the complete opposite direction. I knew I was wrong the moment they turned the corner, but the momentum of my own perceived authority kept my mouth shut.
🌌 Missing the Soul
Generic ERP software is that student [who reduces art to math]. It sees the numbers, but it misses the soul of the work. It misses the fact that in a garment factory, the ‘waste’ isn’t just a loss; it’s a variable that needs to be calculated based on the grain of the fabric, which changes every 29 yards. To the software, it’s just a percentage. To the cutter, it’s the difference between making 99 jackets or 89.
The Demoralization of Expertise
This isn’t just about data entry. It’s about the demoralization of the expert. When a master tanner or a lead seamstress is told that their specialized knowledge-the stuff that takes 29 years to acquire-has no place in the digital record of the company, they stop caring. They become data entry clerks for a system that doesn’t respect them.
Year 1: Apprenticeship (The Grind)
Learning basic physical tolerances.
Year 15: Mastery of Variables
Understanding the 109 factors of quality.
Year 29: Digital Friction
Forced translation into a rigid system.
The friction of trying to bend a rigid, generic tool to fit a fluid, complex process creates a heat that eventually burns out the best employees.
The Hidden ‘Generic Tax’
We are told that customization is a luxury… This is a lie designed to keep you paying for a subscription that doesn’t work. The real cost isn’t the customization; it’s the ‘generic tax.’
Lost time due to Excel double-entry.
Upfront cost (which saves hours yearly).
Reframing the Resolution
There is a better way to frame the argument. In debate, we call it ‘reframing the resolution.’ Instead of asking, ‘How do we fit our business into this software?’ we should be asking, ‘Why is this software so ill-equipped to handle the reality of my industry?’
This is where specialized solutions like
enter the conversation. They don’t start with the assumption that you are selling lemonade. They start with the understanding that you are managing a supply chain that involves chemical reactions, varying material yields, and specific industry standards like dye lot tracking and hide grading.
🔄 Translation vs. Understanding
Technology could free him from that physical ledger he keeps in his back pocket, but only if the technology is smart enough to understand what he’s writing in it. If the software is dumb, Elias becomes the cog. He becomes the person serving the machine, translating the rich, textured world of leather into the flat, gray world of ‘Item ID: 109929.’
Lost Hours at the Altar of Standardization
Let’s look at the numbers. If a factory has 109 employees, and each of them loses 19 minutes a day fighting with a non-intuitive interface, that is over 39 hours of lost productivity every single day. Over a year, that is thousands of hours sacrificed at the altar of ‘standardization.’
Daily Loss Equivalency (109 Employees, 19 Mins/Day)
If you were to walk into your factory and see 9 people sitting on the floor doing nothing for the entire shift, you would be furious. Yet, when those 9 people are ‘working’ but actually just navigating a series of irrelevant menus and ‘notes’ fields, we call it ‘digital transformation.’ It’s a farce.
The End of Apologies
My mistake with the tourist was small. They probably found their way eventually, perhaps after an extra 29 minutes of walking. But the mistakes businesses make when choosing an ERP are often terminal. You cannot run a high-precision garment operation on a system that doesn’t understand seam allowances. You cannot run a world-class tannery on a system that thinks all inventory is static.
Seam Allowances
(Must be recognized)
Shrinkage/Cure
(Not static data)
Craft Legacy
(Deserves more than a notes field)
We need to stop apologizing for our complexity and start demanding that our tools actually reflect the work we do. Otherwise, we’re all just giving wrong directions and hoping nobody notices until they’ve already reached the wharf.