Real Life Enterprise 2.0


So what were the architectural lessons I learnt from the customers? Firstly the back office side of things is still a mess, so much for SOA. In fact some people felt that the back end of things was so far behind that there was not even any point in finishing their implementation of the ERP / CRM / SFA / SOA / ESB system that they had underway until they understood the implications of the changes that the businesses wanted to make. The level of frustration felt by the CIO's about these systems was incredible.

Secondly, as I thought, the main interest in the enterprise is supporting new business rather than the same old internal productivity / Knowledge management stuff. The frustration felt by the business and the CIO at the lack of progress with fixing the back end problems rather spills over onto any IT investment projects.

Thirdly whilst the back end is felt to be a mess it was felt that the IT organization just had to get on and build the new systems that the businesses wanted irrespective. There was a ton of excitement over these new systems.


The main types of new systems the customers seemed to be interested in were:

Rich Media channels (video, phone and media center)

Community systems

Advertising systems

Customer Workflow systems

Attention mining systems


These rather nicely fit onto the columns of the Edge architecture.

Comments (3)

  1. Anonymous says:


    Andrew McAfee has been talking to industrialists about Enterprise 2.0 and getting the same reaction…

  2. Anonymous says:

    Patrick forwarded me this latest article from Cringely. Yet another observation that is consistent…

  3. Jon Collins says:

    Good post and it makes sense – in some way it is quite a relief that the world hasn’t yet moved on, the alternative is that I’d be falling dramatically behind! It reminds me of some Component Based Development consultancy I did a few years ago, where we reached the conclusion that the customer needed to think in terms of new applications, and develop service interfaces onto legacy data and functionality where appropriate. Nobody (or very few companies) have the will or wherewithall to rip out or fix their past systems to make them full-fat SOA, which is a relief as well, we *should* be looking to make the most of what has gone before, not throw it all away and start again. Even if that were possible!

Skip to main content