Skip to main content

Away Day: Service Management

Every four months, our Division's management team have an Away Day, a chance to concentrate on particular aspects of our work without the distractions of our day-to-day responsibilities.  We don't go very far, just to a meeting room in the University's Salisbury Green hotel, right next to Arthur's Seat, but it is away from our respective desks.

Yesterday we focused on the three year strategy for our own services, the ones run by our Service Management section.  These include the university portal, the web hosting service, the lecture capture service, the VLEs and other technology-enhanced learning tools, the ID management system, the electronic voting system, and others.  The three team leaders from the section presented their plans clearly and their presentations triggered lots of discussion.  We reviewed their plans for making services even easier to use from smartphones and tablets, adding functionality without duplicating effort, and integrating services so that users have the information they want when they want it.

One issue that we returned to throughout the day was the need to engage users in our service plans .  We plan to establish more user groups for our services and to involve these groups in the design aspects of our projects.  As the leader of Development Services, this is something I am very keen to take advantage of.   Close user involvement has been key to the success of our Agile development projects and we could do more on other projects if we could investigate user interface options early on.

From a projects point of view, we also discussed how to run more usability evaluations and to engage service management in the usability and graphics aspects of our user interface design.  From a corresponding service point of view, we discussed how to provide continuous improvement via a range of options, from small enhancements through to making better use of our project planning processes.

There was plenty to discuss and several useful points arose that we will be taking further.  Hopefully this day spent away from the mundane will lead to better services for all our users.


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…