![[The IA Domain.jpeg]] This graphic shows the various domains in which information architects practice. In it, one can see four areas of responsibility stacked like layers. [^1] The bottom layer is the realm of business. This layer is where a business is created and managed. The core idea of the business, the way it makes money, and the way it identifies and speaks to its end users is all generated in this layer. The next layer up is technology. This is where all the hardware and software that represents the business is created and maintained. Databases, CRMs, CMSs, PIMs, DAMs, and so forth live in this layer. The next layer is the interaction layer. This is where the work goes on to translate the business's aims – as moderated by the technology layer – into software and experiences that an end user will encounter. The top layer is the experience layer. Here is where an actor (aka end user) in an information system lives their life. An actor in this realm will develop information needs that may bring them to intersect with the interaction layer of the business. The actor's unique filters, such as their domain or technology expertise, will impact how they behave in the interaction layer. Information Architects are the rare role in an organization that must have competence at every layer in order to maximize their impact on the business. IAs must understand the business strategy and end goals of the organization, how information is structured and managed in the technology layer, how interaction design needs information to be structured in order to deliver experiences, and how end users encounter and use information. --- **Relates to**: [[information architecture|IA]] [^1]: Thanks to [[Bob Royce]] for his contribution of the business domain to this model.