Wax On, Wax Off

There is something symbolic about it: organising an IT / architects conference in the Central Hall in London. Right next to the Big Ben and Westminster Abbey, The Open Group Conference takes place once more in one of the landmark buildings of the protestant Methodist church. Established in the 18th century by John Wesley, the Methodist movement consists of people that aim to live a devout, serious life. Not some noncommittal philosophising about the heavenly glory and all that, but practicing faith every dag again, through dedicated, hard work. It’s only when you share your meal in the soup kitchen with the underprivileged of this world, that you start to experience the real essence of faith, so the Methodists believe.

Interesting thinking and at the very least, it gave an extra dimension to the Architect’s panel discussion I witnessed on the podium of this same building, now exactly two years ago. The topic was the eternal tension between the long term and the short term. In the panel,  there were enterprise architects, IT strategists and a market analyst (no, not exactly the underprivileged). The hypothesis discussed was that the shallowness of today’s economic climate asks for a more careful, architected approach. That way, the requirements of the business can be much better aligned with solutions and it will be easier to achieve – and demonstrate – the value of IT.

A politically correct argument that nobody could really oppose to.

But one of the panel members, the CIO of Transport for London, was in no mood to be politically correct. “Yes, architecture and strategy” – he pronounced these words with just the subtlest hint of disdain – “all of that is absolutely crucial, but if the buses don’t run tomorrow because of a computer error nothing else matters much anymore; let’s make sure we master the basics first”. Being a seasoned manager of quite some IT departments, he was proud to tell the audience that he brought back the size of his architects team to just one fifth. “Anybody who doesn’t truly understand what happens in the everyday operations or fails to bring direct value to it, is of no use to me”.

Now that warmed up the audience. John Wesley would be proud of it: how spiritual and high-aiming our ambitions may be, we can only truly live up to them through the sobering experience of daily practice. Dreaming about Business/IT fusion, perpetual innovation and Web 2.0? Fine. Just make sure my workstation functions every morning first.

And the one does not exclude the other. Having an extraordinary good grip on infrastructure and core applications motivates: it generates exactly the positive energy that is needed to explore new ways over and over again. The foundation of change therefore is in repetition, routine and control.

Wax On, Wax Off, as another spiritual leader would say. Change yourself, but always with both feet firmly on the ground. For that, you don’t need to be a Methodist to say hallelujah.

This post is a slightly modified version of a 2009 post on Capgemini’s CTO blog.
Posted in English | Leave a comment

White Elephant

Just to make sure: there is absolutely nothing wrong with White Elephants. Actually, in Asia they were often regarded as signs of prosperity and success and emperors would hold them as status symbols. On the other hand, these huge animals would deliver little value and yet cost a fortune to be maintained.

A White Elephant thus shows a fair balance of blessings and curses. Much like in the world of Business Process Management, which has its own collection of trunk bearing white animals. They are called Proof of Concepts. Sometimes, it’s too hard to explain to the organization what BPM can do (especially if we ask the Mother of All Truth, Wikipedia about BPM: “a holistic management approach focused on aligning all aspects of an organization with the wants and needs of clients”, sounds – well – very holistic indeed).

A local proof of concept, pragmatically addressing a real issue in the business, is then often a splendid way to break through the inertia. As we will show through three cases at the upcoming Gartner BPM Summit, it demonstrates the value of BPM and paves the path towards wider enterprise use. But every now and then, the owners of such a prototype become so attached to it, they cannot dispose from it anymore. It becomes their own, precious status symbol. Keeping it alive, scaling, performing and integrated with other systems requires disproportionate attention and budget. It can even inhibit a wider roll-out. It looked so fresh, promising and simple in the brochure of the technology provider. But now this big white beast has outgrown its stable and is blocking the entrance.

How to prevent it? Manage expectations upfront, explicitly. Design for scalability, performance and integration. Create and maintain an architectural perspective. Essentially: think cradle-to-cradle, even when it is ‘just’ a proof of concept.

