Wednesday, January 9, 2008

What is an Information Architect? - Part 2

What is Information Architecture? - Part 2

There are really two questions here.


A. What is an Information Architect?

B. What does an Information Architect do?


A. An Information Architect can be any number of different linked or unlinked things just like any other person. However the elements of knowledge and experience of an Information Architect define what they can do.


B. What an Information Architect does is not unlike an Architect who builds a building.



  • An Information Architect creates a concept, defines a structure and progression.

  • Information Architects recognise other influences from technologies, incumbent systems and vendors.

  • Information Architects carry out location, community, sector, market and business research to find best practice and where there is none they define it.

  • Information Architects make a space for their clients and the client’s user audience to interact through information, activity or product transfer.

  • Information Architects simplify or reinterpret existing complex systems to ease the flow of interactions on existing systems, or they create new interactions that support audience goals.

  • Information Architects help clients to respond to the changing needs of their audience so that the client maintains a responsive relationship.


So to really understand what an Information Architect is, I'm going to have to try and define what makes up knowledge elements and experience elements in Information Architecture.

No comments: