Skip to main content

Interlude: New opportunities for user interfaces

In my previous entry, I promised some thoughts on presentations at OGF20. Since then you will have seen nothing from me. This is not because I lost interest; unfortunately I've been in hospital and then recuperating. Now I'm well again, back to work and the proud owner of a heart pacemaker. I still plan to blog some thoughts arising from OGF20, but for this entry I will deal with a different topic.

I've just read and been inspired by Chris Mairs' 2006 Turing Lecture on Inclusion and Exclusion in the Digital World. Chris takes what could be a dull (albeit important) topic and makes it very interesting by showing the big picture. He's talking about accessbility, which previously I tended to associate with detailed guidelines about which colours to use on web pages and how to tag HTML images with meaningful "Alt" tags. I did consider it important - I'm now old enough to hate small fonts - but I didn't find it inspiring.

Chris's lecture looks both at technologies that help to overcome disabilities (including pacemakers!) and at technologies that are hard to use for disabled people. He gives mobile phones as an example of the latter, as their use of soft keys means that they were practically unusable by blind people - of which Chris is one. He notes that this is not just a matter of a particular technology but has major social implications, as people now tend to use mobiles to navigate their social lives. Similar concerns apply to the World Wide Web.

Now, however, Chris sees many opportunities for improved interfaces - to benefit all sorts of users, disabled people included. To continue with the example of mobile phones, these are now powerful computers with many input and output devices (including microphones, speakers, displays, cameras, GPS, ...). Just as important as the hardware is the software environment: most phones are now extensible platforms with development kits available. This allows third parties to develop specialist interfaces. The next step is to send the data in multiple forms, so that different interfaces can process it differently. For example, a phone choice menu might be sent both in sound ("Press 1 for new sales, press 2 for...") and in XML (" 1: New sales ... ").

What I found inspiring was Chris's optimism and sense of opportunities. The use of open platforms and cool technology could benefit lots of us in many different ways. I recommend the article. Unfortunately you may have to pay to read it - it's online at


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…