Field note: the foreman who refused the tablet.

title: "Field note: the foreman who refused the tablet." dek: "Construction-tech adoption friction is almost never resistance to change. It's a tool that destroyed a working trust ritual nobody on the vendor side noticed." date: "2026-03-18" pillar: "field-notes" author: "floburn" tags: ["construction", "field-notes", "adoption", "attestation"]

The foreman has been doing the end-of-day walk for 19 years. Each crew chief comes by his truck around 4:30, they go through hours, breaks, what got finished, what got pushed to tomorrow. He writes it down on a yellow notepad. The notepad goes into a manila folder. The folder rides shotgun back to the yard. The office manager photographs the pages on Monday morning.

We were the third vendor in 18 months trying to put a tablet between him and the notepad. The first two were timekeeping software. We were attestation. The pitch was identical: he taps the tablet at end of day, the crew chiefs sign off, the data flows into payroll, the firm has a defensible audit trail under §2699. Faster, cleaner, less paper.

He listened, asked one question, and walked away.

The question was: Where does the data go? The honest answer was that it went into the cloud, into a database under the firm's tenant, available to the office manager and the project executive but not to him. He didn't say what bothered him about that. He didn't need to. The notepad sat in his folder, in his truck, in his sight, all week. The tablet's data was somewhere he couldn't see.

The owner asked us to get the foreman over the hump. That phrase was the problem.

We did the math on the actual workflow first. The vendor demo claimed 30 seconds per crew member. We measured nine minutes per crew on a real Tuesday: the foreman walking around to confirm each chief had signed in, two re-syncs because of low signal at the site, a five-minute redirect to handle a crew that had a missing break punch. Across a year that's around seven hours per crew, per foreman. The foreman wasn't refusing the tablet on principle. He was refusing the part of the workflow the vendor didn't include in the demo.

We rebuilt it from his side. The end-of-day conversation stayed. The notepad stayed. Crew chiefs now sign off in the same five-minute conversation they were already having, on his phone, via a single SMS link that opens, captures the attestation, and closes. He sees what got signed before it leaves the truck. The data goes to the office. So does a copy to his phone. He can show a chief what they confirmed, the next morning, without unlocking anything or logging in.

Three months later, the system runs. The audit trail satisfies counsel. The office manager stopped photographing notepad pages. The foreman still does the walk.

The thing we learned: when a foreman refuses a tablet, the right interpretation is almost never resistant to change. The right interpretation is the tool destroyed a working trust ritual and you didn't notice. The compliance gain in the tablet was real. The trust loss in the workflow was bigger. If you can keep the ritual and add the record, both go up. If you replace the ritual with the record, both go down.

The shorter version: the foreman is the most reliable source of friction information you have. When he says no, the question is what he is telling you, not how to overcome him.