Skip to main content
Skip table of contents

Running a cataloguing workshop

After you have aligned on how you would like to use K and what metadata you would like to store in K, running a cataloguing workshop is a great way to establish a solid foundation to accelerate your data governance and data management maturity journey.

This page provides suggestions on how the data team (or teams) in your organisation can prepare and run a cataloguing workshop.

Preparing for a Catalogue Workshop

There are 2 key elements to prepare for to ensure a successful workshop.

K Platform checklist

  • Check all participants have the correct K roles assigned

  • Check sources have been loaded

  • Check the Data Load Dashboard and ensure there will be no batch jobs running during the session - During the session it is likely multiple users will be using the bulk update functions. Avoiding unnecessary batch jobs running during a workshop time will improve upload speeds

  • All Critical Collections have been created and loaded

K Governance checklist

  • Detailed definition and guidelines have been developed for the Critical Collections

  • A ‘best practice’ example has been created for a Data Profile

Designing the Agenda

When designing the agenda there are a few key questions to consider:

  • What are the success outcomes of the workshop?

  • Will you structure the agenda to be run across one day or multiple sessions?

  • How will you divide the cataloguing tasks into sprints? By Domain? By Source?

    • If want to prioritise specific data assets on the day, you can pre-create a list per team or sprint.

  • With limited time, what data assets do you want to prioritise and focus on?

Agenda example



01 Welcome

  • Introductions

  • What do we want to achieve today

  • Agree scope (In & out)

45 min

02 Recap and Demo of K Features

30 min

03 Walkthrough of ‘Best Practice’

  • Show case example of ‘best practice’ K documentation

  • Team discussion on ‘minimum acceptable’ documentation

30 min

04 Catalogue Sprint 1

  • In pairs (or individually) complete items in scope for Catalogue Sprint

60 min

05 Catalogue Sprint … X

… min

06 Team Debrief and Reflections

  • How was the cataloguing experience?

  • What tips/tricks did you learn that helped speed up the process?

  • What will you take back to the broader team?

3min per person


15 min general conversation

07 Next Steps

  • Actions and next steps to close out remaining metadata gaps in K

  • How to scale and embed K documentation

30 min

Selecting the Participants

The design of the agenda and scope of the Cataloguing Workshop will help guide which Data SMEs you should invite.

In addition to Data SMEs that can help contribute knowledge, other individuals you may want to invite include:

  • K Champions: You may invite K Champions to a portion of the workshop so that they can continue helping advocate for K. This is particular important for teams that have a ‘de-centralised’ governance approach as you may want to have an ‘alignment’ session around ‘best practice’ and how you want K to be used

  • Data Governance managers: It may be worth having a few data governance manages attend so that you can quickly align on any questions that arise on how to tag or categories data items. For example, if you’d like the workshop to link all data assets to a ‘Critical Data Elements’ catalogue, there may be questions around CDE definition

  • Domain representation: Would you like to run sessions that are domain specific or domain agnostic. There are pros and cons to either approach.

Post-Workshop activities

After the first Cataloguing Workshop, some K users have found it helpful to close out the session with the following activities:

  • Socialise the key updates with business stakeholders and close out questions: At the end of every Catalogue sprint, a new Bulk Edit Excel template is downloaded. This excel can be shared with the business and other key users to validate and check the updates made

  • Review the Governance Insights Dashboard to identify which are the next data assets that need to be prioritised for update

  • Review the Data Governance and Data Management collections to assess if they need to be refined

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.