Main conference presentation
Admin interfaces: the unsexy side of information architecture
Monday March 26 2007, 2:00 - 2:45PM
Many times as IAs we spend a lot of time designing the end-user interface for a web site; creating wireframes, site maps and user journeys that describe the way people outside a company will interact, purchase or communicate with the organisation.
On my last two projects as well as creating the interfaces for end-users, I created Admin interfaces – interfaces used by internal staff or business users to upload and manage the content on the web site or application.
Unfortunately Admin interfaces are considered the "unsexy" side of IA and ID. Many companies do not see their value until the user is unable to make a change; and then they become necessary evil. They are often under-funded and the last piece of work to be specified.
For a technical information architect like me, it is the ultimate place where you draw together the presentation layer, the database and e-commerce engine to firstly ensure that a user can see and buy products on the site, and secondly continue to maintain the system.
The aim of the case study is to demystify Admin interfaces and provide others who have to create them with lessons out of a relatively successful implementation of an Admin interface. I will talk through the development of the Admin interface for the O2 Shop site and the lessons I learnt in developing that interface.
In particular focusing on:
- the business requirements gathering process
- how the Admin interface integrated with presentation and technical aspects of the site
- timing in the development of the site or "how I created my first XML to carry us through til launch"
- the Admin interface as an change management tool – what NOT to do
- user input and understanding of the tool
To wrap up the discussion I will talk about how I have applied this experience to my next Admin interface and provide the audience with a set of points to consider when developing for an internal audience.
