[Sigia-l] Usability Testing

[Listera]

Will Parker:

> On the other hand, after the client and  consultant learn each other's needs,
> strengths and weaknesses and  have come to trust each other, is it still
> foolish to hand more  responsibility to the consultant?

To generalize, there are two kinds of designers: those who implement a given
blueprint and those that create it. The latter is a strategic role where, as
you say, a certain level of confidence has to be present or eventually
developed. When that's achieved, it wouldn't be in the hiring company's
interest to be constantly second guessing the consultant.

Many usability biz people (beholden to orthodoxy) have this notion of a
designer that's either incapable of or unwilling to get/evaluate user
feedback *during* the design process. To them design and usability are two
disjointed activities, performed sequentially by two entirely different and
necessarily separated entities. Therein lies the problem.

> This cuts both ways. An external consulting firm also risks missing
> fundamental strategic goals for the project and for the client. It
> therefore behooves the consultant to learn and adapt to the client's
> communication methods, and also to train the client to provide
> *everything* necessary for the consultant's success.

Indeed. One of the most important aspects of my contracts, from my POV, is
the section where the CONSULTANT requires the COMPANY to provide...[spelled
out in terms of access to key tech/biz/management officers, documents,
company info, market intelligence, domain expertise, etc]. I wouldn't dream
of starting a project without that clause in a contract. Having it right up
front in ink also focuses the mind of the company to get organized to
provide me with the required resources. This way the management knows what's
required of them.

----
Ziya

Usability >  Simplify the Solution
Design >  Simplify the Problem