Loose coupling – the future of work

Just heard Esko Kilpi speaking about the future of work, and totally bought his vision.
To put it shortly: the jobs of the future is not any longer hierarchy-organised or process-organised, put network-organised. The model is the same as the Internet; things are done in loosely coupled processes.
Basically it is an idea expanded from the loosely coupled ICT, and the benefits are similar but wider:
(Source – Forrester Research, “Software Innovation Requires A Loosely-Coupled Application Architecture”)
Loose architectural coupling unleashes innovation – With not having to reinvent the wheel every time you start a new project, your team is more focused on developing innovations and relying on this architecture knowing that it will work as expected. Also, since this enables agility, faster time-to-market is possible and thereby encouraging bringing new innovations to the market.
Loose architectural coupling protects application investments. With business landscape constantly changing either due to M&A or just aggressive growth, it is pertinent for IT to evolve with newer IT systems but also remaining cautious about not breaking the system when retiring an old system or replacing it with a new system (especially relevant for the public sector!). Loosely coupled architectures make this process seamless.
Loose architectural coupling is a design discipline, not a technology. This is not a technology feature that any vendor can tout. This is only a design discipline that can be enabled with a mature ESB. Whether you leverage the publish-subscribe methodologies within the product or use SOA/APIs to construct such loose coupling, it is up to your architects to decide. But, ensure that you are working towards this model, if you already don’t have it.