When we say "information architecture," we
mean a definition of the different items of information, how the
items are connected to each other and where they are located (hierarchically
and visually) relative to each other. A product's information
architecture serves as the blueprint that directs the allocation
of functions and data within the product. Like the floorplan for
a house, the information architecture dictates which functions
will be grouped together and how those functions will act on the
elements of data used to construct the product.
It is very important to get the information architecture right
at the beginning of the product development cycle. As when building
a house, it is fairly easy to change the blueprint before construction
begins; but it's often not economically or structurally feasible
to make significant changes once the building is well underway.
Making major corrections to the information architecture late
in the development cycle is akin to deciding to move the kitchen
to the opposite side after the framing has already been completed
for the whole house.
