As an interaction designer, I have participated in the process of Informational Architecture. For example, I have used task and user flows, concept and site maps to organize content and user stories. Design-wise, I have use wireframes to organize this content visually and hierarchical. This back-end design ensures that users will effectively be able to interact with the product, resolve their problems, and even get them to your end goal. Sometimes there can be too much complicated content to effectively organize it.
I recently used Autodesk’s Fusion 360 to create a mouse prototype for one of my projects and oh boy; it was super complicated! There were so many tools, menus, errors, etc., and no real way to find a solution unless you Google it. Though, it was my first time using the program. Professionals and people who have been using it for a while now probably do not have the same difficulties navigating through the software as I did. Maybe it was not a problem with information architecture.
A difference between informational architecture and interaction design is that IA concentrates more on the information and its organization, while IxD focuses on the most effective way for users to experience the system or product. Both of these are crucial for the success of a product. An interaction designer needs organized information during the design process. Additionally, when understanding a user’s needs, the way content is organized—both information and interactional—can change the direction.
Oh yeah! I just realized all these tools software have so many IA within them!