Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Current »

Approaches

Top down

  • business users

  • yield most intuitive, navigable taxonomy designs

  • The issues are that they don’t yield a complete design right at the outset, topics may get left out; second, if not clearly managed/facilitated, taxonomy design can reinforce bad behaviors

  • Start at highest level and break into secondary, tertiary

  • Blank slate is the best approach if using top down

Bottom up

  • Taking the content and indexing it to find similarities between content and then greater similarities; building a pyramid

  • Issues

    • content driven: you’ll end up with tax that’s all about the amount of content you have now. reinforces existing knowledge rather than processes. not necessarily bad, just keep in check

    • time consuming

  • Best when you have a tool helping you auto-categorize, but tools can’t evaluate value of content, they just go on the volume/weight

Hybrid

  • Start with small groups to workshop the first couple of levels then use the tool to match the content with topics and recommend additional subcategories.

  • Start with top down and then tag sample content to identify additional topics (like faking a bottom up design)

Off the shelf taxonomy

  • Only works if you have a standard set of products/information resources you want to align to other orgs (ISO codes)

  • For taxonomy for the business' mission, don’t buy an off the shelf taxonomy

Methodology

image-20250106-132425.png

KIM - knowledge information management

Planning

  • Business case

    • audience, mission of audience

    • true reason for designing taxonomy

    • what specifically will taxonomy do for the end users?

  • Scoping

    image-20250106-132327.png

    • timeline, regulatory requirements

      • plot out as-is and end state (to-be), which is 2-3 years out.

    • people - availability, acceptance, understanding

    • technology - requirements vs capabilities

    • budget

  • Knowledge gathering

    • communication, education, marketing

      • set user expectations, translate pain points into solutions in real time

      • create buzz around the project

      • market the results not the definitions

    • Identify tax and content starting points

      • key stakeholders and early adopters

      • existing tax and info sys

      • critical must-find content

Stopped at 1:35

Design

Testing & Development

  • No labels