For web sites, not
just traffic, but sales, sales leads, etc. ... whatever is important
that you expect your customers and prospects to do.
For software or
web applications, get meaningful feedback on how easily and
efficiently users could work with the delivered technology.
Ask how close the project
was to the budget and the schedule.
Ask what surprises came
up.
Did working with
the consulting company meet expectations?
If the consulting
company says, "We have the technical expertise. We don't bother
with screen design preferences. You just tell us exactly what you
want it to look like!"
RUN AWAY!
Also remember that depth
of experience in graphics and print media does not necessarily translate
to successful web sites.
Depth of experience and
business sense does matter, especially for the proposed project leader.
Find out who that would
be and meet him or her.
Remember - Technology is
a Tool
Dont let the tail
wag the dog!
People and results are the
goals.
Make sure you and the technologists
are clear about the following:
Why you want the technology.
Who you want to use
the technology.
What results you want
the users to have: sales, leads, faster communications, etc.
How you will measure
those results.
What results you don't
want: support calls, complaints, etc.
What kind of budget,
schedule, and resources you have.
Make Demands of the Technologists
Demand ease of use.
Of course, usability
work is recommended.
At least get some kind
of objective feedback from someone similiar to your users.
Not you!
Get someone else to
use the technology design as soon as possible.
When "technical"
issues come up, demand clear explanationsof their impact on
your business need.
Do not feel you must
speak the technologists' language.
Keep your focus on business,
people, and
results.
Make Demands of Yourself
Keep goals simple and straightforward.
Be consistent on your priorities
and expectations.
The KISS principle!
Many technology projects
can and do fail.
A simple project is
far more likely to get done and be successful than a complicated
project.
Go for the clear and
obtainable 'wins.'
Late and major changes can
hurt quality. Avoid them unless they are definitely worth making.