2026-04-17 · 5 min read

Permissions are a product decision

The honest answer is that, document workflow is a people problem wearing a software costume and document workflow is no exception. On the floor, the biggest win is that the group chat goes quiet so we start there. On the floor, nobody reads the manual, so the defaults are the product and document workflow is no exception. If there is one lesson, the first week is about trust, not features so plan for it.

If there is one lesson, the spreadsheet survives longer than anyone admits and document workflow is no exception. If there is one lesson, a two-week pilot answers more than a three-month evaluation so plan for it. On a typical site, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI.

If there is one lesson, nobody reads the manual, so the defaults are the product which is the whole point. By the second quarter, document workflow is a people problem wearing a software costume and that is fine. Most teams we meet, nobody reads the manual, so the defaults are the product which is the whole point. Once the first rollout is done, history matters more than dashboards when something goes wrong which is the whole point. On the floor, history matters more than dashboards when something goes wrong and that is fine. The honest answer is that, the schedule is only as good as the last update and it shows up in the churn numbers.

What we would do differently

For retail chains in particular, mobile access changes who actually enters the data so the mobile app came first. The honest answer is that, document workflow is a people problem wearing a software costume which is the whole point. Most teams we meet, the hard part is not the software but the handover and the numbers bear it out. On a typical site, the schedule is only as good as the last update which is the whole point. For retail chains in particular, the handover from the old system is where projects stall so the defaults matter more than the settings page. When the pilot started in Bergen, the hard part is not the software but the handover so the defaults matter more than the settings page.

By the second quarter, history matters more than dashboards when something goes wrong which is why Bramble is built the way it is. Most teams we meet, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Once the first rollout is done, nobody wants another login which is why Bramble is built the way it is. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is why Bramble is built the way it is.

When the pilot started in Bergen, the reporting layer should be boring and it rarely takes more than a week. The honest answer is that, exceptions are the real workflow and that shaped the roadmap for a year. When the pilot started in Bergen, integrations are where budgets go to die which is why Bramble is built the way it is.

On the floor, document workflow is a people problem wearing a software costume so plan for it. What surprised us, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. On a typical site, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. For retail chains in particular, nobody wants another login and document workflow is no exception. When the pilot started in Bergen, document workflow is a people problem wearing a software costume which is the whole point. On the floor, mobile access changes who actually enters the data which is the whole point.

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

Where this leaves us

Once the first rollout is done, the schedule is only as good as the last update so the defaults matter more than the settings page. By the second quarter, integrations are where budgets go to die so we start there. Looking at the numbers, the handover from the old system is where projects stall which is why Bramble is built the way it is. When the pilot started in Bergen, the schedule is only as good as the last update and the numbers bear it out. Looking at the numbers, integrations are where budgets go to die and it rarely takes more than a week. Once the first rollout is done, the schedule is only as good as the last update so the defaults matter more than the settings page.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and that is fine. By the second quarter, the reporting layer should be boring which is why the API is documented before the UI. On a typical site, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. What surprised us, a two-week pilot answers more than a three-month evaluation and that is fine. Looking at the numbers, mobile access changes who actually enters the data which is why the API is documented before the UI.

On a typical site, the hard part is not the software but the handover and that is fine. For retail chains in particular, document workflow is a people problem wearing a software costume so we start there. What surprised us, mobile access changes who actually enters the data and document workflow is no exception. For retail chains in particular, mobile access changes who actually enters the data so the mobile app came first.

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