When we think of messaging systems, the most common place to go is to simple email like Outlook, Lotus Notes, Hotmail or Gmail.  We might even consider Instant Messaging like AIM, Google Talk, IBM Sametimeand Microsoft Messenger.  We could also very easily talk about Ma Bell and new renditions like Skype and Vonage.

However, we suggest that when thinking about messaging systems we need to talk about EDI (eletronic data interchange), ACH (automated clearning house), FTP (file transfer protocol) automation and social neworks like MySpace, Facemail, Bebo, Flickr and many others - oh, and let's not forget OnStar from General Motors.

The point is, message oriented architectures are a core enabling capability that we all should be thinking about and working to understand.  Messaging systems will use many different technologies over the coming years, but it is clear that the core capability will be pervasive.  Software subscription services depend on this capability.  Music and video services that are "on-demand" will fail without them.  Identify theft and banking systems depend on messaging routines to protect us and keep the economy running. 

Messaging logic and systematic controls must be thoughtfully created and organized in order to meet the needs of society at large and your customers on an individual basis.

If you work for a large organization like IBM, CA, Accenture, General Motors, Hewlett-Packard or any other company we recommend that you look at messaging as much broader than just email and that if you care about your customers that you audit and organize all of your messaging systems.  How you manage your messaging systems is at the core of having satisfied customer relationships.

www.iangilyeat.com