2026-09-27 · 9 min read

What we learned rolling out document workflow at 36 sites

If there is one lesson, optional fields never get filled in so the mobile app came first. In practice, the reporting layer should be boring which is why Basalt is built the way it is. Once the first rollout is done, the handover from the old system is where projects stall which is the whole point. For food producers in particular, exceptions are the real workflow and that is fine. In practice, the handover from the old system is where projects stall and it shows up in the churn numbers.

After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is not what the brochure says. Most teams we meet, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. If there is one lesson, document workflow is a people problem wearing a software costume and that is fine. After a few dozen rollouts, the handover from the old system is where projects stall so we start there. In practice, what matters is whether the crew opens it on a Monday morning which is the whole point. What surprised us, the biggest win is that the group chat goes quiet which is not what the brochure says.

Looking at the numbers, nobody reads the manual, so the defaults are the product so we start there. On the floor, the hard part is not the software but the handover and it shows up in the churn numbers. For food producers in particular, the audit trail pays for itself the first time an inspector asks and that is fine.

The part nobody plans for

For food producers in particular, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. On a typical site, exceptions are the real workflow and that shaped the roadmap for a year. On the floor, mobile access changes who actually enters the data which is not what the brochure says. After a few dozen rollouts, history matters more than dashboards when something goes wrong which is why Basalt is built the way it is. What surprised us, the hard part is not the software but the handover which is why the API is documented before the UI. In practice, the first week is about trust, not features so we start there.

Talking to operations leads, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. On the floor, the hard part is not the software but the handover and that shaped the roadmap for a year. The honest answer is that, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. On the floor, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. By the second quarter, optional fields never get filled in so the mobile app came first.

By the second quarter, the biggest win is that the group chat goes quiet and the numbers bear it out. Talking to operations leads, nobody wants another login and that is fine. Talking to operations leads, integrations are where budgets go to die which is the whole point. When the pilot started in Turku, the spreadsheet survives longer than anyone admits which is the whole point. What surprised us, the reporting layer should be boring and the numbers bear it out.

“Everything food producers need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

If there is one lesson, history matters more than dashboards when something goes wrong and the numbers bear it out. Most teams we meet, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. Most teams we meet, exceptions are the real workflow and it rarely takes more than a week. If there is one lesson, document workflow is a people problem wearing a software costume so the defaults matter more than the settings page. Looking at the numbers, document workflow is a people problem wearing a software costume which is why Basalt is built the way it is. What surprised us, the spreadsheet survives longer than anyone admits and that is fine.

On the floor, the reporting layer should be boring and that shaped the roadmap for a year. Looking at the numbers, mobile access changes who actually enters the data and that is fine. After a few dozen rollouts, the biggest win is that the group chat goes quiet so the mobile app came first. Looking at the numbers, optional fields never get filled in and it rarely takes more than a week. What surprised us, the schedule is only as good as the last update which is why the API is documented before the UI. Talking to operations leads, the schedule is only as good as the last update so plan for it.

For food producers in particular, exceptions are the real workflow so we start there. Looking at the numbers, the first week is about trust, not features and that shaped the roadmap for a year. What surprised us, mobile access changes who actually enters the data which is not what the brochure says. Talking to operations leads, mobile access changes who actually enters the data and that shaped the roadmap for a year. After a few dozen rollouts, the reporting layer should be boring and that is fine.

Written by the Basalt team in Turku. Questions? Get in touch.