Feature: User Experience in a Software Development Team

Within a software development team, most talk of creating a good User Experience (UX) usually relates to creating an intuitive user interface. In the traditional sense this means:
* the layout of the buttons,
* the ability for the application to remember contextual information, or
* the intuitive nature of a web site navigation system.
But these interfaces, although important as the face of the application, are actually only a small part of what makes up the product.

Beyond the User Interface
A software application, like an iceberg, has a great deal of its complexity in the underlying structure of a program, the object model, where there are countless different members (interfaces, methods, and properties, delegates, etc.) which transfer and transform data between objects and to and from the database. While not as visible or as glamorous as the UI these are all interfaces that have users, your colleagues, whose needs must be satisfied.

On one level these users could be considered the most important users to satisfy because the culmination of their efforts make up the finished application. Their ability to produce good software and the trade-offs they make in order to create the software will have a big influence on its character.

Consequently, the environment - and the mindset developers work in - proves crucial to their ability to produce a good overall user experience. Every effort should be taken to ensure that they are focused on creating a good quality product, not in compensating for an awkward development environment or in acquiring the contextual information that they need to complete their task from obscure code.

Creating the right environment for UX to flourish
Every developer should be encouraged to develop this mindset; one way is to ensure that you create code that enables your colleagues to interface with your code easily.

The simplest and most effective way of doing this is by naming your classes and members appropriately. As a rough guide:
* Your objects should be named clearly.
* Your objects and their members should be named so that their intention is obvious.
* Your members should exist harmoniously within scope of the class they inhabit, as well as the overall application.

When the ambiguity is taken out of the development activity, the amount of tacit knowledge needed to complete a task is diminished and the communication between team members is simplified but it's in the subsequent phases of the project when this clarity pays real dividends. Creating an object model that is clear and expressive reduces the amount of background information that has to be re-learnt and understood before starting a development task, allowing the developer to become productive quicker.

As I’ve discussed in this article, the primary benefit of adopting this approach at this point in the development team is a simpler more effective object model, but the secondary and arguably most important benefit is that it encourages and reinforces a user-centric mindset from the ground up, making it easier to integrate the user as an integral part of development lifecycle.

Matthew Goddard
UX Consultancy

Associated Link: UX Consultancy

Online videos: Engaging your users
Source: Webcredible, 6 September 2008
 
A guide to using online video on your site to offer more enticing content and provide a more compelling user experience.

The Office of the Future?
Source: Occupational Hazards via Ergonomics in the News, 5 September 2008
 
The office of the future is less about technology and more about physiology.

This year's 10 best-designed Application User Interfaces
Source: NNg, 4 September 2008
 
Nielsen Norman Group recently announced the winners in its inaugural competition to find the 10 best-designed application user interfaces of the Application Design Annual 2008.

Caroline's Corner: Buttons on Forms - where to put them, and what to call them
Source: Caroline Jarrett, 3 September 2008
 
Should you put the ‘OK’ button to the left or the right of the ‘Cancel’ button? Like so much in forms, the simple answer isn’t really appropriate. And yet, who needs another ‘it depends’?

Three Usability Gurus
Source: avangate blog, 2 September 2008
 
A personal view, but lots of good links, especially if you're new to usability.

Ofcom publishes report on Usability Event
Source: Ofcom, 1 September 2008
 
Independent regulator and competition authority for the UK communications industries, Ofcom, has published its report on usability issues.

Get Fit for Remote Working
Source: UN, 30 August 2008
 
BT Business has announced the launch of a practical guide 'Get fit for mobile working' designed to help mobile workers avoid back, neck and arm problems.

Site Visit Interviews: from Good to Great
Source: User Focus, 29 August 2008
 
For those of you for whom the Basic Introduction to User Interviews wasn't quite enough.

Six Metrics for Managing UI Design
Source: Russell Wilson, 28 August 2008
 
A proposal of six metrics to be used for managing a user interface design department.

Don't Judge a Form by its Cover
Source: Formulate Information Design, 27 August 2008
 
The saying "don't judge a book by its cover" reminds us that looks are deceptive. It turns out that this idiom applies to forms too.