The Knowledge Management (KM) Depot

The Knowledge Management (KM) Depot

Tuesday, December 31, 2013

Leveraging Faceted Search

In my upcoming publication Knowledge Management in Practice I detail search in a chapter called "Dude Where's my Car: Utilizing Search in KM". At the KM World Taxonomy Boot Camp I spoke about Utilizing Ontologies for Taxonomy & Content Organization and during this discussion there were questions concerning faceted search. Before the year ends (literally) I wanted to provide some details concerning faceted search:

Faceted search offers remarkable potential for putting the search experience in the hands of the user. It provides a flexible framework by which users can satisfy a wide variety of information needs, ranging from simple look up and fact retrieval to complex exploratory search and discovery scenarios.

With faceting, search results are grouped under useful headings, using tags you apply ahead of time to the documents in your index. For example, the results of a shopping query for books might be grouped according to the type of book and the price.

Each time the user clicks a facet value, the set of results is reduced to only the items that have that value. Additional clicks continue to narrow down the search—the previous facet values are remembered and applied again.

Faceted search results provide an easy-to-scan, browse and display that helps users quickly narrow down each search. The faceting tags that you store with your documents provide a way to add your own taxonomy to directly control the presentation of search results. In the end, it's about helping the user find the right information. Faceted search gives a user the power to create an individualized navigation path, drilling down through successive refinements to reach the right document. This more effectively mirrors the intuitive thought patterns of most users. Faceted search has become an expected feature, particularly for commerce sites.

However, before you get too deep into the intricacies of faceted search, it is extremely important that you develop use cases or user stories around your search scenarios mentioned earlier. A great way to get started is to identify the main concepts you would like to search (People, reports, policies, etc.); next create logical categories (start by building or leveraging a taxonomy) for each group (Engineers, Executives, Administrators, etc.) a card sort exercise will be helpful here, and finally create (or use a current) information/content model showing relationships and considering navigation paths.

This will put you on a path to realizing the benefits of faceted search!

Labels: , , , ,

Thursday, November 28, 2013

The Role of the Information Architect

The Role of the Information Architect


Often when I am working with organizations to implement a Knowledge Management (KM) Solution the role of the business and more specifically the users of the application are discussed. The users of the proposed KM application will determine its worth to the organization. If the system is not used and/or is poorly received the organization would have wasted time and valuable resources in developing the KM solution. When this occurs KM in many instances receives a negative view in the minds of the people at the organization and this leads to the abandonment of KM entirely. To prevent this unseemly situation and to get your organization started in the right direction I would recommend bringing in an Information Architect. In this role the information Architect will be the catalyst to bring the users together, along with specific business objectives to enable the KM solution to be adopted by the users and embraced by the organization.

One thing you may be asking is “How does the Information Architect accomplish this?” The information Architect Instead of focusing on typical IT problems, comes to the project with a threefold focus: Users of the Information, the Information Itself and the Business/Organization. With this focus the Information Architect will perform the following tasks:

·       Gather Requirements pertaining to the content and structure of the KM solution (SME’s and Users are heavily involved here)

·        Construct the Information Model (SME’s and Users are heavily involved here to further define and validate Content)

·        Instantiate Business Rules (depicted as relationships) onto the model (SME’s and Users are heavily involved here to further define and validate Content Relationships)

·        Develop the Taxonomy (categorizations of content (information & knowledge) for the KM Solution

o   SME’s and Users are heavily involved here

o   Card Sort exercise is often used to solidify the Content Categories and Taxonomy

·         Develops the Metadata Schema (specific information about the content)

·         Develops Standards for Content Assembly

·         Contributes to the development of the Style Guide for Content Delivery

·         Contributes to creating an authoring Environment that would leverage the Standards and Style Guide for Content

When developing your KM solution having an Information Architect (or team of Information Architects) will ensure user and business involvement as well as the adoption and use of the KM solution. This is a step in the right direction to contribute to KM being viewed as a positive influence and having value within the culture of your organization.
If your organization is considering developing or enhancing a KM Solution and are using or considering using an Information Architect I would like to especially hear from you!

Labels: , , , , ,