We have been dealing with this issue here at Image Works. Until I arrived a year and a half ago the designers did most of the IA by default. We have been working out a balance between the two disciplines.
 
The overview is this: during the IA process I drive the process using the designer for input. When visual design starts, the balance shifts and the designer takes over, using me for input. The project manager and I get final say as to whether the page meets the client's goals and is ready to be shown.
 
Here is the process:
1) The lead designer is brought into the project when IA first begins - during the brainstorming stage. This allows him/her to be introduced to the project, client goals and user goals.
2) I paper prototype the site, using the designer as a resource as needed.
3) Before the client sees it, the designer double checks the prototype to make sure I haven't created anything that will be difficult/expensive/impossible to execute. The prototype represents relative prominence of features but does not necessarily reflect final layout.
4) I hand off a document to the designer that lists (in outline form) the page components and their relative importance. I also hand off the prototype, but the designer is not bound to it.
5) When a first draft of the design is done, I review it from two perspectives: human factors and meeting the client's/user's goals. If something isn't working it is my job to say why and we will probably discuss it. It is the designer's job to figure out how to change it, although we will probably discuss options.
 
The whole process is one of negotiation, mutual learning, cooperation and respect.
 
It helps that our designers (and programmers, BTW) are trained in usability and human factors. Their goal is not to create a great looking page - it is to create a great looking page that meets the client's goals. (We have a very user-centered process, so the assumption is that by the time we get to this stage the client goal's and user's goals have been aligned.)
 
Elisabeth Paine
Customer Experience Strategist
Image Works
207-773-1101 ext. 106
 
 -----Original Message-----
From: Benette Datu [mailto:Benette@asiaonline.net.ph]
Sent: Thursday, March 01, 2001 3:48 AM
To: 'Peter Merholz'; sigia-l@asis.org
Subject: RE: SIGIA-L: The Future and Pain: More Reflections on IA

I'm Benette and i'm working for an eSolutions company called Asia Online.
There seems to be a confusion on what iA is here in our company.  Some say the wireframes encompass:
        1. Inventory: All elements present should be accounted for
        2. Weight: The percentage of prominence each element has on the page.
        3. Layout: especially when determining navigational placement and form fields
        4. Visual tools: placement of photos and the like
Arguments started on whether iA is stifling creativity among the designers.
And I don't think we have the monopoly on all design execution ideas though a
number of iAs have design backgrounds.  I was wondering if anybody could
throw in their opinions so I would know if its just the designer in me that's rebelling?
We call our team the Definition Team and we have the the following people in our group:
        web strat, iA persons
        Creative Director
        Content editor/writer
        Designer
We do industry & competetive research, web strategy, iA, task analysis, user scanarios,
creative direction and functional specifications documents.

-----Original Message-----
From: Peter Merholz [mailto:peterme@peterme.com]
Sent: Wednesday, February 28, 2001 12:20 AM
To: sigia-l@asis.org
Subject: SIGIA-L: The Future and Pain: More Reflections on IA


Hey all--

I've finally written down all my notes from the Reflections and Projections
Panel from the ASIS Summit.

You can start here:
http://www.peterme.com/asis/2001summit_intro.html

Or, just read the most recent entries
The Future of Information Architecture
http://www.peterme.com/asis/2001summit_future.html

Pain
http://www.peterme.com/asis/2001summit_pain.html

The Outline, such as it is, of the notes is:
1.  Intro
2.  Trends
- Bottom-up
- It's The Content, Stupid
- Models in Design
- Working with Clients, Not At Them
3.  Future of Information Architecture
- The Spread of "Good IA"
- Data Analysis
- IA Playing Nice in the Sandbox
- Library Science Impacts Agency Information Architecture
- Data-Driven Information Architecture
- Professional Affiliations for Information Architecture
- Further Specialization
4.   Pain
- Business Savvy
- Ill-defined Roles and Responsibilities

I'd love your feedback.

--peter

===========================================================================
List archives are available at:
http://www.listquest.com/computers/tier2/computer_misc.html
--------------------------------------------------------------------------
To subscribe or unsubscribe, send mail to majordomo@asis.org with the
appropriate command from the list below in the body of the message:
subscribe sigia-l
subscribe sigia-l-digest
unsubscribe sigia-l
unsubscribe sigia-l-digest