Skip to main content

Michigan Enterprise Strategic Assessments

Today I visited the EA team at the University of Michigan in Ann Arbor.   One of the things they showed me was their template for IT services to document their strategic plans.  These are called MESAs, which stands for Michigan Enterprise Strategic Assessment.  The name was adopted to fit the shape of the headline diagram in the template, which looks like this example:

Components of the service are placed along the curve to reflect their position in the life-cycle at UMich.  As the deployment of a technology or other service component becomes more mature, it moves along the curve from left to right.  The vertical axis shows when the component is in wide use.  The curve is the same for all services – it is like the Gartner hype curve rather than a graph of specific values.  The icon for each component shows whether a component is recommended or deprecated, with more recent versions of the chart also including an icon for components which are being evaluated.

As with Core Diagrams, and several other EA techniques, the value of the technique lies as much in the conversation as in the final deliverable.  It provides a focus for service groups to reflect on the strategy for their service.  The diagram also provides an easy way for other people to see the maturity of each service. 

The full MESA report for a service includes a second chart for a 3-year lookahead, a one-page summary of the strategy, and one page describing each service component, including why the component has been assigned the status shown on the chart.  The report may also include a TIME diagram.  The full report for the example shown above can be seen at .

UMich have a wiki page that shows all the 39 MESA charts they have developed so far.  These cover about half of the 37 services in their service catalogue.  Some services have found the technique so useful that they have produced multiple charts for different aspects of the service.  The central wiki page gives a quick overview of the strategic plans for each service.


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

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…