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

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…