There is great potential in a new breed of solutions that have BPM inside. Just make sure they don’t grow into White Elephants. Unless you are an emperor, of course

Posted in English | Leave a comment

The Hammers & Nails of BPM

I am preparing for a panel debate and a brief case presentation at the upcoming BPM Gartner Summit in London. The theme of the summit is “Making it happen: Driving high performance results beyond the hype”. And although it makes you think of airport billboards, it has a promising, pragmatic tone. Let’s hope it works out, because you see: every now and then when the like-minded of our industry meet, they seem to be tempted to indulge in their own, well-fenced topic. They forget about the world outside and why they were into the topic in the first place.

It happened to SOA. SOA gurus discussed with other SOA gurus the importance of SOA, the journey to SOA, how to set up a SOA governance, SOA centres of excellence, SOA reference models, how to insure SOA compliance and – unavoidably – the ins and outs of SOA maturity models. Turned out that nobody else cared about SOA (only in what it could deliver) and it took some time for the profession to realise and pronounce the topic ‘dead’.

Conferences full of Hammers discussing Nails in all sizes, categories and colours, I am sure you can easily point to similar areas (Cloud, EA, Web 2.0, anybody?) now and in the recent past. Is it happening to Business Process Management too? Maybe.

It could be tempting indeed to dive into the mechanics of BPM, understanding how to create a culture of continuous process improvement, what methodologies to use, how to promote process stewardship across the organisation, essentially how to live and breath process. But here is the catch: process is not the Holy Grail and managing processes is not the Meaning of Life. Seriously.

We’re in the business of results: value that can be defined and measured. And yes, there is a growing number of organisational pains and aspirations that can be addressed with great solutions that are Powered by BPM. And for sure, if we want sustainable impact, we need a proper BPM governance and mindset (BPM Power, if you like). But in the end, the business case counts. Not an organisation’s score on a BPM maturity index.

This is why I particularly look forward to presenting three real-life cases that created clear results, including a compelling ‘drink your own champagne’ one within our own organisation. I would have loved to present a fourth case story in which we decisively voted not to apply BPM and created tremendous success.

But admitted: for this audience, that would not exactly hit the nail on the head.

First published on Capgemini’s CTO Blog
Posted in English | Tagged , , | Leave a comment

The Inception of TRAIN and SCOOTER Apps

Just sharing with you that we are currently finalizing the 2011 edition of Capgemini’s TechnoVision. An important inception is the analysis of the applications landscape and the impact on delivery models as we are shifting towards a new category of solutions that are lightweight, agile and created in – or very near – to the business.  Actually, we distinguish different ‘Application Lifecycles’, each with their own dynamics around requirements, quality, time-to-market, agility, tools being used and place within the organization. We thought a transport metaphor would be quite effective, so prepare yourselves to be familiarized in the near future with 5 different types of applications, ranging from TRAIN apps (solid, stable, standard, predictable) all the way to SCOOTER apps (highly individual and personalized, ultra-agile, ad-hoc). Much more soon, so stay tuned to this blog. For now, one little visualization of what happens when you try to make a TRAIN application behave like a SCOOTER. I believe our ‘application city’ streets are full of these trains gone rogue. Let’s hope they are just a bad dream soon.

Posted in English | 2 Comments

Boniface and the Cloud

In 754, Boniface found out the hard way that too much evangelizing will kill you. Would the poor man have lived in our time, no doubt he now would be an IT guru. Think about it: the IT industry is relatively young and immature. New, augmented, much improved solutions pop up over and over again. Initially, their potential only seems to be grasped by a few – self-proclaimed – enlightened ones that feel the irrepressible urge to inform, than convince the rest of the world. Which would be just fine, if only they knew when to stop preaching and start acting. It happened with open source, 3G mobile, SOA and – still raging on right now – Web 2.0. I am quite sure you can fill in the blanks yourself, easily naming more promising IT themes that quickly became a buzz and ended up evangelized to death or at least boring the hell out of everybody involved.

