Knowledge Management Spotlight: Accenture Shows Why KM Taxonomy Is Critical
Based on APQC's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Taxonomy success depends on securing the right sponsorship and involving business stakeholders and end users when defining terms and classifications.
Briefing
Accenture’s Sue Pacus says the biggest reason knowledge management teams struggle to get a taxonomy right is not the mechanics of categorization—it’s missing the right sponsorship and the right business people from the start. When KM teams try to define terms and classifications without involving the business and end users, the result often fails its real purpose: giving people context so they can find content through both search and browse.
Pacus links “business relevance” to practical usability. A taxonomy has to reflect how users actually look for information, and it can’t be over-engineered into a maze of categories. Too much complexity discourages contribution and tagging—people won’t spend time submitting content if they can’t figure out where it belongs. The fix is to make tradeoffs early and keep the structure understandable enough that users will participate.
Signs of a taxonomy going off track show up quickly once it’s in use. Pacus points to the need for iterative testing such as card sorting to see whether users group information the same way the taxonomy intends. After launch, teams should watch for frustration with search (people still can’t find what they need) and for low contribution rates. Tagging behavior also acts like a diagnostic: if users don’t understand how to tag, or if they “over-tag” by assigning content to multiple categories because they can’t tell where it fits, the taxonomy likely isn’t aligned with user expectations.
Standardizing vocabulary is another recurring challenge, especially inside large enterprises where geography or business units develop their own preferred terms. Reaching agreement can turn into “duking it out,” but the payoff is cross-unit reuse—content from another region or business unit becomes findable when everyone uses consistent terms. Pacus recommends monitoring usage over time to detect vocabulary problems: if newly allowed terms don’t show up in common search behavior or aren’t used for tagging, they’re probably not the right terms and should be cleaned up.
Education and motivation for stakeholders are treated as equally important. Pacus argues that executives and sponsors respond better when KM value is translated into familiar, everyday examples—citing Amazon, Netflix, and Pandora—to make the business case for better search, faster filtering, and quicker path-to-answer. Ultimately, the taxonomy’s value is measured in time and cost savings, and in preventing “reinvention” when frustrated users build new content storage or workflows instead of leveraging what already exists.
In a cost-pressured consulting environment, Pacus frames taxonomy as a performance enabler: when people can find prior work, teams build on existing ideas rather than starting from scratch, improving both solution quality and innovation velocity. The core message is straightforward—taxonomy success depends on business alignment, user testing, and ongoing adjustment, not on getting the structure perfect in a one-time planning session.
Cornell Notes
Accenture’s Sue Pacus says taxonomy failures usually stem from governance gaps: KM teams define terms without enough business sponsorship and end-user input. A taxonomy must be business-relevant and understandable enough that users can search, browse, and tag content without friction. Success requires iterative validation (including card sorting) and ongoing monitoring after launch—watching for search frustration, low contribution rates, and confusing tagging patterns like over-tagging. Standardizing vocabulary is hard across silos, but usage data over time can reveal which terms users actually adopt, guiding cleanup. When taxonomy works, organizations save time and money by reducing reinvention and enabling teams to build on existing knowledge.
Why does taxonomy often fail when KM teams “just set it up” internally?
What does “business relevance” look like in practice, and how can teams avoid overcomplicating it?
What early and post-launch signals indicate the taxonomy is off track?
How do organizations detect whether a standard vocabulary is actually working across silos?
How should KM leaders educate stakeholders and motivate adoption?
Why does taxonomy quality affect innovation and cost in consulting and other industries?
Review Questions
- What specific user behaviors (search and tagging) indicate a taxonomy may not be business-relevant?
- How does card sorting function as a validation method for taxonomy design?
- Why can standardizing vocabulary across business units be contentious, and what data can resolve the disagreement?
Key Points
- 1
Taxonomy success depends on securing the right sponsorship and involving business stakeholders and end users when defining terms and classifications.
- 2
Classification must be designed for findability through both search and browse, because it ultimately provides context for users.
- 3
Iterative testing—such as card sorting—helps validate whether users categorize information the same way the taxonomy intends.
- 4
After launch, monitor search frustration, contribution rates, and tagging behavior (including over-tagging) to detect misalignment quickly.
- 5
Standardizing vocabulary across silos is difficult, but usage over time can reveal which terms users actually adopt for searching and tagging.
- 6
Translate taxonomy value into executive-friendly outcomes like saving time and money, using familiar examples to make the benefits concrete.
- 7
Good taxonomy reduces reinvention and helps teams innovate by building on prior work instead of starting from scratch.