Episode 5

Why integration projects fail

Throughout this video series, we've talked about how to start API-based integration projects, put the right governance in place, secure infrastructure and applications, and get the right adoption and scalability as the program drives forward.

 

In this final episode, we'll focus on what not to do, why many transformation projects still fail and some of the challenges faced by organisations today.

Episode 5-what not to do

Vikram Setia talks about common mistakes that might lead to integration programs' failure.

Episode 5-what not to do

Vikram Setia talks about common mistakes that might lead to integration programs' failure.

Vikram, CCO at Infomentum, gives us an insight into why some of the integration programs go out of control, become too expensive and fail to deliver the promised values. He identifies 3 main reasons:

- lack of a well-defined overall API strategy can leads to unmanageable 'spaghetti' of APIs;

- a poorly designed network of APIs becomes very expensive to build and maintain;

- a common confusion between technologies, like front-end automation, back-end integration and robotics, and their best fit.

The integration platforms like MuleSoft are very flexible and easy to get started on. As a result, many organisations are keen to quickly build small 'pockets' of APIs. When there is no overall API strategy, a created mess of APIs becomes difficult to reuse and maintain. If something goes wrong, it is very challenging to pinpoint the source of the problem. 


According to Vikram, many business leaders are still unclear about the difference between front-end automation, back-end integration and robotics. They are bombarded with promises from different vendors, positioning their systems as perfect solutions to any problem. From the very start of the integration program you should make sure the right technology is used for the right use case and the design principles for these different technologies are in place.

 

Another common mistake is that the strategic decisions are often made based on the processes that were created and documented 10 years ago, not on how the processes are actually being used in the business. Where to start and how not to start is a big topic.

If you have any questions regarding the issues we covered in this video or want to discuss your challenges, talk to our integration experts.
BOOK A 15-MIN VIDEO TALK

Leave quick feedback