Information Architect

Your day involves a blend of research and design. You might spend the morning conducting a card sort or tree test to understand how users expect content to be organized, then create a sitemap, navigation model, or taxonomy for a product redesign. You're thinking about categorization, labeling, search behavior, and how people build mental models of information spaces.

Collaboration with UX designers, content strategists, and developers is constant. You're providing the structural foundation that visual designers and developers build on. This means your work happens early in the design process, and changes to IA later can be expensive. Getting stakeholders to invest in IA upfront — before it's clear what the benefit will be — requires demonstrating value through research and clear rationale.

People who tend to thrive here are systems thinkers who love organizing complexity. If you genuinely enjoy creating taxonomies, defining metadata schemas, and testing whether navigation makes sense, the work is deeply satisfying. If you prefer visual design or coding over the structural and organizational layer, the abstract nature of IA can feel disconnected from the final product.