How to do CoU analysis
Performing a CoU analysis on a product, systems or service is a straightforward, but potentially time consuming activity. Essentially, there are only two steps:
- Compile a list of appropriate project stakeholders and invite them to a facilitated 0.5 to 1 day CoU meeting, explaining beforehand the importance, purpose and format
- Cycle through a suitable context questionnaire
Benefits
An awareness of contextual factors and how they affect usability is hugely important throughout a project development lifecycle. Contextual factors should be considered particularly carefully at the very earliest stages of specification and design, so that the user, their tasks and their environment, are woven tightly into the way the project unfolds. More specifically, CoU analysis will benefit a project by:
- Aiding specification of the context in which a product or systems will be used
- Aiding elucidation and specification of usability requirements
- Helping to shape the possible solution space for a concept or idea, grounding it in the needs and constraints of real people
- Fosters a focused (less hand-wavy) approach to specification and user requirements
- Promotes a sense of the contextual validity of evaluation findings
- Helps generate consensus amongst a working group
Look out for...
Like requirements capture in a more general sense, you should be careful not to do too much with a CoU analysis. In particular:
- Getting ahead of yourself - don't try and solve problems, put right wrongs, create solutions or otherwise be too overtly creative during requirements capture. You'll have time for that later!
- Analysis paralysis - it's generally not wise to attempt too much analysis during requirements capture. By all means note issues and problems that require more thought - but don't try for solutions yet.
|
