taxonomy.works
Polski

Services

Three stages in a taxonomy's life: diagnosing what is there, designing what is needed, and the rules that make it last.

  1. I

    Taxonomy audit

    A diagnosis of why the existing structure is not working — before you spend a budget rebuilding it.

    What you get

    • Assessment report with findings
    • Map of the gaps between the schema and how content is actually tagged
    • Recommendations ranked by cost-to-impact
    • Closing workshop with the team

  2. II

    Taxonomy and vocabulary design

    A structure built for a specific retrieval job, not for how a domain is supposed to look.

    What you get

    • Taxonomy in SKOS, CSV or your system's native format
    • Documented rules: division criteria, definitions, scope notes
    • Mapping rules from the previous structure
    • A set of retrieval tests for verification

  3. III

    Governance and maintenance

    The rules and roles that keep a structure from drifting apart six months after launch.

    What you get

    • Vocabulary governance document
    • Change proposal and approval path
    • Review schedule and checklist
    • Training for the people who tag
Plate III — Comparing engagement stages — input, deliverable and scope limits
StageWhen to startInput materialPrimary artifactWhen not to pick this
IAuditAn existing vocabulary or category tree has stopped working in practice.Export of current tagging, schema docs and interviews with daily taggers.Gap report + repair roadmap ranked by cost-to-impact.When building from scratch with no existing data or tagging history.
IIDesignNew product, CMS/DAM migration, RAG deployment, or a clean-slate rebuild.Content corpus, real user queries and target system constraints.Faceted taxonomy (SKOS/CSV/JSON) with explicit yes/no boundary rules.When the current structure is sound and only lacks maintenance discipline.
IIIGovernancePost-launch or whenever multiple teams tag content independently.Working vocabulary, organisational role map and current publishing workflow.Change workflow, term-retirement rules, periodic review checklist and training.When the schema itself has broken divisions — governance cannot fix bad boundaries.