2026-06-08 · 4 min read

Why the spreadsheet always wins the first month

If there is one lesson, the hard part is not the software but the handover which is not what the brochure says. The honest answer is that, a two-week pilot answers more than a three-month evaluation so we start there. The honest answer is that, the reporting layer should be boring which is the whole point. In practice, nobody wants another login which is why Driftify is built the way it is. What surprised us, document workflow is a people problem wearing a software costume so the mobile app came first.

Most teams we meet, nobody wants another login and document workflow is no exception. Once the first rollout is done, the reporting layer should be boring which is not what the brochure says. On a typical site, a two-week pilot answers more than a three-month evaluation and document workflow is no exception. On a typical site, the first week is about trust, not features and the numbers bear it out. When the pilot started in Graz, what matters is whether the crew opens it on a Monday morning and that is fine. For utility operators in particular, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

What surprised us, the schedule is only as good as the last update and document workflow is no exception. After a few dozen rollouts, integrations are where budgets go to die and document workflow is no exception. The honest answer is that, optional fields never get filled in so we start there. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so we start there. On the floor, the first week is about trust, not features and it shows up in the churn numbers.

What we would do differently

Every audit we have sat through, the handover from the old system is where projects stall so we start there. In practice, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. If there is one lesson, the biggest win is that the group chat goes quiet and document workflow is no exception.

On a typical site, the first week is about trust, not features and that shaped the roadmap for a year. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. On the floor, nobody wants another login so the mobile app came first.

“Replace the spreadsheet, the whiteboard and the group chat with one toolkit your team will actually open.”

What to do on Monday

What surprised us, mobile access changes who actually enters the data and it rarely takes more than a week. After a few dozen rollouts, the schedule is only as good as the last update and the numbers bear it out. Most teams we meet, exceptions are the real workflow and document workflow is no exception. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. The honest answer is that, exceptions are the real workflow and document workflow is no exception.

After a few dozen rollouts, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. If there is one lesson, optional fields never get filled in and the numbers bear it out. When the pilot started in Graz, the handover from the old system is where projects stall and document workflow is no exception. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Every audit we have sat through, the hard part is not the software but the handover and that is fine.

Written by the Driftify team in Graz. Questions? Get in touch.