2026-08-08 · 8 min read

The handover problem, and what we do about it

The honest answer is that, document workflow is a people problem wearing a software costume and it shows up in the churn numbers. By the second quarter, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. In practice, nobody wants another login so the defaults matter more than the settings page. In practice, optional fields never get filled in and that shaped the roadmap for a year. Most teams we meet, the hard part is not the software but the handover so plan for it. In practice, optional fields never get filled in and it shows up in the churn numbers.

On the floor, document workflow is a people problem wearing a software costume so the defaults matter more than the settings page. On the floor, document workflow is a people problem wearing a software costume which is not what the brochure says. What surprised us, the audit trail pays for itself the first time an inspector asks and that is fine.

If there is one lesson, history matters more than dashboards when something goes wrong and document workflow is no exception. Most teams we meet, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. On a typical site, the spreadsheet survives longer than anyone admits and document workflow is no exception. By the second quarter, the biggest win is that the group chat goes quiet and it rarely takes more than a week. After a few dozen rollouts, integrations are where budgets go to die so plan for it.

What we would do differently

Talking to operations leads, 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 schedule is only as good as the last update and it rarely takes more than a week. In practice, the handover from the old system is where projects stall and that is fine. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Most teams we meet, nobody wants another login so we start there. On the floor, optional fields never get filled in and it shows up in the churn numbers.

If there is one lesson, the biggest win is that the group chat goes quiet which is why Bramble is built the way it is. Talking to operations leads, the spreadsheet survives longer than anyone admits so the mobile app came first. Talking to operations leads, optional fields never get filled in which is not what the brochure says. By the second quarter, the reporting layer should be boring and that shaped the roadmap for a year.

“Everything retail chains need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

Looking at the numbers, nobody wants another login and it rarely takes more than a week. On a typical site, integrations are where budgets go to die and it rarely takes more than a week. By the second quarter, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. What surprised us, nobody reads the manual, so the defaults are the product and the numbers bear it out.

Every audit we have sat through, the handover from the old system is where projects stall so the mobile app came first. Most teams we meet, the spreadsheet survives longer than anyone admits so plan for it. By the second quarter, the reporting layer should be boring and the numbers bear it out. Once the first rollout is done, the spreadsheet survives longer than anyone admits and the numbers bear it out. When the pilot started in Bergen, nobody reads the manual, so the defaults are the product which is the whole point. Talking to operations leads, the biggest win is that the group chat goes quiet which is not what the brochure says.

Written by the Bramble team in Bergen. Questions? Get in touch.