Skip to main content

Customers, users and other myths

Evey project we undertake has a sponsor.  This may be someone in Academic Registry, in the Finance Department, a College, or any other area of the university.  The sponsor is the person who requests the project and in some cases also provides the funds to make it happen.

Until recently, we called this person "the customer".  Which made sense in one way, as they were requesting and possibly paying for the project.  Calling them the customer encouraged us to focus on satisfying their requirements and steered us away from a purely IT-based view of the world.

Of course, these people were usually senior managers and usually did not actually use the systems we were building or buying.  The users, or sometimes "end users", were a different group entirely.  Although I've never met someone who called themselves an "end user".

The downside of these terms is that they aren't accurate and they obscure the requirements of the systems rather than illuminate them.  If the university has any customers, they are the students and/or the funding agencies, rather than managers spending their allocation of the university's funds.  Even here, the word "customer" or "user" is not helpful.  Students may be paying for their education but the relationship with the university is deeper and more complex than when I buy a book from Amazon.

So we're adopting other words to describe our business.  "Partners" is a word we favour for our colleagues in other parts of the university and this is both an aspiration of how we want to work together as well as an indication that the actual people our systems are for are different again.  And rather than call people "users", why not call them "students" or "staff" (or "applicants", "visitors" or "alumni")?

Comments

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…