New Technology Adoption: Avoiding Pilot Purgatory and Moving Beyond the PoC towards Proof of Value

Fujitsu / March 13, 2025

Pioneering organizations understand the importance of new technology and innovation to contribute to a more sustainable and equitable future, while at the same time enhancing their own efficiency and competitiveness to survive in today’s challenging environment. It is but all too common to see technology initiatives of many enterprises towards Digital Transformation (DX) and Sustainability Transformation (SX) get stuck in a perpetual cycle of pilots without being able to move forward.

In an earlier blog (linked below), we wrote about how organizations looking to adopt cutting-edge technologies such as AI, blockchain, and quantum computing can transform operations and generate value. In this follow-up blog, we continue with more practical advice on how to avoid what’s commonly called ‘pilot purgatory’, and how to move purposefully towards value.

Proof of Concept to Proof of Value: More than semantics
Keep the Business Case at the Core
Define and Track Success Metrics Consistently
Keep Stakeholders Engaged and Accountable
Address Organisational and Personnel Change Factors
Prevent ‘Zombie Pilots’ – Decide to Scale or Kill Early
Secure Budget and Operational Readiness for Scaling
Foster a Culture of Trust and Team Cohesion (Patrick Lencioni’s Five Dysfunctions of a Team)
Define the Post-Pilot Roadmap
Conclusion

Proof of Concept to Proof of Value: More than semantics

In innovation and transformation pilot projects, we need to shift the terminology from Proof of Concept (PoC) to Proof of Value (PoV) and this is more than just semantics - it fundamentally reframes how organisations interpret and engage with pilots.

A PoC focuses on feasibility, answering the question: Can this technology or solution work? While useful in technical validation, it often lacks the strategic context and pull needed to drive enterprise-wide adoption. In contrast, PoV shifts the focus to measurable business impact, asking: Does this create tangible business value, and is it worth scaling?

This subtle but critical change in language influences behaviour - stakeholders approach the initiative with an outcomes-driven mindset rather than treating it as an isolated experiment. When teams anchor discussions around PoV, it inherently demands cross-functional alignment, ongoing validation against business goals, and a clear decision-making framework beyond technical success. It fundamentally addresses the question: is this solution a ‘nice to have’ or ‘need to have.’ Investments should only be aligned to the latter.

By emphasising value realisation over conceptual feasibility, organisations can avoid the trap of perpetual pilots and instead foster a culture where innovation is purpose-driven, accountable, and geared toward scalable impact.

Keep the Business Case at the Core

• Continuous Validation: Once the business case has been agreed, regularly revisit it throughout the lifecycle of the project, to ensure it still solves the intended problem and aligns with the company’s/department’s strategic goals.

• Avoid Scope Creep: Any deviations from the original problem statement must be justified, and adjustments should be made deliberately - not through uncontrolled expansion. Rabbit holes are inevitable. Discussions that stray from the intended agenda and goal can be valuable, insightful, and even essential. However, when they occur without deliberate focus, they risk diverting attention from the original objective, causing the project to lose direction. Make sure the project leader or the team can quickly end such a deviation and steer the project back on track quickly.

• Business & IT Alignment: Maintain open communication between innovation, business, and IT teams to avoid misalignment in execution.

Define and Track Success Metrics Consistently

• Establish Clear KPIs: Metrics should remain relevant throughout the PoV and beyond. They must be both qualitative (e.g., user adoption, satisfaction) and quantitative (e.g., ROI, efficiency improvements).

• Reassess Measurement Criteria: If external conditions change (e.g., market trends, regulation shifts), validate whether the defined success metrics are still relevant.

• Ensure Continuous Data Collection: Avoid running a pilot in isolation; embed analytics and feedback loops to track performance in real time - a DevOps CI/CD model.

Loading component...

Keep Stakeholders Engaged and Accountable

• Senior Sponsorship Commitment: Leadership must remain engaged beyond the initial excitement phase. Without continued executive buy-in, projects tend to stall and fail.

• Cross-Functional Alignment: Regular check-ins with business, IT, finance, and operations ensure no team loses sight of its role in scaling the PoV.

• Transparency with External Partners: Ensure vendors, consultants, and other partners involved in the PoV know the long-term vision to avoid disjointed efforts.

Loading component...

Address Organisational and Personnel Change Factors

• Mitigate Leadership Turnover Risks: A key project sponsor leaving or shifting priorities can derail momentum. Build broad-based support across multiple stakeholders.

