2026-07-19 · 6 min read

From pilot to plant: a 37-week timeline

In practice, the hard part is not the software but the handover so plan for it. After a few dozen rollouts, exceptions are the real workflow and that shaped the roadmap for a year. Once the first rollout is done, optional fields never get filled in and that shaped the roadmap for a year. Once the first rollout is done, shift planning is a people problem wearing a software costume so plan for it.

Looking at the numbers, optional fields never get filled in and that is fine. In practice, the spreadsheet survives longer than anyone admits so the mobile app came first. On a typical site, the first week is about trust, not features and that shaped the roadmap for a year. In practice, the first week is about trust, not features which is not what the brochure says. In practice, the biggest win is that the group chat goes quiet and shift planning is no exception.

What actually happened

Every audit we have sat through, shift planning is a people problem wearing a software costume so plan for it. Most teams we meet, optional fields never get filled in and that shaped the roadmap for a year. If there is one lesson, what matters is whether the crew opens it on a Monday morning so the mobile app came first. After a few dozen rollouts, the reporting layer should be boring and it rarely takes more than a week. What surprised us, shift planning is a people problem wearing a software costume and the numbers bear it out.

If there is one lesson, the handover from the old system is where projects stall and that is fine. On the floor, exceptions are the real workflow and shift planning is no exception. When the pilot started in Malmo, exceptions are the real workflow which is why PivotDesk is built the way it is.

When the pilot started in Malmo, the biggest win is that the group chat goes quiet which is not what the brochure says. When the pilot started in Malmo, the handover from the old system is where projects stall and that shaped the roadmap for a year. When the pilot started in Malmo, nobody wants another login which is why PivotDesk is built the way it is.

After a few dozen rollouts, shift planning is a people problem wearing a software costume which is the whole point. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. After a few dozen rollouts, the schedule is only as good as the last update so we start there.

“Plan, dispatch and reconcile in one place. PivotDesk connects to the systems you already run and stays out of the way.”

What to do on Monday

Every audit we have sat through, nobody reads the manual, so the defaults are the product and the numbers bear it out. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Looking at the numbers, mobile access changes who actually enters the data and shift planning is no exception.

By the second quarter, integrations are where budgets go to die which is the whole point. The honest answer is that, the handover from the old system is where projects stall and shift planning is no exception. Talking to operations leads, exceptions are the real workflow so the mobile app came first. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Every audit we have sat through, shift planning is a people problem wearing a software costume and that is fine. When the pilot started in Malmo, shift planning is a people problem wearing a software costume and it shows up in the churn numbers.

By the second quarter, the handover from the old system is where projects stall so the mobile app came first. Once the first rollout is done, exceptions are the real workflow so the defaults matter more than the settings page. Most teams we meet, mobile access changes who actually enters the data which is not what the brochure says. On a typical site, history matters more than dashboards when something goes wrong which is why PivotDesk is built the way it is. If there is one lesson, nobody wants another login and that is fine.

Written by the PivotDesk team in Malmo. Questions? Get in touch.