Maximum Usability Analysis

REDESIGN—Maximum Usability Analysis

Task	Purpose/additional information	Mandatory/optional	Deliverable	Stage of C22 process	Effort (# days)	Duration
Preliminary analysis
Interview client about usability issues with an existing site or usability concerns in general—or have other members of team follow a usability “screener” which will be followed up on if necessary	To understand what problems current users are having so those problems are taken into account in redesign	Mandatory that at least screener be completed	Verbal communication to creative team or brief report	Imagine/ Define	4 hours	One or possibly a few brief meetings
Expert review of existing site—an informal internal review is recommended even if client does not want an official review	If client wants to retain some element of old design, or learn something from it	Optional, but at least an internal review recommended	Report	Imagine/ Define	1-2 days	1-2 days
User testing on existing site	If client wants to retain some element of old design, or learn something from it	Optional	Report	Imagine/ Define	3-4 days	3-4 days
Expert review of competitor’s site	New site should supercede competitors’ sites in terms of usability	Optional	Report	Imagine/ Define	1-2 days	1-2 days
Set usability benchmarks/objectives—part of site concept document or separate concept document?	Based on client/site needs and on current or competitor’s sites (e.g. Site X [or current site] enables users to purchase items with three clicks; new site should require 3 or less).	Optional	Brief report/list	Imagine/ Define	_ day	_ day

Task	Purpose/additional information	Mandatory/optional	Deliverable	Stage of C22 process	Effort (# days)	Duration
Analysis of prototypes
Site inventory consult/review with Experience Architect (iterative)	To ensure that inventory is focused on the site’s audience- can serve as QA in some cases (i.e. on Chicago-based projects)	Mandatory	Verbal communication or informal documentation	Define	4 hours	5-10 days
Site Architecture consult/review with Experience Architect (iterative)	To ensure that architecture is logical and promotes easy navigation and task flow	Mandatory	Verbal communication or informal documentation	Define	4 hours	5-10 days
Greyline consult/review with Experience Architect/Web Engineer (iterative)	To ensure that greylines follow usability principles and support user’s needs	Mandatory	Verbal communication or informal documentation	Define	3-2 hour sessions	3 weeks
Color Line consult/review with Experience Architect/Visual Designer (iterative)	To ensure that colorlines follow usability principles and support user’s needs	Mandatory	Verbal communication or informal documentation	Define	3-2 hour sessions	2 weeks
Build scenarios/Cognitive walkthrough with the Experience Architect (and others?) on greylines/colorlines	Enacting different users’ experiences on site- could also encourage client to do their own walkthrough by giving them a list of tasks (?)	Mandatory	Optional report on results of cognitive walkthrough	Late Define	1 day	1 day
User testing on greylines/colorlines	To assess usability before majority of building site begins	Optional, but highly recommended	Report	Late Define	4 days	2-3 days

Task	Purpose/additional information	Mandatory/optional	Deliverable	Stage of C22 process	Effort (# days)	Duration
Analysis of Final Project
Expert review of final product	Compare to previous review/testing, to future phases, or to competitor’s site	Optional, but highly recommended internal review	Report	Deliver	1-2 days	1-1 _ days
User testing of final product	To compare it to previous review/testing, to future phases, or to competitors’ sites	Optional	Report	Deliver	3-4 days	3-4 days
Assessment of final results against usability benchmarks/objectives	To provide a measurable assessment of whether usability has increased and by how much	Optional	Brief Report	Deliver	_ day	_ day

Total effort: 4 days – 18 days

NEW DESIGN- Maximum Usability Analysis

Task	Purpose/additional information	Mandatory/optional	Deliverable	Stage of C22 process	Effort (# days)	Duration
Preliminary analysis
Interview client about usability issues with an existing site or usability concerns in general—or have other members of team follow a usability “screener” which will be followed up on if necessary	To understand what problems current users are having so those problems are taken into account in redesign	Mandatory that at least screener be completed	Verbal communication to creative team or brief report	Imagine/ Define	4 hours	One or possibly a few brief meetings
Expert review of competitor’s site	New site should supercede competitors’ sites in terms of usability	Optional	Report	Imagine/ Define	1-2 days	1-2 days
Set usability benchmarks/objectives	Based on client/site needs and on competitor’s sites (e.g. Site X [or current site] enables users to purchase items with three clicks; new site should require 3 or less).	Optional	Report	Imagine/ Define	__ days	__ days

Task	Purpose/additional information	Mandatory/optional	Deliverable	Stage of C22 process	Effort (# days)	Duration
Analysis of prototypes
Site inventory consult/review with Experience Architect (iterative)	To ensure that inventory is focused on the site’s audience- can serve as QA in some cases (i.e. on Chicago-based projects)	Mandatory	Verbal communication or informal documentation	Define	4 hours	5-10 days
Site Architecture consult/review with Experience Architect (iterative)	To ensure that architecture is logical and promotes easy navigation and task flow	Mandatory	Verbal communication or informal documentation	Define	4 hours	5-10 days
Greyline consult/review with Experience Architect/Web Engineer (iterative)	To ensure that greylines follow usability principles and support user’s needs	Mandatory	Verbal communication or informal documentation	Define	3-2 hour sessions	3 weeks
Color Line consult/review with Experience Architect/Visual Designer (iterative)	To ensure that colorlines follow usability principles and support user’s needs	Mandatory	Verbal communication or informal documentation	Define	3-2 hour sessions	2 weeks
Build scenarios/Cognitive walkthrough with the Experience Architect (and others?) on greylines/colorlines	Enacting different users’ experiences on site- could also encourage client to do their own walkthrough by giving them a list of tasks (?)	Mandatory	Optional report on results of cognitive walkthrough	Late Define	1 day	1 day
User testing on greylines/colorlines	To assess usability before majority of building site begins	Optional, but highly recommended	Report	Late Define	4 days	2-3 days

Task	Purpose/additional information	Mandatory/optional	Deliverable	Stage of C22 process	Effort (# days)	Duration
Analysis of Final Project
Expert review of final product	Compare to future phases, or to competitor’s site	Optional, but highly recommended internal review	Report	Deliver	1-2 days	1-1 _ days
User testing of final product	To compare to future phases, or to competitors’ sites	Optional	Report	Deliver	3-4 days	3-4 days
Assessment of final results against usability benchmarks/objectives	To provide a measurable assessment of whether usability has increased and by how much	Optional	Brief Report	Deliver	_ day	_ day

Total effort: 4 days – 16 days

Copyright 2002 Chromosome22. All Rights Reserved.

download the WORD .DOC (64k)