• Adapt to Changing Priorities: If business conditions shift, assess whether the PoV still holds value and, if necessary, reposition it rather than letting it fade away.

Loading component...

Prevent ‘Zombie Pilots’ – Decide to Scale or Kill Early

• Fail Fast, Learn Fast: Not all PoVs should scale. If results don’t justify further investment, wrap up efficiently and pivot resources elsewhere.

• Clear Go/No-Go Criteria: Establish firm decision points (e.g., cost-benefit analysis, scalability assessment) to determine whether to proceed.

• Avoid Perpetual Experimentation: A PoV should not linger indefinitely without clear direction. If it proves value, move decisively toward implementation.

Loading component...

Secure Budget and Operational Readiness for Scaling

• Allocate Resources in Advance: If a PoV is successful, there should already be a path to secure funding for scaling it.

• Plan for Integration and Change Management: Ensure the organisation is ready for implementation - including necessary process changes, workforce training, and infrastructure upgrades.

• Break Down Functional Silos: Large-scale adoption often requires collaboration between different departments; alignment must happen early to avoid friction later or unforeseen obstacles.

Loading component...

Foster a Culture of Trust and Team Cohesion

• Encourage Open and Honest Communication: Build trust within teams by fostering a safe space to talk, where concerns and risks can be openly discussed.

• Address Team Dysfunction Early: Dysfunctional team dynamics (e.g., lack of commitment, avoidance of accountability) can derail execution.

• Promote Shared Ownership: Everyone involved in the PoV should see it as a collective effort, rather than an initiative owned by a single department.

Patrick Lencioni’s Five Dysfunctions of a Team is a good reference in this context to build cohesive virtual teams with a culture of trust.

Loading component...

Define the Post-Pilot Roadmap

• Develop a Scaling Plan Before the PoV Ends: Ensure that, if successful, there is a clear roadmap with assigned responsibilities for full-scale implementation.

• Secure Executive Buy-In for the Next Phase: Leadership should be prepared to champion the transition from pilot to operational deployment.

• Communicate Results and Next Steps Clearly: Transparency in outcomes and next steps prevent PoVs from being forgotten or losing momentum.

Loading component...

Conclusion

In conclusion, avoiding pilot purgatory requires a strategic shift from mere feasibility to demonstrable value. By focusing on clear business objectives, engaging stakeholders, and preparing for scalable implementation, organizations can ensure their digital transformation efforts are impactful and sustainable.

Move beyond pilot purgatory with Fujitsu Digital Shifts, which includes cutting-edge solutions in Data & AI, Blockchain, and Computer Vision to solve planet-wide challenges such as Supply Chain resilience and achieving ESG goals. Elevate your innovation strategy and turn potential into performance today. Get started with the links below or reach out to us.

Loading component...

Dominik Ferrara

Dominik is a Sustainability Transformation Solution Consultant at Fujitsu with a proven track record in driving sustainability initiatives and implementing transformation strategies. Experienced in building Low Carbon Energy certification schemes and environmental impact data platforms, as well as skilled in business development, sales, and strategic partnerships, he focuses his passion on delivering sustainable solutions to customers to drive positive environmental change. He is also adept at developing go-to-market strategies, committed to promoting sustainability and making a difference in the world.

New Technology Adoption: Avoiding Pilot Purgatory and Moving Beyond the PoC towards Proof of Value

Contents

Proof of Concept to Proof of Value: More than semantics

Keep the Business Case at the Core

Define and Track Success Metrics Consistently

Loading component...

Keep Stakeholders Engaged and Accountable

Loading component...

Address Organisational and Personnel Change Factors

Loading component...

Prevent ‘Zombie Pilots’ – Decide to Scale or Kill Early

Loading component...

Secure Budget and Operational Readiness for Scaling

Loading component...

Foster a Culture of Trust and Team Cohesion

Loading component...

Define the Post-Pilot Roadmap

Loading component...

Conclusion

Loading component...

Loading component...

Related information

Loading component...

You May Like

Loading component...

Editor's Picks

Loading component...

Loading component...

Define and Track Success Metrics Consistently

Keep Stakeholders Engaged and Accountable

Address Organisational and Personnel Change Factors

Prevent ‘Zombie Pilots’ – Decide to Scale or Kill Early

Secure Budget and Operational Readiness for Scaling

Foster a Culture of Trust and Team Cohesion

Define the Post-Pilot Roadmap

Conclusion

Related information

You May Like

Editor's Picks