Skip to main content

Digital maturity


I had an “A-ha!” moment when reading a book called Enterprise Architecture as Strategy, published by Harvard Business Review in 2006, which has been recommended to me by several architects working in other universities. The book is indeed very interesting. It looks at the overall operating models of businesses and how the top-performing companies digitise their core processes.

The book’s title is slightly confusing because the authors use “Enterprise Architecture” in a rather different way from the main EA frameworks such as TOGAF.  Instead, their book focusses on strategy. If it were written today, a more relevant title might be “Digital Strategy”.

There are many useful ideas in this book but the one that most caught my attention was part of the discussion of “architecture maturity” – or what I call “digital maturity”.  The authors present four stages:
  1. Business silos
  2. Standardised technology
  3. Optimised core
  4. Business modularity
Each stage is described in some detail which I don’t have space to cover here. The key point the authors make is that none of the organisations they surveyed managed to skip any of these stages – they had to progress through each one before the next.

This resonated with me because for several years I have been trying to encourage the creation of plug-and-play business modules, implemented as reusable IT services. This is the “holy grail” of service-oriented architecture and is captured in level four of the authors’ maturity model. In those years, I got nowhere. What this model tells me is that failure had a root cause which is that the overall organisation of the University is not sophisticated enough to support this level of componentisation. I would put the University at level two of the above model.

The evidence presented in this book is that we need to move through the intermediate stage of standardising processes and data across the organisation before we can introduce reusable business processes. So I should stop reaching for the unobtainable and focus on these more modest goals. This intermediate stage will still be a significant advance for the university.

By the way, it was this book that introduced the idea of the “Core Diagram”, which the University of Wisconsin-Madison has used to such good effect.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …