Saturday 9 February 2013

Business Architecture Maturity Models


The subject of business architecture capability maturity models has come up in discussion with clients recently. Organisations are seeing them as a means to bench mark their own capability and plan the implementation towards a higher degree of maturity. Whilst I do see some benefit in this, in that it gives you something to think about and ask yourself questions, I am a little concerned to some respect.

The issue is how you can use a maturity model to test yourself against when the discipline itself is unclear and fragmented. Business architecture is different things to different people and is still under innovation and debate in many of its aspects.

What is happening here is that certain well-meaning and well intentioned groups are claiming the space as their own and proclaiming “bodies of knowledge” and publishing models of “their” best practice. Many of these groups are highly I.T. centric and to be honest I am not sure that the provenance of this material is too helpful. Even the Wikipedia entry for business architecture currently promotes and tries to create legitimacy for certain bodies who have perhaps taken it upon themselves to proclaim their ownership of this topic.

Quite often it how an I.T. person thinks business architecture should be from his or her systems based view of the world.  To be fair to them though a lot of the content has value but it isn’t gospel. We are not at a point where these models are of an equivalent status to CMMI or similar.

The forums are full of debate on business architecture and there are multiple threads of thought and opinion, so no firm view in any form is possible at this point in time. I do accept that they probably are worthy endeavours and are based on positive and well-meant intention but one could argue that it is very pretentious and somewhat a potentially arrogant approach.

If organisations are using these models thinking that this is the only way, or seeing them as something to aspire too, when in reality the approach put forward is perhaps not right for their organisation then big mistakes are going to be made. This will not add to the good name of the discipline as a whole.

Business architecture needs to be applied appropriately, not in a one way fits approach; each and every organisation will benefit from an approach that suite: its business, its market and its culture. Business architecture is not painting by numbers!

So we need to use these emerging models carefully and use then to ask questions and promote thought, not as a blue print for what we should do.

The models should be used to develop an appropriate model for the organisation under discussion and then the model becomes a bespoke implementation plan for that organisation not a business architecture maturity model.

No comments:

Post a Comment