Cloud is such a promising theme as well. And it’s entirely up to us if we want to meander yet another few years around it – discussing definitions, benefits, obstacles and possible roadmaps – or start doing something useful right now.

Somehow, time is much shorter nowadays. It helps to become pragmatic. I conclude that already today, cloud-based solutions have set a new benchmark, a new ‘normal’, in terms of how easy it should be to buy, create, deploy and manage an IT solution. The business side already gets the point and they may need much less convincing than the IT side thinks.

Yes, it’s 2011. Time to act.

And believe it or not, there are books on their way that can help considerably. I just reviewed one, written by an illustrious team of professionals within the Capgemini group together with our partner IBM. For sure, it contains all the definitions, insights and perspectives that get a firm grip on the cloud phenomenon. It’s all the bible you need, if you like. But more importantly, it is down-to-earth, pragmatic and action-oriented. This is illustrated by many cases from real life, telling us about inspiring people and their businesses, already exploring, testing, learning and benefiting from the cloud.

The same approach is taken by the cloud work group of The Open Group. They are currently synthesizing the excellent results that have been produced last year into the upcoming ‘Cloud Computing Guide for the Business Executive’. Yes there are definitions again (fortunately the work group chose to embrace the definitions of the US National Institute of Standards and Technology, which seems to evolve into a generally accepted standard; saves a lot of time) and there are quite some musings about cost models, risks, roadmaps and disruptive business models. But central in the guide is a collection of 24 Cloud Use Cases: very business-oriented, most of them sector-specific, distilled from real-life scenarios and experiences, ready to be used right now.

Two titles to look forward to. I will keep you informed. In the meantime, here is the motto for 2011: stop evangelizing, start acting.

First published at Capgemini’s CTO Blog

Posted in English | Tagged , , , | Leave a comment

The Zen of applications retirement

When our new ExpertConnect site was launched a few days ago, several people asked me what – for heaven’s sake – I mean with ‘seeking the Zen within technology’. Well, first of all I must admit I know nothing about Zen: I never even caught a glimpse of the Ox’s hoof marks. I do however like the emphasis of Zen on disciplined training and a continuous polishing of the basics (more about this on our earlier ‘Wax-on Wax-off’ blog item). It contains a highly relevant message towards our own profession:  a carefully crafted, yet simple foundation of infrastructure and core applications is a must for anything fancy and innovative on top of it.

Zen teachers often tend towards pragmatism. I particularly value a lesson I once learned: whenever you buy a piece of clothing, get rid of two others first. In this way, getting something new also creates a welcome opportunity to clean up. It’s crucial to deal with the inertia of chaos, to stay in control, even improve your grip on things.

Why not apply this principle to applications? We know all too well that the petrified, cluttered application landscapes of today keep us from moving forward. They are like clothing closets that are completely packed; so much that we don’t even dare to open its doors. We would love to build new applications that better serve our business users, applying new technologies and tools. But we must create the headroom for it first, by sanitizing what we already have.

Whenever you want to add an application, get rid of two others first.

So how is that for a rule of thumb? Quite a useful guideline when creating the portfolio strategy for next year or when somebody jumps into your office with a brilliant idea for a new project. It legitimizes the noble craft of applications retirement and links it inseparably to implementing new ones. You build something, you retire more.

Getting rid of your once beloved babies can be an almost emotional process. In practice, we have found that it is not only a matter of having good tools, the right applications intelligence and a solid business case (all of these are crucial, though): it is also a matter of being emphatic to the change dynamics of the organization and the personal drivers of the people involved. More about this at HP Software Universe in beautiful Barcelona (November 30 – December 2), where we will be introducing a joint effort around applications retirement. It involves both state-of-the-art tooling – records management, database archiving, project and portfolio management – and a wide-angle approach that considers all the crucial success factors.

