Skip to main content

User Experience and Architecture




Architecture descriptions tend to be dry and technical-looking affairs, with pictures of structure and process flow.  I’m pleased to say that we are seizing an opportunity to present a much more visual explanation of what our target architecture will mean for our users, particularly for our students.

For the last couple of months, we’ve had usability consultants on site working with our students and staff to review the “online experience” that students receive from university systems.  They presented their findings last week, including an outline proposal for a better approach.

To no-one's surprise, the mirror they held up to us showed a rather fragmented set of systems, with unhelpful names, instructions that were often unclear, different versions of the same information, important e-mails buried among less important information, inconsistent look-and-feel, and so forth.  The details of their report are fascinating but far too long for this blog.

What is relevant here is that the consultants also sketched what an integrated experience might look like, and I am taking this part of their report to form the first draft of our target user experience.  Instead of this report being filed in a forgotten folder gathering virtual dust, I want to make it part of our architecture.  The idea is that this will be a living document, to be updated over time by our usability experts and graphic designers. 

This is important. If we are to make this integrated experience a reality, we will need lots of work behind the scenes as well as work on the user-visible aspects.  In fact, we are already working on some of the steps along this path, such as a notification backbone and a set of microservice APIs. (The consultants also praised some of this work, such as our Edinburgh Global Experience Language.)  These sorts of changes can be difficult to explain to non-technical people; with actual examples from the report, we can show people what we are looking to achieve.

A quick look online suggests that there hasn’t been a lot of work combining user experience and architecture.  Yet the two often address the same concerns, and each is necessary to deliver a successful outcome.  It seems a highly synergistic combination to me and I hope to use that synergy to help produce a much better online experience for our students.

Comments

Popular posts from this blog

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

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-de...

"Just enough" Enterprise Architecture

I spent an informative and enjoyable day with a proto-community of people pursuing Enterprise Architecture in UK Higher Education.  Many of the participants had been previously involved in JISC projects and have enjoyed similar events in the past, so I began the day as a bit of an outsider.  In the University of Edinburgh, our progress in adopting "architectures" is mainly on the IT side, via our Applications Architecture and our use of Service-Oriented Architecture .  Enterprise Architecture would integrate all this IT activity with the business processes and goals of the University (or what I sometimes call the administrative processes, for those readers who are unhappy with calling a university a "business"). I've tended to be a little sceptical of fully-fledged enterprise architecture (EA) because it sounds like a mammoth undertaking and the organisations doing it have often been very large corporations.  The two main outcomes of the JISC experiences ar...