What does an information architect actually do?
Diana Payton interviewed me for the Technical Writing Uncensored YouTube channel.
In this episode of Technical Writing Uncensored, we break down the real role of information architecture in modern digital products—from documentation to apps to full product experiences. We discussed:
- What information architecture really is (beyond documentation)
- Why “adding more content” is often the wrong solution
- The difference between front-end vs back-end IA
- How poor navigation and labeling hurt user experience
- The role of analytics, user research, and testing in IA
- Common mistakes companies make (and how to fix them)
- How IA overlaps with technical writing, UX, and product design
I also shared my workflow, how I work with cross-functional teams, and why reducing cognitive load is one of the most important (and overlooked) goals in product content.
Thank you Diana for a lovely in-depth conversation about all things IA!
Borrowing from Technical Writing Uncensored’s LinkedIn, I’ll wrap up with some of their favorite takeaways from the interview.
“If users can’t find what they need, it doesn’t matter how fast, secure, or polished your product is, then they leave.”
“Most teams think their problem is design.
It’s not.
It’s structure.”
