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

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

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…