Avoiding the technology ‘Pilot Paradox’

It was many years ago I first heard this business mantra: think big, start small and scale fast.

I thought it was a wonderful concept, and it has driven my thought process in many technology implementations. Over time, however, I realized that there were too many projects that stalled somewhere between the start small and scale fast phases.

Technology projects play a crucial role in driving organizational growth and innovation, but moving these projects from the pilot stage to full-scale application can be a major challenge. This is not just a minor hiccup in corporate technology deployment. It represents a critical barrier to progress and efficient resource utilization. In this article I explore why many of these undertakings do not make it past the pilot stage and, even if they do, why they often struggle to scale effectively across an organization.

In a recent article, McKinsey states that innovators dominate headlines, but scalers dominate markets. In other words, successful CEOs are as passionate about scale as they are about strategy. According to the article, 40% of digital and AI transformations stall out at the scaling phase, and that was from a 2019 study. We can safely assume the percentage has climbed since.

The problem with pilots

Pilot projects are typically the first step in implementing new technology within an organization. They serve as a testing ground, offering a controlled environment to evaluate the potential of a new system. The pilot paradox lies in the fact that while pilots are designed to be the first step toward a solution, they often end up being the final stage for many projects, sometimes even when the pilot has been successful.

One of the primary reasons pilots fail to progress is their limited scope. Pilots are usually conducted in a regulated setting with a small user group, which may not accurately represent the organization overall. This limitation can result in a failure to identify key challenges that become apparent only when the technology is deployed at a larger scale.

Another critical factor is misalignment with broader business objectives. Sometimes technology projects are initiated because of their novelty or the vague promise of efficiency without a clear understanding of how they align with strategic goals. If the pilot does not demonstrate clear value in line with those objectives, decision makers may be reluctant to invest further.

The scaling challenge

Integration complexities. Integrating new technology into existing systems can be daunting, and the larger the organization, the more challenging it becomes. In some cases the integration needs for the pilot were met with temporary workarounds. Solutions that worked flawlessly in a pilot environment may encounter unforeseen issues when interfaced with legacy systems or used in different operational contexts.

Resource and budget constraints. Scaling often requires significant investment in both human and financial capital. Organizations may find it challenging to allocate the necessary resources, especially if the pilot did not unequivocally prove the anticipated benefits. Budgets for pilots may also originate from different pots of money and approval processes than the funding for full implementation.

Change management and user adoption. The human element cannot be underestimated. Resistance to change, lack of training and poor user adoption are significant hurdles. What worked in a small group during the pilot can falter when applied across a larger and more diverse workforce. This is especially likely when the pilot participants were chosen for being enthusiastic early adopters.

Solutions and best practices

Align with business goals. Projects, especially pilots, must be closely aligned with strategic objectives from the outset. In the case of the oncoming AI avalanche, management may feel pressured to show they are using this new technology and undertake a project with high visibility but low overall impact, veering away from actual business goals.

Plan comprehensively. A plan will include budget, resources and timelines. Two often overlooked areas are the detailed post-pilot scaling plan and the list of necessary collaborative activities with your solution providers. The first is often deferred to a second planning session once the pilot is complete, and that session does not always happen.

Manage change effectively. Proactively managing the human aspect of technology implementation is vital. In many companies this cost is the first to be cut when fitting a project into budget. In the McKinsey book Rewired, they suggest a rule of thumb: for every dollar spent on the technology itself, spend a dollar on the user adoption and change management necessary to make it work.

Choose a scaling strategy. Rather than attempting full-scale implementation at once, an incremental approach can be more effective, defined by geography, business unit or function. Alternatively, a Harvard Business Review article suggests a different approach: rather than requiring new teams to replicate the pilot exactly, share what you learned and challenge them to find their own solutions that could work as well as or better than the original.

Evaluate and adapt continuously. Ongoing evaluation and a willingness to adapt based on real-world experience are essential. Make sure project meetings extend well beyond the go-live date, with the executive sponsor included, and retain the ability to make changes as needed.

The key point

The journey from pilot to full-scale implementation is difficult, but strategic alignment, careful planning, effective change management and a flexible incremental approach all improve the odds. The key is recognizing that scaling a technology project is not just a technical challenge. It is a strategic and human one.