April 17, 2012 - 4:58 GMT
I was very pleased to receive the following notes from a participant in one of my recent SharePoint IA courses.
“This workshop is powerful and more than meets my expectations! I wasn't sure if I should attend as I'm not a technical person, but am a member of the IT project team. It is immediately applicable to my job. I plan to share the information with the project team when I return to the office… I have already gained some excellent tools to work with each of the businesses as we migrate them to SharePoint 2010. “
This was wonderful feedback and it prodded me to try to distill what it was that attendees valued about the course.
This class pulls together a number of principles around information management strategy, process analysis, user research and taxonomy to guide development of key information architecture constructs in SharePoint. All fine and good, but similar to standard IA approaches and not terribly exciting . Describing the course curriculum doesn’t really communicate the value that students take away from the class. So, I spent some time trying to think through the situations in which I have seen light bulbs go on.
It’s in the structure of interactive exercises. Students are given seemingly simple problems to solve, yet they yield deep insights. Take a simple exercise around term derivation. (Used for populating the SharePoint term store.)
April 17, 2012 - 4:58 GMT
I was very pleased to receive the following notes from a participant in one of my recent SharePoint IA courses.
“This workshop is powerful and more than meets my expectations! I wasn't sure if I should attend as I'm not a technical person, but am a member of the IT project team. It is immediately applicable to my job. I plan to share the information with the project team when I return to the office… I have already gained some excellent tools to work with each of the businesses as we migrate them to SharePoint 2010. “
This was wonderful feedback and it prodded me to try to distill what it was that attendees valued about the course.
This class pulls together a number of principles around information management strategy, process analysis, user research and taxonomy to guide development of key information architecture constructs in SharePoint. All fine and good, but similar to standard IA approaches and not terribly exciting . Describing the course curriculum doesn’t really communicate the value that students take away from the class. So, I spent some time trying to think through the situations in which I have seen light bulbs go on.
It’s in the structure of interactive exercises. Students are given seemingly simple problems to solve, yet they yield deep insights. Take a simple exercise around term derivation. (Used for populating the SharePoint term store.)
March 28, 2012 - 10:36 GMT
I recently taught the Information Architecture for SharePoint class in Chicago. Each time I teach this class, I gain more insights into how SharePoint content needs to be organized. This last time, I had some new thoughts on how to consider a site map.
March 28, 2012 - 10:36 GMT
I recently taught the Information Architecture for SharePoint class in Chicago. Each time I teach this class, I gain more insights into how SharePoint content needs to be organized. This last time, I had some new thoughts on how to consider a site map.
March 19, 2012 - 3:13 GMT
We hear it more and more – managing non-text (digital) assets along with textual content in the context of business systems and processes is challenging. What are we hearing and where are the challenges coming from?
February 29, 2012 - 1:00 GMT
I really enjoy teaching our new workshop on SharePoint Information Architecture (IA). There is nothing like teaching to further one’s own knowledge. The classes attract a diverse range of students. Some come knowing little about SharePoint or IA; others have expertise in either SharePoint or IA. The mix of knowledge in the class brings a wide range of issues to discussions and the class-dynamics and interaction lead to valuable new insights into SharePoint design, development and adoption.
December 15, 2011 - 11:43 GMT
SharePoint taxonomies are new and exciting. For the first time a widely adopted content management tool can manage and leverage taxonomies and provide for some semblance of vocabulary control.
December 15, 2011 - 10:56 GMT
This is a continuation of last month's post: What You Need to Know to End Information Chaos.
Business makes extensive use of taxonomy and metadata in a variety of scenarios including accounting, databases and inter/intra-net based applications to provide structure and organize information. All this is normal and straightforward. Chaos arises, however, when a business manager or executive asks questions that cut-across systems. When, for example, they want to be able to integrate engineering data, customer-oriented product information, customer information, and customer service complaints to identify new product-lines and solution opportunities.
To achieve the goal of visualizing a business problem by mining information repositories in a creative way to address complex issues involving multiple data repositories, taxonomies and metadata must be aligned to establish a comprehensive "single source of truth." The concept of a single source of truth is the mantra in the drive to put Master Data Management (MDM) into practice. However, the effort comes with certain practical and serious challenges. The most significant being the fact that different and well-governed information systems have different semantics and different metadata standards. Achieving semantic interoperability is a serious challenge, especially as business systems and network service architectures develop to meet organizational needs to adapt to a rapidly changing technology environment.
So what to do? How do organizations find ways to capture, manage, and derive understanding from a wide range of sources including its internal expertise resources and the stream of information provided by social media channels?
December 15, 2011 - 10:56 GMT
This is a continuation of last month's post: What You Need to Know to End Information Chaos.
Business makes extensive use of taxonomy and metadata in a variety of scenarios including accounting, databases and inter/intra-net based applications to provide structure and organize information. All this is normal and straightforward. Chaos arises, however, when a business manager or executive asks questions that cut-across systems. When, for example, they want to be able to integrate engineering data, customer-oriented product information, customer information, and customer service complaints to identify new product-lines and solution opportunities.
To achieve the goal of visualizing a business problem by mining information repositories in a creative way to address complex issues involving multiple data repositories, taxonomies and metadata must be aligned to establish a comprehensive "single source of truth." The concept of a single source of truth is the mantra in the drive to put Master Data Management (MDM) into practice. However, the effort comes with certain practical and serious challenges. The most significant being the fact that different and well-governed information systems have different semantics and different metadata standards. Achieving semantic interoperability is a serious challenge, especially as business systems and network service architectures develop to meet organizational needs to adapt to a rapidly changing technology environment.
So what to do? How do organizations find ways to capture, manage, and derive understanding from a wide range of sources including its internal expertise resources and the stream of information provided by social media channels?
November 15, 2011 - 8:50 GMT
Part 1: Metadata governance, standards, and maturity
Clients I work with struggle with many issues. Among these, two often rise to the top.
- How do we show the impact of metadata on our business?
- Do we need our own metadata standard? Alternatively, should we use industry standards?
This blog covers my approach to answering these questions.
To begin with, I ask them how they define metadata. And most often, they give me the usual tautology: metadata is data about data. You can do better than that! A more meaningful alternative is to say that metadata is what allows data to be searched, understood, and consistently used within a company.
Metadata provides data with a context that enables users to think about and share data in useful ways. In short, metadata transforms data into information. It enables a complex organization to make informed decisions and take appropriate actions because we can look at our collective experience through a common framework of understanding.

