[Sigia-l] RE: IA Practice Maturation

[Welie, Martijn van]

> -----Original Message-----
> From: eric mahleb [mailto:emahleb at yahoo.com]
> 
> I repeat. This is my own experience. For the Europeans
> with different experiences, then great, continue to
> share them since this was the goal of this thread.
> However, there is absolutely no point in fuelling the
> discussion of US vs Europe thing (and that goes for
> the US side as well). It's childish and not condusive
> to interesting and stimulating discussions.

I agree

> 
> BTW, i see IA as only one of many elements of User
> Centered design. Does this mean that at Satama,
> everyone is a User Centered Designer? Plese elaborate
> on this point as i am curious as to how this works. tx

The way User Centred Design works at Satama is roughly like this:

1. When a project is started, a "Concept Designer" first
tries to analyze from a UCD perspective what kind of site
is most appropriate (the "concept"). This involves both
the end-user perspective but also the client's perspective
which is usually very business oriented. The concept designer
has direct contact with the client and iteratively determines
the site concept. It is not uncommon that a consultant is involved
as well. The same goes for a technical consultant in order to 
make sure that what we want to design can actually be built.

2. Once the foundations are layed down, the concept designer
will work out the site in more detail using wireframes, content
structures and flow diagrams. 

3. Once the wireframes start to "stabilize" a graphical designer
is introduced. Both the concept designer and graphical designer
work together to see what the graphical design could be. Naturally,
this involves iterations with client feedback etc.

4. Now that the site structure, flow and graphical design have
been worked out, the detailed design starts. This could be done
by the Concept Designer as well but it is also often done by
more junior concept/interaction designers. At this phase we might
already have some clickable prototypes running for discussion 
purposes.

5. Once the design is completed, the programmers start building 
the site.

What I describe here is the basic ROUGH process. Each projects has
its own peculiarities that may lead to changes in the process.
For example, if the client merely wants a graphical redesign
not all steps are taken.

This of course only describes the process and not the quality
of the outcome. The quality is also heavily determined by the 
client's explicit wishes, the project budgets and the extent
to which we can convince clients to change his mind on certain
issues.

Regards,

Martijn