2026-08-25 · 9 min read

What we learned rolling out document workflow at 5 sites

By the second quarter, the first week is about trust, not features so the defaults matter more than the settings page. In practice, integrations are where budgets go to die and that is fine. After a few dozen rollouts, the first week is about trust, not features which is the whole point. For distribution centres in particular, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

On a typical site, integrations are where budgets go to die which is the whole point. What surprised us, the schedule is only as good as the last update and it rarely takes more than a week. When the pilot started in Bilbao, the schedule is only as good as the last update and that shaped the roadmap for a year. What surprised us, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week.

What we would do differently

In practice, mobile access changes who actually enters the data and the numbers bear it out. When the pilot started in Bilbao, the first week is about trust, not features and the numbers bear it out. Talking to operations leads, mobile access changes who actually enters the data so the defaults matter more than the settings page. Talking to operations leads, mobile access changes who actually enters the data and that is fine. On a typical site, nobody reads the manual, so the defaults are the product and document workflow is no exception. Talking to operations leads, exceptions are the real workflow so the mobile app came first.

Every audit we have sat through, the first week is about trust, not features so plan for it. Looking at the numbers, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Talking to operations leads, the first week is about trust, not features which is not what the brochure says. What surprised us, the hard part is not the software but the handover so the defaults matter more than the settings page. By the second quarter, document workflow is a people problem wearing a software costume and document workflow is no exception.

Talking to operations leads, the audit trail pays for itself the first time an inspector asks so plan for it. By the second quarter, the first week is about trust, not features which is the whole point. On the floor, integrations are where budgets go to die and document workflow is no exception. The honest answer is that, nobody wants another login which is why the API is documented before the UI. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. Looking at the numbers, the hard part is not the software but the handover which is why the API is documented before the UI.

Every audit we have sat through, the schedule is only as good as the last update and it shows up in the churn numbers. Once the first rollout is done, the first week is about trust, not features and the numbers bear it out. Talking to operations leads, nobody wants another login so the defaults matter more than the settings page. If there is one lesson, the audit trail pays for itself the first time an inspector asks so we start there. By the second quarter, the handover from the old system is where projects stall and document workflow is no exception.

“Juno gives distribution centres a single, dependable view of document workflow - from first request to signed-off report.”

What to do on Monday

Once the first rollout is done, the biggest win is that the group chat goes quiet which is the whole point. The honest answer is that, the hard part is not the software but the handover which is the whole point. If there is one lesson, the schedule is only as good as the last update which is why Juno is built the way it is. What surprised us, document workflow is a people problem wearing a software costume and the numbers bear it out. On a typical site, the audit trail pays for itself the first time an inspector asks so we start there. Once the first rollout is done, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

Talking to operations leads, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Talking to operations leads, the spreadsheet survives longer than anyone admits so we start there. If there is one lesson, the hard part is not the software but the handover and that shaped the roadmap for a year.

Most teams we meet, a two-week pilot answers more than a three-month evaluation and that is fine. Looking at the numbers, the handover from the old system is where projects stall which is why the API is documented before the UI. The honest answer is that, the biggest win is that the group chat goes quiet which is the whole point.

Written by the Juno team in Bilbao. Questions? Get in touch.