A misconception about information architecture is that it can only solve deep, systemic problems. We used to call this "Big IA".
The industry has forgotten that IA plays a role in day-to-day design decisions, too. What we used to call "Little IA."
What's a little IA problem you've faced recently?
The industry has forgotten that IA plays a role in day-to-day design decisions, too. What we used to call "Little IA."
What's a little IA problem you've faced recently?
Comments
With that said, when I read posts or talk to people who are or were information architects, they mostly talk about big IA.
1. Everyone thinks strategy is the cool thing to work on.
2. Big IA challenges may make better stories that can be abstracted to protect IP.
3. Little IA challenges are so specific and nuanced they may be difficult to talk about meaningfully.