Five Reasons Why IIoT Projects Fail at the PoC Stage

DZone 's Guide to

Five Reasons Why IIoT Projects Fail at the PoC Stage

Have you been trying to launch an IoT or IIoT solution, only to see it fall apart? Here are the mistake any good PoC needs to avoid to result in success.

· IoT Zone ·
Free Resource

Nearly 70% of IoT and, implicitly, IIoT initiatives fail at the Proof of Concept (PoC) stage, according to a recent study by Cisco. Though the number looks high, it resembles the past records of other new initiatives such as cloud computing, agile initiatives, and likewise.

What are the main reasons for such high failure rate of the projects at an early stage? I am attempting to highlight few main factors that could lead to such a situation.

Jumping the Hype Bandwagon Without Proper Clarity on Business Impacts

Typically, business needs should be the driver for the technology changes. Business should drive the technology, and not vice versa. However, many times it happens so that because of the technology hype cycle, leaders gets excited and would like to be seen as the front-running change agents. They would like their department to be the one showcasing the leading edge of projects. In such cases, the feasibility and viability aspects are not adequately studied in detail and the PoC is started with incomplete information. In such situations, parties rarely arrive at a common expectation of outcomes. Each of them has their expectations, which is documented only in their mind. As things progress, the differences in expectations start to come out into the open, leading to tussles and impacting project outcome profoundly.

Image title

Scaling Roadmap Is Not Drawn

It is important to do a PoC and validate the concept before going for full-fledged implementation. It helps in validating the concept, end user desirability, and creates ample room for incorporating feedback from business stakeholders. Though it is not required in detail, a high-level roadmap that gives a clear view of how things are to proceed from start to end is a plus. This provides clarity to the mission, links the actions with the vision for the initiative, and keeps check on the timeline, cost, etc. If a scaling roadmap is missing, the team carries a lot of confusion, apprehension, and doubt in mind, leading to less than 100% dedication.

Missing Talent and Expertise for Implementation

IoT is still an evolving concept. Constant innovation is taking place on an ongoing basis. The project implementation needs very high expertise on technologies that have just arrived, or in some cases are not yet in the market. Finding talent, the skill set, and expertise for such projects is hard. Reference implementation and best practices may still be lacking, further leaving room for some experimentation during implementation.

Missing Integration and Collaboration Among Various Teams

IoT projects have several interdependent components, such as hardware, device software, protocol stack implementation, gateway systems, backend systems, end user application, analytics, etc. Several independent teams are working on these components, which have very high interdependency on each other. They should constantly work in perfect collaboration with each other, having concise and precise communication on a regular basis. Invariably, it happens that team collaboration doesn't work perfectly, leading to undesired situations.

Changing Priority and Missing Management Commitment

Any new change is expected to create rough weather. Change is supposed to face internal and external resistance, and sometimes a lot of criticism. In such situation, it is important that all important stakeholders are rightly onboard and provide their complete support. Crucial support and backing of senior management is key to the success of such initiatives in hard times. Patience is the key and the outcome will follow. If there are frequent changes in the management priorities, it is bound to lead to failure.

iot ,iiot ,poc ,iot solutions

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}