/ in short
Most manufacturers can make a digital pilot work. Far fewer can make it work everywhere. This paper is for operations, finance and transformation leaders who are tired of promising pilots that never leave the test site. It explains why pilots stall, then sets out how to build a factory playbook that turns one win into a repeatable system, codifying the technical set-up, the operating routines and the human factors. It shows how to build a business case with finance from day one, how to change behaviour rather than just tools, and how mid-sized firms can borrow the habits of the World Economic Forum’s Lighthouse factories without their budgets. Each chapter ends with practical tips you can use on Monday morning, written for businesses where capacity is tight, teams are stretched and outcomes matter.
Key takeaways
- Treat pilots as starting blocks, not finish lines, and design them to scale from day one.
- Write a factory playbook in three layers: technical set-up, operating routines and human factors.
- Bring finance in early and show impact at 6, 12 and 24 months.
- Culture is the operating system: make wins visible on the shop floor.
- You do not need to be a Lighthouse to behave like one.
/ what’s inside
- Why pilots stall and playbooks matter
- Shift from isolated pilots to intentional scaling
- Culture is the operating system
- Build your factory playbook
- Speak the CFO’s language
- Change behaviour, not just tools
- Operate like a Lighthouse, at your own scale
Pilot purgatory: Pilot purgatory is a cycle where digital tools prove useful in isolation but fail to gain traction across the network, so pilots generate insight but little enduring value.
Questions this paper answers
Pilots are often designed to prove a point, not to power a business system. They rely on local champions and one-off fixes, there is no roadmap beyond the test site, ROI is unclear and functional silos block ownership.
A living record of what made a pilot work, in three layers: the technical set-up (data, alerts, logic), the operating routines (roles, timing, troubleshooting) and the human factors (stories, wins, lessons), updated quarterly.
Build it with finance from the start, convert technical wins into money, show impact at 6, 12 and 24 months, and tie the case to board-level themes such as energy volatility, margin pressure and ESG.
Yes. Lighthouses started with clarity, capability and repeatability rather than advanced AI. Start with one repeatable problem across sites, codify wins in playbooks, set up light governance and tell the story every time something works.