The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
Information Architect (L2)
2-3 years at L2Skills to master
- Independently owning IA for specific product features, proving your ability to deliver clear sitemaps and content models, and consistently applying user research methods.
You're ready to move on when
- Consistently delivers high-quality IA artefacts for medium-complexity projects without significant supervision.
- Proactively identifies and proposes solutions for information organisation challenges.
- Demonstrates strong communication skills when explaining IA concepts to cross-functional teams.
- Has successfully led at least one end-to-end IA project from research to implementation.
- 2
UX Designer with IA Focus
3-5 years in UX designSkills to master
- Deepening your understanding of content modelling and taxonomy design, leading user research specifically for information architecture, and demonstrating strong systems thinking beyond just UI design.
You're ready to move on when
- Has consistently taken ownership of information architecture within UX projects, not just visual design.
- Can articulate the rationale behind information structures based on user mental models and business needs.
- Has experience with tools like Optimal Workshop for card sorting/tree testing.
- Shows a strong interest in the 'behind-the-scenes' structure of information, not just the front-end experience.
- 3
Content Strategist (with Technical IA Focus)
4-6 years in content strategySkills to master
- Moving beyond content creation and governance to technical content modelling, metadata strategy, and understanding the implications of headless CMS architectures. You'll need to get comfortable with more technical IA tools.
You're ready to move on when
- Has experience defining content types and attributes, not just writing content.
- Understands the principles of structured content and content reuse.
- Has worked closely with development teams on content implementation.
- Shows a strong desire to formalise content structures and metadata at a systemic level.