Nobody at a Scrap Yard Wants Your Software. Here Is How It Actually Gets Adopted

My grandfather started our yard with a beam scale and a cigar box. My father added a printing scale and a filing cabinet. I added a computer, and I will tell you exactly how that went: the computer sat unused in the office for fourteen months while everyone kept using the carbon pads.

I have since helped two regional chains roll out software across a combined nineteen yards. I have watched good products fail and mediocre products stick. The difference was never the product. Let me save you the fourteen months.

Why software dies at yards

It is almost never features. It is these, in order:

• It made the scale slower on day one. Even if it is faster by week three, you do not survive day one if there is a line of trucks and a frustrated Earl.
• It was introduced as a control tool. The moment the crew thinks the software exists to watch them, it becomes the enemy. Adoption becomes quiet resistance.
• Nobody owned it. "The software will handle it" is how nothing gets handled. Software does not have hands.

Here is the adoption curve I have seen over and over, and the one most rollouts actually get:

Yard A looks fine for a week because people comply when watched. Then the manager looks away and the carbon pads come back out of the drawer. By week six there is a beautiful dashboard showing almost nothing, because the real work is happening on paper and getting back-entered (badly) on Fridays.

Yard B started slower on purpose. We did not roll out "the system." We rolled out one thing: the scale ticket, and only after it was provably faster than Earl's pad with a stopwatch to prove it.

The rollout that actually works

Compressed into the order that matters:

• Week 0: Pick the champion. Not the most senior person, the most respected one at the scale. Often that is Earl. Train only them.
• Week 1: One feature. The scale ticket. Run it in parallel with paper. Race it. Let the crew watch the champion win.
• Week 2-3: Drop the paper for inbound only. Champion supports the crew, not management. Fix the three friction points that show up (there are always exactly about three).
• Week 4+: Now add inventory, then reporting. Now the dashboard means something because the data underneath it is real.

Notice reporting comes last. Every failed rollout I have seen led with reporting because that is what the person who bought the software wants to see. The crew has to make the data real before the report is anything but a pretty lie.

What I tell every owner now

Your software project is not a technology project. It is a project about one respected person at the scale being made visibly faster and then being trusted to bring everyone else along. Get that right and almost any competent product works. Get it wrong and the best product on the market ends up in the same drawer as my fourteen-month computer.

The carbon pad is not your competition. Inertia wearing a person's face is. His name might be Earl. Go win Earl.