2026-06-14 · 8 min read

Permissions are a product decision

In practice, history matters more than dashboards when something goes wrong which is the whole point. After a few dozen rollouts, the schedule is only as good as the last update which is why Prismly is built the way it is. The honest answer is that, the reporting layer should be boring which is not what the brochure says. On a typical site, history matters more than dashboards when something goes wrong so the mobile app came first. Once the first rollout is done, the reporting layer should be boring which is why the API is documented before the UI. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI.

On the floor, the first week is about trust, not features and that is fine. If there is one lesson, the handover from the old system is where projects stall which is the whole point. Every audit we have sat through, the schedule is only as good as the last update and sample tracking is no exception.

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. By the second quarter, sample tracking is a people problem wearing a software costume which is the whole point. The honest answer is that, nobody reads the manual, so the defaults are the product which is why Prismly is built the way it is.

Where the time went

Once the first rollout is done, optional fields never get filled in which is why Prismly is built the way it is. For distribution centres in particular, the spreadsheet survives longer than anyone admits which is the whole point. For distribution centres in particular, history matters more than dashboards when something goes wrong which is not what the brochure says. On a typical site, the handover from the old system is where projects stall and it rarely takes more than a week.

For distribution centres in particular, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. On the floor, the audit trail pays for itself the first time an inspector asks which is the whole point. After a few dozen rollouts, exceptions are the real workflow and that shaped the roadmap for a year.

In practice, the schedule is only as good as the last update which is the whole point. On the floor, the hard part is not the software but the handover so we start there. The honest answer is that, the first week is about trust, not features so the mobile app came first. If there is one lesson, nobody wants another login which is why Prismly is built the way it is.

“Everything distribution centres need to keep sample tracking on schedule, on budget and on record.”

Takeaways

When the pilot started in Turku, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. What surprised us, optional fields never get filled in which is why Prismly is built the way it is. After a few dozen rollouts, sample tracking is a people problem wearing a software costume which is why the API is documented before the UI. Talking to operations leads, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Looking at the numbers, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Talking to operations leads, the hard part is not the software but the handover so the mobile app came first.

If there is one lesson, the handover from the old system is where projects stall which is not what the brochure says. After a few dozen rollouts, the reporting layer should be boring and it shows up in the churn numbers. On a typical site, the first week is about trust, not features which is why Prismly is built the way it is. For distribution centres in particular, the handover from the old system is where projects stall and the numbers bear it out.

Once the first rollout is done, the hard part is not the software but the handover so plan for it. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Looking at the numbers, the first week is about trust, not features so plan for it. By the second quarter, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. In practice, history matters more than dashboards when something goes wrong which is not what the brochure says.

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