Reason 9: Letting internal technologists own the IoT program

Issues:

It is often the case that a leadership team will outline a strategy to harness IoT and turn ownership of the program to its technologists. This is mainly because they see it as a technology challenge and compare it to previous technology initiatives – therefore having faith that their team can handled it again. It is rare the the internal technical community has the capability of make the right architecture, design, development, integration and deployment decisions and will they can quickly lose sight of the program’s goals as the project is faced with a growing number of technology hurdles.

Avoidance:

From the very start this must be a business first driven program. The goals and metrics have to be driven by real business needs and ownership of the program and its goals needs to be in the line of business. The LOB management needs to assess the capabilities of their own technologists and the central function of IT – it will be upto them to work out how to fill the inevitable knowledge and experience gaps. The technologists need to be fully involved but their key role is work with the selected partners to focus on the integration of IoT system and its business improvements with the rest of the companies systems.

Assess-IoT Advice:

At the leadership level drive hard for the right business strategy and then delegate the full program responsibilities to the relevant LOB(s).  Support the LOB leadership as they seek to selected the right partners. Hold them accountable for the goals with carefully selected metrics. Recognize that a 100 percent in house effort could be doomed from the start.

Reason 10: Development not Phased

Issues:

Once the project capabilities are fully defined it is a natural step to want it deployed as soon as possible. Eager development organizations can quickly over commit to meet aggressive marketing  dates with all the features available at launch. Senior management then have an expectation of immediate business metrics improvements, when the program does not deliver then its seen as a failure.

Avoidance:

IoT projects are complex. Often the full technology stack (from Device, to connectivity, to edge, to cloud, to analytics, to visualizations) is needed to implement the system architecture to support even the relatively simple features. The whole program needs an agile approach with a phased plan, building up capabilities through multiple releases – build and prove the infrastructure with several key features followed by 2 or 3 additional releases. After the final capabilities have been released then fully review the predicted metrics improvements to determine success.

Assess-IoT Advice:

Seek partners with Agile Development, system integration and deployment experience to help establish a phased plan