We don' need no stinkin' taxonomy

I come to the ExpertExperience community as a taxonomy guru.  Why are taxonomies important to DAM projects?  A taxonomy is the core organizing principle that allows the DAM to present content to users in the context of their task and particular requirements.  We'll get into the details of how this happens in future posts.  In this first post, I'll review some of the common questions I'm asked.

Having created taxonomies for organizations of all sizes for the past 15 years, I have seen a variety of technology trends come and go and have some thoughts about the current state of taxonomy maturity that I'd like to share.  Here several bone headed questions that I have heard:

1. Our CEO says we need a taxonomy.  It's really important to the organization. What's a taxonomy anyway?
2. We did a taxonomy last year - so we're all set, right? 
3. Taxonomy? That's so 90's. We need a folksonomy. (or 3a. Taxonomy? That's so 90's. We need an ontology.)
4. Our data people are in charge of the taxonomy, you have a problem with that?
5. Can't we buy a taxonomy?
6. Taxonomies are difficult, why don't we just get Google?
7. Can you come in this week and "do" our taxonomy?
8. Can't our advertising agency provide the taxonomy along with the site branding project? They say they can...
9. We need a five level deep taxonomy... or should it be six?
10. You're the expert, why can't you tell us what the taxonomy is supposed to be?

There are many things wrong with each of these.  I am sure some of you are smiling and shaking your heads.  In future posts, we'll address many operational and strategic issues around taxonomy management and development as it applies to DAM projects.

Which of these 10 issues most resonate with your situation or experience?  What would you like to add to the list?  You can write me at seth@earley.com or post a comment here.