An integration strategy for onboarding
As a business adopts more SaaS solutions, it will need to review whether it’s integration architecture should be updated so that data can be integrated between disparate systems – the modern digital infrastructure of a dynamic enterprise.
When you onboard new software, integration should cater for types of resources that will make use of an integration capability. These resources are:
- Citizen integrators (aka citizen developers)
Developers are an obvious resource as they will be responsible for most integration needs. But as various sources – analysts, and vendors – are pointing out, businesses are finding they can get some work done quicker by letting people who understand the business processes, and the capabilities and data objects of applications, to do the integration themselves. These are citizen integrators.
If you look at onboarding in terms of Gartner’s Bimodal IT approach, developers would focus on Mode 1( traditional, sequential, emphasizing safety and accuracy), and citizen integrators handle Mode 2(exploratory, nonlinear, emphasizing agility and speed).
There are several reasons for organizations to consider adopting SaaS solutions when they can and moving off legacy applications: whether it’s the postmodern ERP argument, or the issue of technical debt(the concept that an organization will end up spending more in the long run more if it ignores a technical problem when it first arises). Moving apps to cloud often makes financial sense, but you need to have a plan and solutions to implement the change and to support integration.