Olivier Travers

Free cash flow for the win
Home > Archives > 2002 > July > 17 > Information architecture concepts: Misconceptions explained
Information architecture concepts: Misconceptions explained

IBM:

"The best time to use an information architect is at the very beginning of the development effort. Just as you wouldn't call a real architect to a building site just as the roof is being placed on rickety walls, it's generally a good idea to call in an expert before running into trouble with a Web site. [...] An information architect's main concern is to build information structures that are easy to comprehend and use. To do this, he must align the goals of the business with the goals of the users, and at the same time work within the constraints posed by the project (deadlines, resources, budget, etc.), technical issues (choice of development language, database, etc.), and content production (staffing, depth of in-house/freelance talent, etc.)."

Post a comment






Remember personal info?
Your e-mail address is used to send you future comments to this entry, but I won't use it for any other purpose and it won't appear on the site. I prefer you comment using your real identity, thanks.
Email this Story to a Friend




This form is used only to email this story to your friend. I won't save the email addresses you type in, or use them in the future in any way.


About
Contact



Web Feed

Powered by Movable Type

My profiles: