A construction firm came to us frustrated. For months they had been trying to get their field workers to submit daily status reports. They had tried everything — gift certificates for the workers with the best submission records, bonus deductions for anyone falling below eighty percent. Nothing worked.

We had a different question. Before talking about solutions, we asked them to walk us through why they wanted the reports in the first place. The answer turned out to be three things — none of them "compliance." They needed to keep clients informed. They needed to know what materials were required the next day. They needed to know when equipment was free on one site so another crew could use it.

The reports that did come in weren't being read. They sat until a client asked about progress. Nothing flagged a problem or routed critical information to the person who needed to act on it. The loop between field and office was broken at both ends.

Before we touched the format, we worked through every question on the report: why is this here, and what does someone do with the answer? Questions that couldn't be justified were removed. The ones that remained were ranked by importance.

We redesigned the report around its actual purpose. Most questions became single-tap responses. The materials question got its own prominent field — and crew leads could flag a need the moment they noticed it, not just at end of day. We added an equipment inventory and the ability to attach photos. Behind the scenes, the system now routes anything that deviates from expected directly to the person who needs to act on it.

We also sat with the crew leads and explained what the reports were for. Not as a mandate. As a conversation. When people understand why something matters, the relationship to the task changes.

The reports didn't change because we built a better system. They changed because we asked what the system was actually supposed to do — and then made sure the answer ran all the way through it.