Loosely Coupled v Tightly Integrated
14 January 2008 2 Comments
I’ve been mulling over the loosely coupled versus tightly integrated systems development arguments and in particular Martin Weller has a number of posts on the subject including this one. In it talks about the control issues which are faced by many organisations. I’m in agreement with him about favouring a less restrictive approach but perhaps not for the reasons he gives. My main reason for having a set of ‘loosly coupled’ services many of which may be externally provided is for the following reasons :-
1. Expertise through experience – People have spent years developing specific tools to serve particular purposes, they do this very well (which is why their products have lasted years) so they give a rich and fulfilling user experience. When these are re-created within a VLE much of the richness appears to be lost. For an example of this I’ve always used FirstClass which is a CMC system (plus some other bits as well now) but at it’s heart is a well designed interface of conferencing. When we move to a VLE the alternative provided is a forum posting system. This reduces the functionality and user experience significantly just so that it can be ‘tightly integrated’.
2. Complex systems lead to complex solutions – When you try to develop something to do everything for your business (Enterprise Content Management and Virtual Learning Environments being two that we are grappling with at the moment) they rarely knock down all the pins. It’s likely they’ll do a lot of good things but that shouldn’t then mean they replace everything that went before them. If they don’t do something as well as it can be done externally (for example blogging) then organisations should look to use an external blogging service instead. Organisations should get over the ‘not invented here’ or even the ‘not commissioned here’ syndrome.
3. Your staff and students use other systems anyhow – In staff and students are using external blogs, wikis, social networks, search engines and so forth so the idea of controlling those people to use your own in-house system is mute. Once you recognise this fact it allows you to think in a more loosely connected fashion about how to join up resources and tools. Things such as Google Desktop start to become much more of a business tool. Read my previous posts about horizon scanning for some information about how businesses are picking up on this idea of incorporating some of these tools.
4. Get someone else to do the work – Why build and support a product when someone else can do it for you? All you need to do it integrate it. If new browsers arrive then it’s someone else’s problem to ensure that the products work with them. You can of course help (in an open and collaborative fashion) but the effort is hugely reduced by not building everything in-house.
5. People like to share – There it is. In organisations where information is tightly controlled there are always communications difficulties and duplications taking place. I don’t mean that we should open everything up to the world (‘going naked’ as people keep saying) but transparency is no bad thing. Where it can be applied, it should be applied.