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

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post, the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web.

We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR:
This is only intended to be suggestive: the real canvas would need to result from in-depth discussions about th…