How often have you found yourself on an ill-defined site redesign project? You know, the ones that you end up redesigning and restructuring every few years as you add new content. Or perhaps you spin up a new microsite because the new product/solution doesn’t fit in with the current structure, not because you want to create a new experience around it. Maybe your site has vaguely labelled navigation buckets like “More Magic”—which is essentially your junk drawer, your “everything else.”
Your top concerns on such projects are:
- You can’t find anything.
- Your users can’t find anything.
- The navigation isn’t consistent.
- You have too much content.
Your hopeful answer to everything is to rely on an external search engine, not the one that’s on your site. Google will find everything for you.
A typical site redesign project might include refreshing the visual design, considering the best interaction practices, and conducting usability testing. But what’s missing? Creating the taxonomy.
“Taxonomy is just tagging, right? Sharepoint/AEM has it—we’re covered!”
In the coming months, I will be exploring the what, why, and how of taxonomy planning, design, and implementation:
- Building the business case for taxonomy
- Planning a taxonomy
- The many facets of taxonomy
- Card sorting
- Tree testing
- Taxonomy governance
- Best practices of enterprise taxonomies
Are you ready?