The intellectual endeavor of managing "metadata" is at the core of all information and knowledge related work. Taxonomy is dedicated to the practice of producing logical categorization models, and therefore at the very heart of creating metadata systems. Human-understandable taxonomies provide the words and relationships needed to access and use information.
October 24, 2011 - 3:29 GMT
[This post originally appeared on DigitalLandfill.com on August 25, 2011. It has also been included in AIIM's Governance in SharePoint Toolkit which is available free to Professional Members or $99 to others. Use coupon code PROMEMX2 to extend your membership through December 2012 when you upgrade to Professional for $139.]
Many organizations are finding that leveraging the full suite of capabilities SharePoint offers requires introduction of a new requirement – that of dealing with, managing and exploiting taxonomies. Of course taxonomies are not new, but there is some confusion about where managed metadata services and the term store end and true taxonomy management begins. There are also some misconceptions about the process of deriving and applying taxonomies in SharePoint. The following are five areas of confusion that we have seen in our engagements and research.
October 18, 2011 - 12:04 GMT
How can you tell the difference between an introverted records manager and an extroverted records manager? The extrovert stares at your shoes when they talk to you.
That’s actually an old accounting joke and the subtext here is that records managers are boring because records management is boring. The last thing that people doing cool knowledge management, dynamic content, or search projects want to consider is records processes. Boring!
The topic brings to mind the old days of file rooms and file clerks. But these are not the old days and there are reasons now for all information management professionals to care about RM. Records are created by everyone, everywhere, on all kinds of devices. A record can be anything that is used in the course of executing a transaction, performing day to day work tasks or that is created in support of a transaction. That means that we are all creating records. Records processes are distributed and ad hoc and in most organizations not well managed due to the fact that evolution of technology has happened more quickly than processes can keep up with.
Here are five reasons why you need to adopt a records management perspective:
October 14, 2011 - 3:24 GMT
As someone whose primary business assets are often intangible or abstract, like models and processes, it’s rather obvious that visualization techniques are important. Without maps, charts, lists, and illustrations, it can be very difficult to capture critical ideas, let alone communicate them with others. And I’ve seen many great examples of visualization in the last few weeks, thanks to the many like-minded individuals who tweet and retweet links to these examples. Some recent infographic favorites include:
Twiterize Yourself
Patent Evil
Is it Really Green?
As helpful as visualizations can be, however, they’re not always the most impactful. Even with training and experience, it is really hard to browse a taxonomy tree, read a map, interpret blueprints, and understand a complex graph or a series of graphs. Informational visualizations still require a level of interpretation that makes an immediate, intuitive, and even emotional response impossible. Compare how much more change is effected by experiencing a physical car crash than by a poster on safe automobile handling; by bumping your head than by noticing the yellow warning stripe; by suffering a baby’s cry than by … well, just about anything. In fact, the screaming wail of an infant human is hardwired into our brains as a call for action.
September 22, 2011 - 8:02 GMT
I recently taught the four day Information Organization and Access course. I enjoy teaching and it’s a great way for me to stay connected with customer projects and stay fresh.
Interestingly at the end of the second day, one of the attendees complained that the course was too theoretical and not sufficiently practical. I was incredulous at this statement and was so shocked I did not know what to say in response. Not practical? This is what we do for our clients. How could it not be practical?
But rather than get defensive or write this individual off as an anomaly (I had not ever heard anyone say this before), I decided to find out what would make class more practical. I asked each person to write down what they expected to learn that they had not. What was going to make this practical?
The results were interesting indeed. I had covered every topic they mentioned, many with examples. So what was missing? They wanted the class tailored to their problems. It would also be nice to have one of the client taxonomy frameworks I showed as an example to build on. Basically it would be great if they could come in and solve their taxonomy, metadata and IA problems in the four days.
It would be great if we could do that but as we reflected on these ideas it became clear that it really was not practical to do this in a public class. As we discussed the details, we could see that we did in fact cover most of the components that they were mentioning. The reason for the first comment about theory was simply this: I had overloaded them with information with no clear plan of attack. They did not see how to organize the content into a practical set of steps to apply to their own situation.
August 22, 2011 - 4:52 GMT
The heart of Web 3.0 is semantics. Semantics focuses on what one means to say, not just what one actually says. Semantics is the difference between salient search results and an unfocused aggregation of … stuff. Algorithms used by search engines are an effort to discern the meaning and rank relevance against users short, ambiguous, approximation of intent expressed in their search queries. Web 3.0 semantics represents a significant advance over current search technologies because it attempts to look at meaning inherent in the content itself.
To understand how this works and the role taxonomy plays in this search for meaning a little review maybe helpful. Taxonomy categorizes information into a unified structure and controls the language to describe those categories. Under this definition, the contributions of taxonomy are labeling, designing content, providing navigation patterns, and managing the relationship among content units. These roles for taxonomy are essential to successful site development, especially as sites are increasingly dynamic, drawing content directly out of content management systems, and increasingly socialized to the point that systems rooted in databases are no longer able to scale to meet the storage demands.
Taxonomy is an integral part of a content producer's tools kit for adding metadata to their site. Metadata presents an interpretive model for understanding content data, or the types of data actually evaluated by search engine algorithms.
August 22, 2011 - 4:52 GMT
The heart of Web 3.0 is semantics. Semantics focuses on what one means to say, not just what one actually says. Semantics is the difference between salient search results and an unfocused aggregation of … stuff. Algorithms used by search engines are an effort to discern the meaning and rank relevance against users short, ambiguous, approximation of intent expressed in their search queries. Web 3.0 semantics represents a significant advance over current search technologies because it attempts to look at meaning inherent in the content itself.
To understand how this works and the role taxonomy plays in this search for meaning a little review maybe helpful. Taxonomy categorizes information into a unified structure and controls the language to describe those categories. Under this definition, the contributions of taxonomy are labeling, designing content, providing navigation patterns, and managing the relationship among content units. These roles for taxonomy are essential to successful site development, especially as sites are increasingly dynamic, drawing content directly out of content management systems, and increasingly socialized to the point that systems rooted in databases are no longer able to scale to meet the storage demands.
Taxonomy is an integral part of a content producer's tools kit for adding metadata to their site. Metadata presents an interpretive model for understanding content data, or the types of data actually evaluated by search engine algorithms.
August 12, 2011 - 4:35 GMT
Earley & Associates recently announced a webinar series on Content in Context: Why Dynamic Content and Content Choreography is Critical to Information Management. Since you may be asking yourself, “what is content choreography?” we thought we’d share the history of the term and what we mean by it.
Back in March of 2011, a major global high tech company engaged Earley & Associates to work on the redesign of a major website, site search, metadata and all new web CMS and DAM infrastructure. It was an enormous undertaking, headed by Marketing and involving brand managers, the SEO team, content authors, creative agencies, a systems integrator, a user experience design agency, technical consultants, and the IT department. The existing sites were to migrate from traditional navigation, search and single page content to a totally new paradigm of dynamic content collections, where user context would be driven by the search experience more than by navigation or site depth. With personalization. And in multiple languages. Taxonomy and metadata would play an important role in each of these areas, but just how well the whole system was going to hang together (“If we do not hang together, we shall all hang separately...”) was a real concern, and the very reason we’d been called in as a sort of SWAT team.
July 11, 2011 - 12:35 GMT
"You ain't seen nothin' yet." So says an IDC report on the growth of information. The statistics cited by IDC included voice, radio, print and TV as they transition to digital formats. The number? 35 trillion gigabytes. That's 35 exabytes. An Exabyte being one thousand billion billion. But, how much, exactly, is 'too much' information? Is there really such a thing?
Consider that back in the 16th century, around the time when the printing press was invented, the world was undergoing an information explosion. People wondered, how could anyone possibly read all of those books? It was quickly determined that we didn't need to read all the books and what was needed was simply an index of all the available books. This evolved into today's library system where all books are accessible--if and when needed.
This so-called "information overload" problem will be solved in the same way - by creating lists, classification structures, bibliographies, reference materials and all sorts of dynamic, curated content. The best web sites have the capability of anticipating what users need and assembling that content dynamically - something we refer to as Content Choreography™ - the ability to coordinate, weave and present content into new information products and services based on the needs of a diverse set of users all operating on the site at the same time. And of course, to combine, curate, and choreograph content effectively requires metadata, taxonomies, consistent organizing principles tuned to audience, task and problem.
April 20, 2011 - 4:43 GMT
I just returned from the Sentiment Analysis Symposium, recently held in NYC where I presented a short talk on the role of taxonomy in social media. This conference focuses on solutions that discover business value in opinions and attitudes in social media, news, and enterprise feedback. I used my Blackberry to tweet ideas in real time during the session (hash tag SAS11).
This combination of immediacy and mobility has interesting implications for business. Consumers are connected to the feedback and opinion of others and are increasingly using their devices to research products and services through multiple mechanisms.
We'll be addressing aspects of this in our session this week on "Optimizing the Information Supply Chain for Competitive Advantage" where we will discuss how optimized supply chains, cross channel shopping and mobile commerce will require integrated taxonomies and metadata.
Healthcare and Electronic Health Records is the topic of a two part call we are presenting in May. This is another area where the development of systems that can provide immediate and accurate information about patient health will depend on taxonomies. Patient safety data, evidence based medicine and integration of diagnostic and patient management systems along with a range of other methods to improve quality and control costs will require harmonization of complex healthcare and life sciences information sources.
April 15, 2011 - 12:18 GMT
In online retailing the only opportunity is the information-based opportunity. In this post I want to talk about that bold statement.
Selling online is dependent upon information. Without information for the customer to process it is essentially impossible to sell online. It is true that selling online is not all about information. Brand and product selection, pricing (which is both information and a retailer choice), availability and quality of fulfillment, to name a few parameters, all count for the customer. But in online retailing information is the customer experience. It is crucial to understand that not all information for your products and customers is equal in terms of you touching and then leading your customers to the point of sale.
Standards and Uniqueness
In terms of using information effectively, we can see selling online as a play between two competing yet also complementary momentums. Between leveraging industry information standards – to gain efficiencies in time, resources and costs – and creating and then leveraging information uniqueness. There are many information standards for retailers to work with – for example those from The Association for Retail Technology Standards (ARTS). Standards are where you will share information values and models with your peers and competitors and use the same information in the same ways. There is nothing lost competitively, and much to be gained (and saved) with you and your competitors using exactly the same lists of geographic locations, components and variants of personal names, classifications of the same types of prices (list, regular, suggested) and so on.
March 31, 2011 - 3:14 GMT
We all know that taxonomy-based solutions are core and integral to creating business opportunities and solving business problems in our worlds of information. Yet, there are some areas that taxonomy cannot model, and so seemingly can be of no help whatsoever to some unlucky owners of certain business “problems”. For instance, organizing what we don’t know. That seems straightforward and uncontroversial. Surely we cannot organize what we don’t know?
And yet … undiscovered and/or so-far-unknown relevance hold value for the first discoverers. There are whole areas of business problems and opportunities hidden in discovery for litigation or in ultra-early stage science and research, to call out just two. So, logically, if topics and their unknown connections could be discovered on the emergent edge or in massive heterogeneous corpora or joined sets of documents – then taxonomy-based organization could be brought to bear, with all the attendant benefits we know of so well.
I had lunch recently with Jeff Bierach, VP of Sales for Sophia Search (http://www.sophiasearch.com/home), an early-stage start-up with buzz and promising solutions. Sophia Search – the “Search” part of the name is really a misnomer – do automatic clustering of documents into integral clusters that are relatively free of “noise” (bad cluster inclusion), have clean distinction between clusters and make relevant sense. And, they seem to do this very well, indeed.
February 15, 2011 - 11:43 GMT
I recently pulled out my yellowed copy of Michael Dertouzos’ 1995 What Will Be: How the New World of Information Will Change Our Lives. What I found interesting is how some of those predictions were spot on and some oddly naïve about just how much humans can change.
In “What Will Be” the term used to describe how people get their jobs done by leveraging various tools for managing documents and information was “Groupwork”. Today, we simply use content management applications to get our jobs done. See my recent blog, “This internet thing? It's gonna be BIG!” for more discussion on what will be, what is, and what is to come.
As I looked back over the last 15 years, I thought about the progress made in content management platforms; and the hype that accompanied each one. “Now, we will we have an end to information chaos! We can control what goes where and enable easy access!” Sadly, each new offering led to its own flavor of information chaos.
So is SharePoint 2010 the platform that will solve the problem? Or, will we find that information chaos is migrated along with content? It’s really up to you and your organization. The opportunity is there but don’t take it for granted.
As I talk to companies and other enterprises, I find that most fall into the same trap – they buy a tool, install it, roll it out and wait for their people to get more efficient and effective. They wait… and wait… and… Instead of things getting better, they actually can get worse.
Why is this, I asked myself. Here are the five things that came immediately to mind.
February 10, 2011 - 2:21 GMT
We’re several months into a large project implementing Oracle PDQ (Product Data Quality) for a major online retailer. This is the first of what will be several updates on what we expect to be an exciting and interesting journey going forward. I will start this series by providing a little background on the tool we are using (Oracle PDQ) as well as some key points that are driving this project.
First, let me begin by bringing readers up to speed on Oracle PDQ. This is a product (which consists of a number of integrated modules) that addresses ALL of the issues associated with the b2b and b2c content supply chain, including –
- cleansing content from suppliers – correcting “noisy” content by normalizing semantic variance - misspellings, truncations, abbreviations etc. - implementing editorial standards, and identifying missing content
- setting limits on numerical values for attribute values (e.g. a belt for men’s pants has a limit of 60”), recognizing numbers into types of numbers – is it a decimal, is it an integer, or can it be either - and enabling calculations
- recognizing products, their attributes and their attribute values – we do this through semantic pattern recognition
- organizing product content (i.e. taxonomy/hierarchy)
- defining a product and its associated attribute data (i.e. a node in the product taxonomy) and weighting the attributes
- outputting cleansed content for all customer touchpoints (web, POS, in-store, catalogues, direct mail etc.)
- mapping products to one or multiple taxonomies, including site taxonomies
Pretty heady stuff—and we are having some fun with it.
What Retailers Need (and why they need it)
November 04, 2010 - 9:07 GMT
This week I have had the privilege of teaching the information organization and access (AIIM IOA) course at a
combined meeting of the Joint Task Force North, The Dept of Homeland Security, The US Army North and the US Northern Command.
From the JTF site: “The Joint Task Force North http://www.jtfn.northcom.mil/ is the Department of Defense organization tasked to support our nation’s federal law enforcement agencies in the identification and interdiction of suspected transnational threats within and along the approaches to the continental United States. “
“Transnational threats are those activities conducted by individuals or groups that involve international terrorism, narcotrafficking, alien smuggling, weapons of mass destruction, and includes the delivery systems for such weapons that threaten the national security of the United States."
One of the primary goals of this mission is the capture and dissemination of knowledge throughout a network whose mission is the protection of the United States. I was told by the head of the knowledge management organization, Dr Rick Morris, that my contribution would go directly to improving the security of the country. I have to say that I am truly honored to be making such a contribution to our nation.
Also from the JTF site: “JTF North’s homeland security support role is articulated in its mission statement:
November 02, 2010 - 10:15 GMT
In an earlier blog, I introduced the term eTaxonomy. ETaxonomy represents “embedded taxonomies”. Many kinds of IT solutions rely on taxonomy as a core organizing principle (reference data, content object models, information architecture, metadata schemas, etc) as opposed to simply being a navigational construct. In this blog, I discuss applications of eTaxonomy from our recent client work. Of note are:
- Search
- Document and Records Management
- Content Management
- Digital Asset Management
- Ecommerce
- Marketing Campaign Management
Search
Search is about metadata. A search application “derives” metadata by creating an index of the content. The index is information about the content, i.e. metadata. The search tool uses the index to locate documents and pages. This “derived metadata” can be enriched by adding attributes or keywords with terms defined in a taxonomy. Taxonomy provides a hierarchical structure of controlled vocabulary terms. With this structure, search-enabled applications can present related concepts, broaden or narrow the search, and filter results based on “facets” or attributes. The use of related terms (developed with a “thesaurus” – taxonomy on steroids) provides tremendous power in search applications.
Document and Records Management
October 25, 2010 - 10:24 GMT
I speak to many CIO’s who think taxonomy is an arcane piece of library science. Haven’t they heard of eTaxonomy? Well, of course not. While we labor to embed taxonomies into technology solutions, vendors take the credit for their “highly configurable solutions.” The good but unrecognized work we do needs a 21st century name – hence eTaxonomy.
Etaxonomy is the art and science of integrating taxonomy into deployable IT solutions. Our professional community of taxonomy practitioners is getting sophisticated at this. The best web sites today achieve usability through dynamic content presentation enabled by taxonomy. New classes of solutions, such as Marketing Resource Management, get their power from hierarchical information models that integrate diverse information sources. And critical initiatives in healthcare, such as electronic patient records, leverage taxonomies for coding.
So taxonomy is not your father’s library science construct. It’s not a spreadsheet of terms. Rather, it’s about methodologies for enabling smart computing through the use of sophisticated semantic models. That’s what eTaxonomy is. So taxonomists of yore, start calling yourself eTaxonomists, and make sure your CIO knows about the secret sauce.
In future blogs, I will discuss eTaxonomy in different solution settings. I look forward to getting feedback on this concept and whether it will help you make your case to management. Also, check out our Insight Webinar Series for a deep dive into eTaxonomy solutions and approaches.
July 09, 2010 - 11:55 GMT
Clink, clink went two halves of a Japanese rifle shell case on my researcher's desk at the National Archives and Records Administration facility in College Park, Maryland. They fell from the envelope attached to a memorandum in the folder I took from the large, archival documents box belonging RG-319, Office of Assistant Secretary, Army Staff Operations. The memorandum discussed problems associated with placing Imperial Japanese Army rifles under U.S. Army control back into service as part of the mobilization effort in Japan in response to rising tensions on the Korean Peninsula between 1948 and 1950. It was a good plan except: 1) the parts of the Japanese rifles were hand-crafted by each soldier during final assembly at time of issue and were unique and therefore the guns lacked interchangeable replacement parts; 2) the shells were designed for the gun bore, and 3) the US military had no practical means to mass produce shells for these archaic weapons.
This story illustrates a number of important points. A theory requires supporting knowledge to establish its actual goodness. Knowledge is a work product that moves through an organization. The repository for a work product artifact can be in an unusual place. Navigating to that place requires both an external structure and a diligent, informed seeker. Once accessed, retrieval results may include both target and unanticipated, serendipitous materials.
June 22, 2010 - 12:45 GMT
Information professionals interested in taxonomies now have another conference, besides Information Today’s Taxonomy Boot Camp, that has numerous taxonomy sessions. This is the annual conference, usually in June, of the professional association SLA (Special Libraries Association). I attended this year’s conference for the first time, which was held in New Orleans, June 13-16, and was quite impressed with its taxonomy-focused sessions and networking opportunities.
Although there is no professional association dedicated just to taxonomists, the new Taxonomy Division of SLA has begun to change that. SLA is the leading international association of library and information professionals working corporate settings, government, nonprofits, and educational institutions with specialized research and information management needs. Until recently, its Knowledge Management Division came closest to serving the interests of taxonomists, but since August 2009, those engaged in taxonomy work now have their own group within the association. The SLA annual conference in June this year was thus the first that the Taxonomy Division was able to sponsor sessions, and it did in a big way. In the past, SLA included only a pre-conference workshop and perhaps a single session on taxonomies, but this time the two and a half days of regular sessions was filled with taxonomy-related programs in every time-slot and one time with conflicting taxonomy sessions.
March 05, 2010 - 7:41 GMT
Taxonomy consultants, such as those at Earley & Associates, may be the ones who develop a taxonomy for an organization, but the organization's own staff will ultimately be responsible for maintaining it, so the question arises what tool or tools should be used the maintain that taxonomy and perhaps further develop it. A taxonomy may be implemented in a CMS, in SharePoint, or with search (Google Search Appliance, FAST, etc.), but these systems do not have taxonomy management components.
An interest in taxonomy tools was evident by the number of chat-based questions that my colleague Seth Maislin and I received from participants in this week’s Taxonomy Community of Practice Call, Cross-Mapping Taxonomies, which we jointly presented. There is a need for tools that do more than merely enabling manual adding and deleting of terms. Mapping two taxonomies is something that only a few tools support, but there are many other day-to-day taxonomy management activities that also require specialized taxonomy management software.
This week several Earley & Associates consultants, including myself, participated in a special training on Smartlogic Ontology Manager, a good example of full-featured taxonomy management software. The question arises: is this taxonomy management or ontology management software?
If we look at competing software products, we see various designations:
December 01, 2009 - 10:15 GMT
Best Practice #3: Use concise and precise terminology.
As I've mentioned in previous best practices (#1 Less is more and #2 Grouping and chunking), a lot of these design principles apply to any navigational construct -- using concise and intuitive labeling seems like a no-brainer. Given the textually charged interface and the amount of thinking you are asking people to do to navigate your site, mega menus simply force you to follow these rules more strictly.
Hunting and pecking for the right label to click on in a mega menu is no small task, so you really need to avoid the 2 major categories of labeling problems:
1. Excessive length & concatenation:
When you're trying to cram 20+ links in a hover pane, every character counts. If you've got extraneous words in your labels that make your links harder to scan, or even worse cause wrapping (*gasp*), take out the scalpel and try some creative rewording or restructuring. Labels should be short, sweet and precise, leaving nothing to guessing. Call it what it is as simply as possible, don't try to be fancy - you'll just end up confusing users.
Additionally, avoid concatenating (joining) more than 2 items in one label. Laundry list labels (this, this, this & this) are much harder to scan, as you force the user to read all the way to the end before they can move on. We also recommend you avoid having too many concatenated items in one menu or group. Ampersand-farms can make a menu much harder to scan and it usually means that you have tried to put way too much in one category and need to think about restructuring.
Here's an example of some labelling that breaks these rules:
November 24, 2009 - 9:23 GMT
Subtitle: The Future of Taxonomy... Ad Nauseum
This year's Taxonomy Bootcamp conference was much like years prior: full of great information, knowledgeable speakers, and a ton of self-doubt/-defense/-definition. Which is ironic: professional organizers who struggle to classify themselves. There were at least 3 major sessions dealing with the taxonomist's identity and future (in a 2-day conference with a single track, that's a lot), which left me feeling a bit estranged.
The opening session by Patrick Lambe discussed the identity of the "new taxonomist" in the field, using results from a survey of members of the Taxonomy Community of Practice. His findings were unsurprising to me at least:
November 20, 2009 - 1:29 GMT
The Faceted Fallacy
... If a tree falls in the forest and no one is there to hear, does it make a sound?
Yes I know it’s a silly old question, with no real definitive answers but it makes our brains think creatively about ambiguous problems, which is fun. A recent thread in the Taxonomy Community of Practice really got me thinking this way in relation to taxonomy.
To summarize the thread, the question was raised, what are the most commonly used facets in an enterprise taxonomy? In response one member posted a “definitive” list of primary facets that could be used as an exhaustive skeleton for the “enterprise”. From here the conversation split in multiple ways:
November 04, 2009 - 9:07 GMT
After braving the high winds, rain and herring here today in Aarhus, Denmark, I had the pleasure of sitting in on the J.Boye keynote session by BJ Fogg of the Stanford University Persuasive Technology Lab.
BJ's topic was how social media uses (and we can leverage) persuasion techniques to influence behaviour. As an intermittently avid and lapsed Facebook and Twitter user, most of this talk felt like a session "on the couch" trying to deconstruct why we do what we do...
Triggers, Motivation & Ability
BJ started his talk with the notion of hot vs cold triggers. Hot triggers give users an immediate and obvious call to action (e.g. a sandwich board inviting you to come inside a store to have a coffee for 1$). Cold triggers are calls to action that can't be immediately acted upon (e.g. an advertisement for a movie or play - you have to call or go to a location to buy tickets).
Social media often uses hot triggers, sending you notifications to see people's feeds, see who has friended you, etc. But as BJ explains, triggers are not enough to create behaviours. You also need motivation.
Motivations for behaviour include:
- Pleasure / Pain
- Hope / Fear
- Social Rejection / Acceptance
So, I might decide to get involved in Facebook because I enjoy seeing what my friends from high school look like 15 years later (which counts for both pleasure and pain in many cases), or because I fear being seen as a old fuddy-duddy who doesn't keep up with the times, or because I want to relive the awful dance of social acceptance and rejection from high-scool.... ugh.
October 21, 2009 - 1:19 GMT
Best Practice #2: Use chunking and grouping to increase scanability and learnability
So you’ve taken the mega-menu plunge and you now have more labels to fit into your drop-down. How do you make sure it doesn’t look like a mess of text?
There are a couple of options:
Grouping:
Create clear and logical groupings within the menu and give them prominent labels that can easily be scanned.
There are four elements to this approach
1. Logic: Groups have to be internally coherent and logical. Either they are all children of a common parent or somehow conceptually related in a way that is evident and quickly learnable.
2. Labeling: Use simple, unambiguous labels that convey the nature of each group. Decide if your labels will be “clickable” – is there a landing page behind them or is it just a visual way-finder? The mega-menus tend to discourage clicking on such intermediate levels, but marketing may want the space to provide category-level merchandising.
3. Volume: Follow general good practice on number of items in a category. We can thank cognitive science for an easy rule of thumb of 7 +/- 2, but I would say that in a mega-menu, space being limited, I would reduce that to 5 +/-2. This will reduce visual noise and fits well with best practice #1 (less is more).
4. Visual distinction: Use striking colors, increase white space between groups, use shading or dotted lines… anything that you can do to make a visual separation between the groups so that they eye can quickly skip from one group to the other without much thinking.
Let's look at some examples.
October 05, 2009 - 10:15 GMT
No matter where I run, I cannot seem to hide from them.
They fly out of website navigation menus with no warning. They assault my senses with link overload.
...they are...mega menus.
Are they a new navigation paradigm or just a bad fad - like acid washed jeans?
And whose idea were they anyways?
It's difficult to trace the starting point of the mega menu (or mega fly-out, or maxi menu, or whatever you call them); they started popping up on e-commerce sites a couple of years ago. The first one I bumped into one, my brow got that wrinkle it gets when I am at once curious and horrified - horrious? curified? I remember thinking, really? This is what we are doing now instead of putting effort into making our drop-downs more usable? Let's just add more drop-down...
Once the initial feeling of horriosity passed, I just forgot about it (aka denial). None of our clients were using them, so I didn't really have to pay attention. And THEN, this March Jakob Nielsen put out an Alertbox saying "Mega Menus Work Well." That was really the clincher. If Jakob/NNG says it's ok, well there goes the neighbourhood.
Since then, we've had a couple of clients go down this road. And I've kind of gotten used to mega menus... in the way that one gets used to white noise or a bad hair cut. To the point where I think that it's time that we acknowledged that a lot of websites are using them - for better or for worse - and that they are here to stay until the next navigation fad comes up. So it's probably a good time to set some basic best practices, to "limit the disasters" (limiter les dégas, as we say in French).
September 29, 2009 - 8:40 GMT
The final draft has been submitted... Mark your calendars...
The Information Management Best Practices 2009 book is going to publication this week, in hopes of being ready for launch at the J.Boye Conference in Aarhus, Denmark, Nov 2-4. I'll be there, giving a talk on SharePoint IA, but also to lend a hand with the book launch activities.
I'm proud to have a chapter in this book, with co-authors Seth Earley & Charlie Gray (CMS & Taxonomy Strategist, Motorola), on one of our most in-depth and successful projects - integrating taxonomy with CMS at Motorola. The best practice covers the steps below in great detail, offering practical advice and screenshots from the actual implementation at Motorola.
September 23, 2009 - 12:18 GMT
How often do you get to be immersed in a completely alien work environment?
As a taxonomist, I get to learn about so many different domains through my work, from mouse genetics to greeting card manufacturing. Each company has its interesting quirks and workplaces...Like the toy manufacturer, whose workers had their cubicles adorned with all sorts of inspiration and materials: multi-colored fur, googly-eye collections, pictures of themsleves as superheroes...
But this week, I got to experience something completely different.
We just started a content strategy project with a semiconductor equipment manufacturer which aims to help their service groups (the folks who fix the machines) get the right information at the right time. This is an interesting project involving issues around technical writing and information architecture (DITA), integration across many different knowledge systems and databases, and getting information to users in a less than hospitable environment - the clean room.
September 14, 2009 - 12:59 GMT
Looking for a good way to spend a week in the California sun and learn more about taxonomy, search and knowledge management? Look no further than the triple-slam event of the fall conference season:
Taxonomy Bootcamp / KM World / Enterprise Search Summit West
Register today with our discount code to save 200$!
Mark your calendars, cause we have a full slate of taxonomy-related presentations this year, including:
Workshop: Taxonomy Implementation & Integration (Seth Earley & Stephanie Lemieux)
Date: November 16, 2009 - 9:00 - 12:00
Come hear Seth & I talk about how some of the companies we've worked with have been able to implement their taxonomies and integrate them with WCM, ECM and digital asset management systems among others. Hear about practical applications of taxonomy within different classes of tools as well as technical integration challenges (hierarchy challenges, build-vs-buy issues, etc.).
July 17, 2009 - 1:02 GMT
Recently on the Taxonomy Community of Practice, a member asked the following question on faceted taxonomy design:
"I'm researching about Faceted Navigation and Information Retrieval. I've been looking over the Internet for some articles/books/white papers about which is the best number of facets to use on a classification."
Interesting question, especially given the popularity of faceted search and taxonomy. The community discussed the topic, and a a few answers were provided by members.
June 11, 2009 - 9:00 GMT
I had the great pleasure of doing a podcast a few weeks ago with Paul Miller, podcaster for Nodalities (magazine & blog), on hybrid approaches to folksonomy and taxonomy and their role in the enterprise.
We discussed the now tired debate of folksonomy vs. taxonomy, and focused on the strengths and applications of each approach. I covered how organizations are leveraging social tagging and what some of the pitfalls are in the enterprise context.
I also talk a lot a few of the hybrid approaches to taxonomy & folksonomy:
- Co-existence
- Tag-influenced taxonomy
- Taxonomy-influenced tagging
- Tag hierarchies
February 20, 2009 - 10:24 GMT
I recently started reading Wikinomics: How Mass Collaboration Changes Everything, by Don Tapscott and Anthony D. Williams. I know, I know. The book was published in 2006, and I’m only just now reading it. However, the ideas I think are very relevant to what is happening in the current economy and discussions around the future of taxonomy.
Tapscott and Williams write about corporations: “While hierarchies are not vanishing, profound changes in the nature of technology, demographics, and the global economy are giving rise to powerful new models of production based on community, collaboration, and self-organization rather than on hierarchy and control.” Since taxonomies are a reflection of the needs and culture of an organization, I apply this notion to the future of hierarchical vocabularies as well.
February 14, 2009 - 9:35 GMT
My last few blog posts on keyword research tips have generated interest from our readers regarding the relationship between the SEO task of keyword research and taxonomy. The purpose of today’s post is to examine the intersection between the two and offer a little advice for reconciling the internal perspective of taxonomy with external internet search. We can harmonize these perspectives using a data-driven approach to understand the "mental model" of the external searcher.
January 19, 2009 - 11:31 GMT
Continuing the exploration of taxonomy in the context of records management, I’m going to focus on the second challenge listed in my earlier post on the subject: taxonomies and record retention schedules exist but are not being used effectively. I worked on a records management project in which we were to create the retention schedule for one business unit as a baseline for building out the schedule as the records management initiative was rolled out to subsequent divisions.
In this case, it was not that they didn’t already have a retention schedule. In fact, they had an extremely robust, thorough, and complicated schedule created by another consulting firm specializing in records management. It was so robust, thorough, and complicated that no one could figure out how to apply it, and, so, didn’t.
January 01, 2009 - 6:21 GMT
On this first day of 2009, I thought I'd take a moment to reflect on the CMS Watch list of predictions for 2009. Getting big play in the top 3 is "Taxonomies are dead. Long live metadata!".
"With social computing coming to the fore, it's never been more obvious that everyone does not, and will never, categorize things in the same way. It doesn't even matter what's correct anymore... I will assert that the days of the traditional, definitive, and single-hierarchy taxonomy are long behind us."
I think that this is accurate -- insofar as it uses the traditional, definitive and single-dimension definition of taxonomy that I agree ought to be left in the dust along with corded telephones and dot matrix printers. I mean, I can't even remember ever building a taxonomy that was meant to be traditional or had a single-hierarchy.
December 24, 2008 - 11:38 GMT
We’ve been doing a lot of work with SharePoint lately so I thought I’d put together a quick post on some approaches to implementing taxonomies in the new version. As you may or may not know, MOSS 2007 (or Microsoft Office SharePoint Server) is quickly becoming the new platform of choice for many organizations. This newer version of the application is being leveraged in the development of corporate Intranets, Extranets and even public facing Internet websites, providing information workers with enhanced collaboration and document management capability.
With the exponential growth of implementations worldwide (MOSS is the fastest growing server product in the history of the company) come greater challenges and opportunities for improving knowledge management and information access within the enterprise. The need for consistent organizing principles across enterprise information is of ever increasing importance and, when done correctly, can result in leaps and bounds in employee productivity.
Before we get to any of the details however, let’s remind ourselves that the purpose of building and maintaining taxonomies is to improve the findability of information by:
December 15, 2008 - 5:49 GMT
Taxonomies, as hierarchical vocabulary structures, clearly define relationships between words and concepts. If a taxonomy is implemented and governed properly, there is a high degree of control over how terms are added, modified, and deleted. Terms used for content tagging can also be controlled in how they are selected and applied. Similarly, records management is a discipline requiring high control over documents meeting legal compliance. An ARMA fact sheet defines records management as “the systematic control of records throughout their life cycle.”
Strangely enough, taxonomies and records management remind me of the Panopticon, a prison imagined by the English social theorist, Jeremy Bentham. Let me explain. The Panopticon is a circular architectural structure with an observer in the middle able to keep surveillance over many prisoners at one time without the prisoners knowing who was being watched at any given moment. This allowed for great control at great economy.
As a liberal with world views shaped by films of the 1980s riddled with paranoia about governmental control and espousing an anti-Orwellian future as imagined in 1984, the concept of control of any kind stirs my blood. The Panopticon could very well be the source of Tolkien’s Eye of Sauron, presented in film as aloft in a tower—a kind of all-seeing eye with a 360 degree view. However, and here’s the connection, the control of records in an organization supported by a taxonomy structure can mean the difference between being fined millions of dollars and providing information during a legal discovery process. This by simply managing which information should be retained, retrieved, and/or disposed of properly and in a timely fashion. There is the bridge between the Panopticon and taxonomy and records management; now to build the bridge between taxonomy and records management.
December 03, 2008 - 10:57 GMT
Here is the question posed by Arnold King (http://arnoldkling.com)
"I am interested in the phenomenon of knowledge specialization.For example, in medicine, there are many more specialties and sub-specialties than there were 30 years ago. My guess is that if libraries are still using classification systems, there should be a lot more categories. My guess is that major universities have many more departments than they did 30 years ago. I think this is important in economics because I think that businesses and economic systems have become harder to manage as a result. In short, the leaders tend to know less about the specialized information that is further down in the organization, because the amount of the latter is increasing (I conjecture). I would like some quantitative indicators of the rate at which new knowledge categories or sub-categories are being developed. Do you know how to even go about searching for such indicators?"
I spent some time thinking this over. I may have ranged too far from the question and I know I am preaching to the choir here, but thought the issue of economic value creation and knowledge categorization would benefit from a bigger picture perspective. The problem with the question is that knowledge is fractal in nature. It is endlessly complex and classification depends on scale and perspective. It’s not a matter of “there should be more categories… “; there are more. It simply depends on where you look and your perspective.
December 03, 2008 - 10:57 GMT
Here is the question posed by Arnold King (http://arnoldkling.com)
"I am interested in the phenomenon of knowledge specialization.For example, in medicine, there are many more specialties and sub-specialties than there were 30 years ago. My guess is that if libraries are still using classification systems, there should be a lot more categories. My guess is that major universities have many more departments than they did 30 years ago. I think this is important in economics because I think that businesses and economic systems have become harder to manage as a result. In short, the leaders tend to know less about the specialized information that is further down in the organization, because the amount of the latter is increasing (I conjecture). I would like some quantitative indicators of the rate at which new knowledge categories or sub-categories are being developed. Do you know how to even go about searching for such indicators?"
I spent some time thinking this over. I may have ranged too far from the question and I know I am preaching to the choir here, but thought the issue of economic value creation and knowledge categorization would benefit from a bigger picture perspective. The problem with the question is that knowledge is fractal in nature. It is endlessly complex and classification depends on scale and perspective. It’s not a matter of “there should be more categories… “; there are more. It simply depends on where you look and your perspective.
November 16, 2008 - 8:39 GMT
I recently met with a client who said "no one uses facets for searching..." I expressed surprise at this comment and probed a bit as to why they thought so. We opened their home page and I soon surmised why. The facets they had did not seem to be very useful. No one had tested them and I had not yet spent any time in analysis, but at first glance, they did not provide context for their content. I recall one facet was "content type" and contained terms like "pdf", "doc" and "jpg". There were also ambiguous terms like "article", "white paper" and "research". I am not necessarily saying these were not useful, but I did not understand the difference between "white paper" and "research". (Perhaps a frequent user would).
The point here is that faceted search is incredibly powerful but only if the facets make sense to users and the terms are clear, concise and meaningful. Terms have to help users locate what they want and not frustrate them in the process.
In support of that goal, I wanted to point out some examples of bad facets - the facets that don't help anyone and that sully the good name of faceted search.
Here is an example from the Verizon Wireless site:

October 06, 2008 - 1:03 GMT
Forget taxonomy, ontology, and psychology. Who knows why people do what they do? The point is they do it, and we can track and measure it with unprecedented fidelity. With enough data, the numbers speak for themselves." (1)
Recently Chris Anderson wrote an article for Wired magazine called the The End of Theory. The thesis of the article in a nutshell is that the impending petabyte era of data storage signals the end of the traditional scientific method of discovery. No longer are we bound to the outdated model of observation, hypothesis and measurement. Computers (developed by Google & IBM) "can throw the numbers into the biggest computing clusters the world has ever seen and let statistical algorithms find patterns where science cannot."
September 19, 2008 - 4:14 GMT
I was recently in a meeting where it was said that a lack of subject matter expertise is a disadvantage in taxonomy development. This is understandable; it makes sense to assume that the more domain expertise a taxonomist has, the better the final information product will be. However, my experience has shown that this is not always the case. So exactly how does the role of subject matter expert (SME) fit into taxonomy development?
September 05, 2008 - 10:34 GMT
The Other category: also known as General, Miscellaneous, My Stuff, or, too often, the shared drive.
The Other category is the junk drawer for all those taxonomy terms that just don’t seem to fit anywhere else. Reaching into it is taking a chance as you never know what you may find—the yo-yo you can’t seem to throw away, a pair of rusty scissors threatening to impale you when looking for loose change, batteries, baggy ties, the old cell phone with numbers in it of people you don’t even remember. When it’s time for cleaning up, you can either throw it all away or sort it out and put everything in a more appropriate place.
August 18, 2008 - 4:56 GMT
I worked on a project recently highlighting findability issues with unstructured content and the need for appropriate tagging using values from a controlled vocabulary.
At the heart of this project was Digital Asset Management (DAM), a rapidly growing area as more multimedia content is being distributed online, particularly for marketing purposes. The inherent problem with digital assets is the potentially large amount of information about what a piece of content is but the lack of information describing what that content is about. Unlike other content, which may contain text or be located with surrounding textual context, digital assets do not typically contain text, especially any which is structured for discovery by search engines. Any textual and searchable elements must be associated to digital assets through the use of metadata. Metadata describing what the content is, including attributes like video length, number of pixels, and file size, can be associated to the content and is often automatically attributed through business rules.
What the asset is about, however, is not inherent. It must be associated to the content either manually or automatically by loading the content once business rules have been thought out and established.
August 14, 2008 - 4:59 GMT
In my last post, I mentioned the difficulty that some clients/stakeholders have in letting go of certain terminology when they undertake a taxonomy project:
Search engine optimization (SEO) has become one of the most important tools in helping us taxonomists get hard data that is meaningful and fight against the inclusion of terms that are too cute, ambiguous or otherwise detract from the findability of content.
August 11, 2008 - 7:37 GMT
There are three different types of relationships in taxonomies:
- Equivalent (Synonyms: "International Business Machines = IBM")
- Hierarchical (Parent/Child : "Computer Manufacturers => IBM")
- Associative (Concept/Concept: "Software Group - Software")
Heather Hedden's presentation on taxonomy powered discovery for a recent Boston KM Forum contained an interesting set of examples for how to organize the last type of conceptually related term sets.
- Process and agent: Programming - Programmers
- Process and instrument: Skiing - Skis
- Process and counter-agent: Infections - Antibiotics
- Action and property: Environmental cleanup - Pollution
- Action and target: Auto repair - Automobiles
- Cause and effect: Hurricanes - Flooding
- Object and property: Plastics - Elasticity
- Raw material and product: Timber - Wood products
- Discipline and practitioner: Physics - Physicists
- Discipline and object: Literature - Books
July 21, 2008 - 6:35 GMT
In our work of building and maintaining e-commerce taxonomies, we often run into the problem of products not fitting nicely into one single category. Although this problem is not specific to e-commerce taxonomies, their use for navigation and browsing presents a special categorization challenge; the need to lead a wide range of customer types down an intuitive path to the product they are looking for. Think about something as simple as a pair of headphones: where do they belong in the following hierarchy?
July 08, 2008 - 10:29 GMT
As a taxonomy consultant, I always recommend (rather, urge with great gravitas) to my clients that they reserve some time and budget for adequate user testing. As they say, the proof is in the pudding: there's nothing better than quantitative data to tell you whether you've built a structure that really resonates with your core audiences and facilitates their tasks. Creating a taxonomy without testing is putting a lot of faith in guessing - albeit, usually pretty good guessing, based on industry experience and knowledge of best practices if you have a good taxonomist. Having done user testing on taxonomies I've built a few times, I compare the feeling to what I imagine it's like a being an actor or actress watching yourself in a film.
December 09, 2007 - 9:18 GMT
We recently had a prospect ask what they needed to consider as part of their taxonomy RFP. Here are some things to include:
1. Specific approaches to taxonomy development: steps for term extraction, approaches for automated and manual content audit procedures
2. Taxonomy testing: What are the methods by which the taxonomy will be tested prior to deployment? What usability tests would be performed and what data would be collected?
3. Metrics: How will search engine and web tracking metrics be used in deriving the taxonomy?
June 03, 2007 - 10:32 GMT
April 12, 2007 - 1:08 GMT
One of the biggest challenges to maintaining quality and value in a taxonomy lies in keeping interests aligned and resolving conflicting perspectives. By its nature, a taxonomy attempts to reconcile diverse perspectives – those of various types of users, engaging in diverse tasks. It also needs to support the needs of merchandisers who are vying for valuable site real estate. But what is the true purpose of the taxonomy from a strategic perspective? Is it to market the company’s offerings? Educate customers? Sell merchandise? Help the customer find answers?
February 15, 2007 - 4:25 GMT
A client recently forwarded a blog post to me about folksonomies and asked if this is something we should consider.
Here is my take: Social Tagging (use of “Folksonomies”) has a valid place in the scheme of things. We can use them as a source for candidate terms or new term harvesting. They are also useful for content that is less structured that may be tougher to organize (discussion or blog postings for example) or material that does not justify structured tagging. (Obscure web pages). The fundamental issue here is that they don’t take the place of formal taxonomies but can be used to augment them. In some cases, user generated tags make a lot of sense. (A group of engineers working on a new product might come up with terms that are not yet in the formal taxonomy. They also speak the same technical language and use the same terms. Raytheon uses this approach of social tagging for what are called “featured results”. These appear along with the “officially” tagged content).
February 03, 2007 - 4:14 GMT
One of the things that we get called in to help with is the set of governance policies and processes that are necessary to make taxonomy projects a success. There are number of things that need to happen for organizations to be effective in this area:
1. Sponsorship: Someone with power and authority needs to understand the value of taxonomy and nomenclature governance This person can help settle turf disputes and conflicting organizational requirements. The key is that they are truly engaged and really get it, rather than delegating authority.
2. Ownership: An operational champion needs to own the project. This is the person to whom ultimate accountability falls. They are the one that has to drive communication and get people to participate
November 07, 2006 - 1:30 GMT
Recently, a client declined the opportunity to review some work we were doing. When we submitted the project, we did so with the caveat that the taxonomy needed to be validated and that we needed a half day from the subject matter experts.
The client said "no, we can't do that - they don't have the time".
I explained that we had to make a number of assumptions about the taxonomy and how it would be integrated into content strategy. We needed to discuss these issues and talk about the choices that could be made and the alternatives available. This still met resistance. They said "you are the experts - just tell us how to do it. Rather than asking us, just tell us the answer."
September 28, 2006 - 11:22 GMT
A number of clients and prospects have come to me with the same dilemma. They have been engaged in varying levels of taxonomy programs and have arrived at a point where they need to overcome a certain sticking point in their projects. They are wrestling with challenges around getting real benefit from their taxonomy projects. While on the surface, taxonomy as a concept is straightforward, getting the organization to embrace standardized terminology and consistent classifications is incredibly complex. It impacts so many aspects of the organization on many different levels: many classes and instances of technology, work processes and practices, change management and governance. Here are a few guidelines to keep in mind when trying to move the organization to the next level:
August 14, 2006 - 7:28 GMT
An interesting problem was posed to a mailing list I am a part of...
Imagine that you have been using a single hierarchy to structure and organize your information for years, and it has been very successful up until now...
But now it is time to move to a different content management system, and not only that - business has changed (of course), and not every way of organizing and understanding the information could possibly have been anticipated. (Or perhaps you did anticipate some, but for practical matters limited the amount of metadata you might apply to content.) So you have new ways that users want to search and navigate, but never considered these at the start. What do you do?
July 07, 2006 - 1:55 GMT
My last post discussed the idea that knowledge management has gone through the hype cycle and people are abandoning the term for more fertile buzzwords. According to Gartner, taxonomies are now at the “Peak of Inflated Expectations” headed for the “Trough of Disillusionment” in the hype cycle, which begs reflection on the concept of taxonomies.
All sorts of projects come to us as “taxonomy” projects: Information architecture, content management, portal, records management, document management, integration projects, metadata management, search tuning and integration, workflow management, even organizational change projects. And of course Knowledge Management.
The bulk of my career has been in these areas with taxonomy being a natural part of the process. In the past I was called in to do “x” with x being any of the above and taxonomy being a work stream. Now, because we are so well known as taxonomy experts, we are called in to develop the taxonomy components of large multi vendor projects.
There are a few ways to think about this.
Taxonomy affects each of these areas and needs to be integrated into multiple applications and contexts
We are looking at these client requirements and in some case deciding that though taxonomy is essential, the focus of the project is in implementation of one of these initiatives. The customer is calling this a taxonomy project, but it is really a document management project, etc
For whatever reason, “taxonomy” has become the preferred term and seems to be understandable and resonates with managers. This is good for the most part.