The IoT provides companies with the opportunity to gather data from a wide variety of assets and then transmit it, via the Internet, to cloud-based or other IT systems. Companies can then use this data to reduce the assets’ downtime, streamline their business processes, offer new services that increase their revenues, and otherwise transform their businesses.
However, despite the promise of the IoT, and the success of many IoT projects, there have also been a large number of IoT project failures. These failures have led many companies to ask themselves what they got wrong with their IoT projects, and what they can do differently in the future to ensure their IoT projects are successful.
To help address these questions my firm, Beecham Research, recently published a new report titled “Why IoT Projects Fail.”
As one of the results from the online survey we conducted for this report demonstrates — 58% of the respondents to the survey stated that their IoT project was either mostly unsuccessful, or wholly unsuccessful, with a further 30% stating their projects were ‘mostly’ successful but not entirely so — the question of why IoT projects fail is of great importance to the large and growing number of companies who want to adopt IoT. It is also very relevant to the IoT companies who are providing these IoT adopters with the embedded modules, IoT gateways, smart connectivity services, edge-to-cloud solutions and the other solutions they need to bring these projects to fruition.
In the report we reviewed a wide variety of IoT industry sources and surveys to see what they had discovered regarding the reasons for IoT project failures. We also interviewed and surveyed IoT adopters, IoT solution providers and other IoT experts to understand their perspective on why many IoT projects do not live up to expectations, and why those projects that do succeed, do so.
What we found is that there are four high level reasons why IoT projects fail, with a series of lower level reasons:
Unclear business objectives were a major reason for IoT project failure. This confusion resulted in IoT adopters not understanding what the project needed to accomplish from a technical perspective, in order to meet the company’s business objectives. In addition, our research found that many IoT adopters wanted to be seen as embracing IoT technological developments for the sake of keeping up with market trends, and failed to understand all the complexities involved in actually building and commercializing an IoT application.
Following the launch of an IoT project, many companies also had no clear roadmap for how to evolve, scale, or otherwise move the project forward over time. In fact, we found that in many cases projects were running for several years before management recognized the project was not delivering significant benefits to the company and should be cancelled or revised.
One key takeaway from our research on how first-time IoT adopters can avoid these and other problems? They should start small, with early tests to ensure that the project will realize the business objectives envisioned for it.
In a wide number of cases it is not technical challenges (which can usually be solved given sufficient time and money) which lead to IoT project failure, but rather business and organizational related issues.
For example, different business units within a company might have different perspectives on an IoT project, inhibiting the project’s progress. In particular, with complex projects involving many different business departments or other units, resistance to change by one of the units can lead to the project’s failure. Many first-time IoT adopters also experienced difficulties when they tried to integrate new IoT practices with their older-established, legacy business practices.
What all these issues point to is that IoT adopters need to foster close collaboration between all the technical, managerial, partner, and other groups working on their IoT project if they hope for it to succeed.
Technological problems that were not identified at the start of an IoT project is another one of the main reasons why many IoT projects fail. In particular, our research showed that IoT adopters often fail to appreciate the complexity of the connectivity part of an IoT application. For example, in an online survey we conducted of 25,000 IoT adopters/buyers managed by the IoT M2M Council (IMC) virtually all respondents identified connectivity issues – coverage, reliability, bandwidth, latency – as significant technical challenges.
One of the reasons for this is that first-time IoT adopters that are accustomed to setting up wireless networks at their offices or other facilities, tend to believe IoT application connectivity is a simple matter of plug and play, not understanding that wireless devices were not designed with IoT in mind and that “wireless IoT” can be complex and needs proper planning. For example, scalability with these devices can be a problem as IoT adopters find they need different technologies to expand their IoT application from say 100 sensors, to hundreds of thousands of sensors. Additionally, IoT adopters may find that some connectivity technologies do not provide the wireless coverage they need to connect to edge devices located in remote rural areas, deep inside buildings, or underground. If they assume they will be able to do so and roll their project out anyway, when they encounter this problem it can and indeed has led to project failures. Some examples of this happening are highlighted in our report.
The lack of one universal worldwide network also causes issues, with IoT adopters finding they need to forge agreements with multiple mobile network operators (MNOs) around the world to achieve full coverage. One solution that some IoT adopters are using to address this particular challenge is to work with a connectivity provider who can provide them with worldwide coverage. These types of IoT-focused connectivity providers can deliver global coverage thanks to their agreements with multiple MNOs, and their ability to provide customers with an embedded SIM (eSIM) that can connect customers’ edge devices to all the networks they have agreements with.
A variety of problems with customers and vendors can lead to IoT project failure. Some IoT solution providers have unrealistically raised IoT adopter expectations, or over-hyped the capabilities of their products. Meanwhile, it can be difficult for IoT adopters to secure informed guidance on how to align their IoT project with their business objectives, or find help in determining the real-world feasibility and expected return on investment of their IoT projects.
Another key problem identified in the published surveys we reviewed, as well as our own research with live interviewees and online respondents, is that insufficient IoT skills are a key contributor to IoT project failure. For example, 96 percent of respondents in our online survey cited sufficient expertise as being significant or very significant to project success. If they want their IoT projects to be successful, IoT adopters need to find a way to either acquire these IoT skills, or find IoT solutions that allow them to avoid the need to acquire these skills themselves.
While the problems above have led to many IoT project failures, it is important to keep in mind that the IoT is still relatively young, with many IoT adopters still considering themselves to be at the ‘innovation stage’ of their IoT-driven digital transformation.
In addition, the IoT adopters we interviewed directly have a good idea of what business and technical challenges they must overcome if they want their IoT projects to succeed moving forward. They think that, by utilizing the lessons learned from their own and others’ IoT experiences, they can successfully deploy IoT applications that allow them to improve operational efficiencies, reduce costs, launch new business models, and improve their asset utilization.
Get innovation delivered to your inbox. Sign up for our blog and stay on top of the very latest from Sierra Wireless.
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields