The term “information architecture” is usually a reference to the structure of information that supports a web site. This is a very restricted definition for such a broad term. In this blog we talk about information architecture in a much broader sense, for example
- how a company should manage the large variety of information that it generates on a daily basis
- how people within the company should access the information repositories
- how information assets evolve over time
- how to structure the data to minimize the overhead associated with having different versions of the same information sprinkled throughout the repository
- how information should be presented on the internet to support web services
- the differences between software configuration management, requirements management and enterprise content management
- assisted data access (software agents)
- assisted data management
… and so on. Follow this blog if you want to minimize ongoing information management overhead and make relevant information more readily available to users.