User-centred design and prototyping

Last night I presented to the Australian Business Analysis Association (ABAA) on a topic that is close to my heart — user-centred design and prototyping.

As business analysts, we’re often focussed on eliciting business requirements for systems, managing the relationships between the business owners and the vendors and developers of the technology. Unfortunately, we sometimes forget that what we’re doing is delivering a system that is for users. This results in us delivering the ‘what’ in terms of requirements, but forgetting that there’s a very strong need to find out from the people who will use systems the ‘how’ it will work for them. If you’ve worked with an Information Architect before, this is exactly the head-space that drives their activities to determine navigation paradigms that are truly usable and accessible and systems that are designed to meet people’s needs in an intuitive way, rather than systems by developers that you have to ‘learn’ how to use.

User-centred design seeks to change all that by putting the user as the focus of all project activities, from scoping, to analysis and requirements gathering, all the way through design and delivery.

Starting with prototying in the scoping and planning phase is a great way to swing things back to the a focus on users — storyboarding and interactive prototypes are two of my favourite tools to achieve this goal.

If movie-makers like Pixar and Peter Jackson can use these tools to make movies that people will go to see and enjoy, then BAs can also make use of them to design systems that people will want to use.

M