[Sigia-l] IA Missions

[princeofcats at newarcadia.com]

Hey, I'm game.

-----

IA mission.

You've been contacted by a large technology firm which is in the
process of redesigning their web site and moving a static site into a
content management system. The site is due to launch in eight
weeks; however, there has been no IA presence on the project up until
your arrival. The team has been moving forward based upon a one
page site map and home page wireframe created by the project
manager, and an initial set of business requirements, though
business requirements are still being gathered. There have been no
user studies performed, and the project manager for the site has
indicated that there will be no time for usability testing prior to launch.
The design team has already completed several home page comps,
but are refusing to go any further until they receive detailed wireframes
and a site map. The development team has already begun work,
basing their efforts upon the previous version of the site.

Biz goals: re-launch site, incorporating several legacy extranet sites,
while re-positioning company product offerings to match new
marketing direction, and answering all 'pain points' that have arisen
from previous architecture of site. Prepare for next phase of project,
which will include personalization.

Time: Eight weeks.

My Solution:

1) Make clear to entire team the hurdles posed by lack of user
research and omission of usability testing. Take opportunity to
communicate this to chief marketing officer, and beg for time/
resources to perform at least discount usability testing. Sob inwardly
when I realize he doesn't get it, and then stop worrying about it.

2) After one week on the job, deliver a 3-level site map and an initial
batch of wireframes. Review with design and development teams,
stressing these will continue to change until business requirements
are finalized.

3) During week two, work non-stop to create a detailed site map and
more wireframes. Establish publication schedule: once per week,
updated site map and wireframes will be published. For weeks two
and three, insist upon full team meeting with creatives, developers &
project management to review changes to site map and wireframes.

4) Insert myself into business requirements gathering process, while
establishing boundaries with business analysts. ("You tell me what
needs to happen, and I'll show you how we can make it work on the
web site.") Begin to offer "impact analysis"; "yes, we can do that, but it
will take us x weeks of design/development time."

5) Continue to revise and update site map and wireframes on weekly
basis, while meeting with various business unit owners now coming
out of the woodwork. Establish regular communication with individual
creatives & developers.

6) In week four, create an index linking wireframes to site map, and
add index numbers into site map documentation. Add "confidence"
ratings to every  page of documentation, and communicate to project
management areas in which I foresee difficulties ahead. Encourage
developers to use these ratings for the purposes of triaging the work
they have ahead of them.

7) Repeat step 5 as needed. Stress again to project management that
requirements should be frozen before development begins; nod
fatalistically when they mention "parallel tracking".

8) When IA docs are finally frozen, push for full team review of site,
including developers, project management, and creatives. Cross
check functionality against wireframes, and provide both design and
development team with comprehensive series of notes on what
needs to be changed.

9) Nod sympathetically when project management suddenly
recognizes the challenge of guaranteeing accurate content migration.
Provide sample of content matrix, mapping content against site map
page numbers. Remind project management that there isn't time built
into my contract for me to take control of content migration process.

10) Review changes made based upon notes provided; highlight
changes which were not made, or made incorrectly, and pass back to
design/creative team. Repeat until site matches wireframes & site
map.

11) During final hand off of IA materials, get up on soap box once
again and stress importance of user research and usability testing.

12) Ride off into the sunset.

Result:

The client was delighted (when I wasn't scolding them about their lack
of user focus.) The site launched on time, though the chaos in regards
to content meant several all-nighters for writing team. As far as site
quality, well... in the words of Pierre St-Jacques, "Done is better. Done
is good."