[Sigia-l] The value of an IA

[Patrick Neeman]

This is something I've seen in certain situations. And I agree with  
you - it should be an integration, because by the time an IA does get  
brought in, the client realizes need the IA to increase profitablity  
(or reduce losses), and the first words out of the IA's mouth are  
sometimes "reduce the advertising on the page, it's not good for the  
user".

Part of the issue also is where most IAs (and QA) are brought in the  
process -- usually too late to be effective. Software developers are  
positioned to come in early when they should be brought in later  
(like after figuring out what exactly is going to be built, then they  
can advise on solutions). Most of the time IAs and QA are brought in  
late, affecting the quality of site/software. What IAs do should be  
built in the process, and that currently doesn't happen. If IAs are  
brought in earlier, maybe 75 percent of all projects wouldn't fail.

(And don't get me going on the topic of incompetent consultants).

P@

On Jan 26, 2006, at 2:55 PM, Listera wrote:

> Patrick Neeman:
>
>> the job of Information Architect is to defend the user
>
> As you note, this has been one of the urban myths most detrimental  
> to the
> discipline: it ceded (the integration of) business strategy to  
> "others"
> thereby forever relegating IA to secondary class in corporate  
> pecking order.
>
> I never tire of saying here that there's nobody better at balancing  
> the
> needs of the client and the user than the Designer. Whenever we aim  
> for
> anything less we are implicitly accepting to become a plaything for  
> those
> who "defend the business."
>
> ----
> Ziya
>
> I'm a Designer: I Solve Problems
>