Field notes
Why your crew went back to spreadsheets, and how to make it stick this time
You bought the system. The crew used it for two weeks, drifted back to spreadsheets and group texts, and you cleaned up the mess. That is the failure nobody talks about, and it is almost never the crew's fault.
By Gil Ramirez
Every contractor we work with has tried a new system before. Most have a graveyard of them. The tool was fine. The rollout is where it died. Building the system is the easy part. Getting a crew that ran on paper to actually use something new is the work, and it is the part almost everyone skips.
The two reasons it did not stick
It did not fit how the work actually happens. Off-the-shelf software is built for the average of a thousand companies. It asks your crew to change how they work to match the tool. On a jobsite, in the weather, behind schedule, that friction is all it takes. The crew does the fastest thing that works, and the fastest thing is the spreadsheet they already know.
Nobody was there after go-live. The vendor sold it, did a training call, and disappeared. When the first real confusion hit, there was no one to fix it, so the crew went back to what worked.
What actually makes it stick
Build around the work, not against it. When the system fits the way your crews already operate, adoption stops being a fight. The field app captures what they were already doing, not extra steps invented by a product manager who has never been on a jobsite.
Stay in it for 90 days. Adoption does not happen at go-live. It happens over the next three months, as real jobs run through the system and the rough edges get found and fixed. That is why we do not consider a build done at launch. We stay in it for 90 days, because that is when a crew that ran on paper actually starts trusting something new.
Make the right way the easy way. If the system is more work than the workaround, the workaround wins every time. The job of the build is to make the documented, billable, trackable path also the path of least resistance.
The order matters
This is also why we diagnose before we prescribe. A two-week Operations Audit tells us how your crews actually work before anyone builds anything, so what gets built fits the operation instead of fighting it. That is the difference between a system that sticks and another one for the graveyard.