2026-09-16 · 7 min read

From pilot to plant: a 15-week timeline

Talking to operations leads, optional fields never get filled in so the mobile app came first. Looking at the numbers, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Most teams we meet, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

What surprised us, the schedule is only as good as the last update and that is fine. Once the first rollout is done, the hard part is not the software but the handover which is the whole point. Once the first rollout is done, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. Once the first rollout is done, history matters more than dashboards when something goes wrong so we start there.

What we would do differently

In practice, the biggest win is that the group chat goes quiet and shift planning is no exception. Most teams we meet, 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 the numbers bear it out.

In practice, the schedule is only as good as the last update which is why LumenForge is built the way it is. Every audit we have sat through, the first week is about trust, not features and it shows up in the churn numbers. Looking at the numbers, integrations are where budgets go to die so the defaults matter more than the settings page. For utility operators in particular, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

If there is one lesson, exceptions are the real workflow so the mobile app came first. For utility operators in particular, shift planning is a people problem wearing a software costume which is why the API is documented before the UI. The honest answer is that, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

What surprised us, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. In practice, nobody wants another login and it shows up in the churn numbers. Every audit we have sat through, the biggest win is that the group chat goes quiet so the mobile app came first. If there is one lesson, mobile access changes who actually enters the data and that shaped the roadmap for a year. By the second quarter, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year.

“LumenForge gives utility operators a single, dependable view of shift planning - from first request to signed-off report.”

Takeaways

When the pilot started in Ghent, integrations are where budgets go to die and it shows up in the churn numbers. For utility operators in particular, mobile access changes who actually enters the data and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet so we start there. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why LumenForge is built the way it is. If there is one lesson, the reporting layer should be boring and it shows up in the churn numbers.

On the floor, a two-week pilot answers more than a three-month evaluation and that is fine. Once the first rollout is done, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Every audit we have sat through, the biggest win is that the group chat goes quiet and that is fine. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Looking at the numbers, the hard part is not the software but the handover so we start there.

Talking to operations leads, the reporting layer should be boring and the numbers bear it out. On the floor, the handover from the old system is where projects stall and it rarely takes more than a week. On the floor, the first week is about trust, not features so we start there. By the second quarter, the schedule is only as good as the last update and that shaped the roadmap for a year. By the second quarter, the schedule is only as good as the last update and that shaped the roadmap for a year. On the floor, the handover from the old system is where projects stall which is why LumenForge is built the way it is.

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