Yet much more to be said about this topic. What happens once applications actually have been marked for retirement? (often nothing, because few people have real experience with shutting down applications, let alone that they have documented procedures for it). And what will be the impact on retirement when the We have an App for That philosophy starts to hit our desktops in the forthcoming years? Just a few questions around a vital theme that no doubt will have more spotlight in 2011. So free your mind, open the door, and we will quickly be back on this blog with more thoughts about how to clean up that closet.

First published on Capgemini’s CTO blog

Posted in English | Tagged , , , , , | 5 Comments

SAP Lifecycle: slicing for value

This is a metaphor. Imagine you wake up one morning and find an elephant in your backyard. It has settled itself comfortably in the garden shack and does not seem to be planning on moving anytime soon. It is easy to feel the potential and immense power this creature can bring. But you may quickly find yourself occupied by managing collateral damage and making sure the elephant doesn’t swallow your entire budget already for breakfast. In the meantime, in the house people start to ask questions what that animal is doing in the backyard in the first place.

Again: this is a metaphor. I am not implying that the average IT landscape – more specifically a typical SAP-oriented one – is just as intimidating and immovable as an elephant. But the sheer size and complexity of an installation can absorb all management attention. It leaves little room for unleashing the true potential of the solutions, let alone that it can be discussed with the business side of the organisation. This becomes all the more difficult when you consider upgrading to a major new version of the platform: it may require significant upfront investment and – at first sight – provide little direct value to the business.

So how do you manage something big and imposing like that? Well, think about slicing it. And getting a bit outside the box (or shack, if you like). Very few will doubt that by now the cloud has become a serious mechanism to deliver solutions to the business community. And although not all of it may be considered enterprise-ready yet, the phenomenon is quickly setting a new benchmark for what to get from the IT department. Business users start to expect focused, fine-grained solutions that they can activate any time they like. They expect to pay for it per use or on a subscription basis. They don’t want to be exposed to the infrastructural requirements of the solutions. And they certainly don’t want to be bothered by upgrades and other considerations for improvement.

All of this is in the rationale behind one of the more crucial propositions to the market I have seen in quite a few years. It is SAP Lifecycle, one of the flagships of Capgemini’s increased focus on managing the entire lifecycle of complete application landscapes.
It reduces the complexity and capital expenditure of implementing or upgrading to Business Suite 7, securing applications management, applying platform innovations and – if needed – running the underlying infrastructure to one simple thing: a pick & choose menu card of elegant, clearly defined business services that are paid for on a subscription basis.

To me, it is the future of packaged based solutions: a set of business services you can subscribe to with all the underlying complexity – including the very fact that there are package components inside – shielded off. It gets rid of massive capital expenditure and replaces it by much more flexible, operational expenditure. It also secures innovation, as new business services are made available – like a menu card that evolves with the seasons – and the provider handles all the technology innovations inside the platform.

Best of all, by defining and pricing at the level of fine-grained business services, you find that they – finally – become a topic again to discuss with the business side. Not only in terms of what individual, core business services should cost, but also what the immediate value would be of new services that can be activated. This is the reason why frequent value workshops – to understand these dynamics – are an integral part of the proposal. After all, in the end you want to be involved with your business users in these type of value workshops, not in risk review boards or at the receiving end of spreadsheet costing.

You will appreciate that there is some spectacular complexity behind the deceivingly simple façade of the menu card. Both in terms of technology – upgrades, migration, applications management, hosting – as in terms of financial engineering. I have witnessed some of the brightest minds in our company deal with the challenging economics of transforming big monolithic investments into flexible subscriptions. And all that without scaring our corporate legal and risk management people too much.

True heroism indeed. But then again, it takes nothing less than a bold approach to get an elephant to move. Or to get it sliced, if you like.

(Oh, did I already mention that elephant was just a metaphor? )

First published on Capgemini’s CTO blog

Posted in English | Tagged , , , , | Leave a comment