2026-08-12 · 4 min read

A boring reporting layer is a good reporting layer

The honest answer is that, nobody reads the manual, so the defaults are the product and that is fine. In practice, optional fields never get filled in which is why Orbithq is built the way it is. The honest answer is that, nobody wants another login and it shows up in the churn numbers. Once the first rollout is done, shift planning is a people problem wearing a software costume so plan for it. For distribution centres in particular, what matters is whether the crew opens it on a Monday morning which is why Orbithq is built the way it is. What surprised us, exceptions are the real workflow so the defaults matter more than the settings page.

On the floor, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. On a typical site, the first week is about trust, not features so the defaults matter more than the settings page. By the second quarter, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Talking to operations leads, the hard part is not the software but the handover so plan for it. After a few dozen rollouts, the spreadsheet survives longer than anyone admits and shift planning is no exception.

The honest answer is that, optional fields never get filled in which is why Orbithq is built the way it is. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is why Orbithq is built the way it is. The honest answer is that, integrations are where budgets go to die and shift planning is no exception. By the second quarter, mobile access changes who actually enters the data which is why the API is documented before the UI. On the floor, nobody reads the manual, so the defaults are the product which is why Orbithq is built the way it is.

What actually happened

Talking to operations leads, exceptions are the real workflow so the defaults matter more than the settings page. Every audit we have sat through, integrations are where budgets go to die and that shaped the roadmap for a year. Once the first rollout is done, shift planning is a people problem wearing a software costume which is not what the brochure says. For distribution centres in particular, history matters more than dashboards when something goes wrong and the numbers bear it out.

When the pilot started in Ghent, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Most teams we meet, the schedule is only as good as the last update which is the whole point. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and shift planning is no exception. After a few dozen rollouts, the hard part is not the software but the handover and that shaped the roadmap for a year. Most teams we meet, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. For distribution centres in particular, shift planning is a people problem wearing a software costume and that shaped the roadmap for a year.

“Replace the spreadsheet, the whiteboard and the group chat with one toolkit your team will actually open.”

Takeaways

By the second quarter, shift planning is a people problem wearing a software costume so we start there. What surprised us, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. Talking to operations leads, the schedule is only as good as the last update and it shows up in the churn numbers. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. In practice, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

On the floor, the first week is about trust, not features which is why Orbithq is built the way it is. On a typical site, nobody wants another login and it rarely takes more than a week. In practice, the handover from the old system is where projects stall which is the whole point. The honest answer is that, optional fields never get filled in which is the whole point. In practice, the reporting layer should be boring which is not what the brochure says. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

Written by the Orbithq team in Ghent. Questions? Get in touch.