<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Collie Maguire on Medium]]></title>
        <description><![CDATA[Stories by Collie Maguire on Medium]]></description>
        <link>https://medium.com/@collie.maguire?source=rss-305222f238cc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lB6hoHm_w_TEIhlCp0-4BA.jpeg</url>
            <title>Stories by Collie Maguire on Medium</title>
            <link>https://medium.com/@collie.maguire?source=rss-305222f238cc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:10:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@collie.maguire/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[There Can Be Only One]]></title>
            <link>https://medium.com/kingfisher-technology/there-can-be-only-one-e917d877db9a?source=rss-305222f238cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e917d877db9a</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[glossary]]></category>
            <dc:creator><![CDATA[Collie Maguire]]></dc:creator>
            <pubDate>Fri, 25 Aug 2023 07:53:28 GMT</pubDate>
            <atom:updated>2023-08-25T07:53:28.376Z</atom:updated>
            <content:encoded><![CDATA[<p>This article has been written by Collie and Katerina Ploussiou</p><p>Those of you of a certain generation will remember the line from the movie ‘Highlander’. It is appropriate. We live in a world of choice. The more choice we have the more stressed we become. This blog is how we came to create a <strong><em>single source of truth</em></strong> for our glossaries in Kingfisher.</p><p>When it comes to choosing the correct road, route, word, method, it’s easier when the choice is limited than when it’s expansive.</p><figure><img alt="stressed and confused in front of a board full of questions" src="https://cdn-images-1.medium.com/max/800/1*hgFUvAKI286SsIvlyeDffA.jpeg" /></figure><blockquote>“Freedom of choice” leads people to feel powerless and frustrated, because choosing ‘one’ among many other options means giving up the rest of the opportunities. At the same time, since people can easily change and replace the choice, the absolute value of making a choice no longer exists.” ( <a href="https://en.wikipedia.org/wiki/The_Paradox_of_Choice">https://en.wikipedia.org/wiki/The_Paradox_of_Choice</a>)</blockquote><p>Imagine if you will, a wiki in a single department which returned over 1500 choices for the word glossary. How would you know which one to trust?</p><p>My remit in Kingfisher is to help people find documentation. When that’s done, it’s then to work on communication. Establishing a single source of truth is in effect killing two birds with the one stone.</p><p>Documentation that can be found, understood and trusted as a single source of truth saves time money and energy. When we have a bunch of glossaries that are not updated, have no owner, and are incomplete, we have no way of knowing which one we can trust or which one to build on.</p><p>The first solution was to track down as many of these glossaries and add labels or meta data. That was a very time consuming task and not very practical due to the sheer number in existence.</p><p>The second part of the solution was to run a ‘content by label’ macro. This macro finds all the pages with a specific label set and returns them in your specific page. The point of this was to gather all the glossaries in one place. It worked after a fashion. There was still loads out there I hadn’t managed to label. At least people were beginning to come to the one place and understand what had been happening over the years.</p><p>Further investigation showed us that at one point, space templates had been created and implemented and one of these templates had included an empty glossary page by default. So there were hundreds of pages titled glossary that were just empty holders.</p><p>At this point we had built a trustworthy glossary for the engineering department and had a holder for all other glossaries we could find. The drawback was still the amount of content available on the search, plus it wasn’t business wide. It was limited to the users of the wiki.</p><p>While this work was ongoing, other teams and individuals had reached out about creating a glossary. While I welcomed the initiatives, it seemed the same mistake as in the past was being created. An individual would put in time and effort, create a coherent expansive glossary, but then nothing. It didn’t have meta data. Socialisation was lacking. There was no company wide agreement or even access to those glossaries that were being established.</p><p>Eventually some colleagues reached out to talk about an application called Collibra, that was available but they felt was being underutilised. This application was extremely suitable for building a company wide glossary. Everyone in the company had access to it so licensing wasn’t an issue.</p><p>This is the use case they established.</p><p>A well-managed glossary ensures that Kingfisher speaks the same language by clearing up ambiguity in business/data/technical terminology. To ensure that Kingfisher is managing its glossaries we have identified all key glossaries used in various locations and ingested them into a single sourced location — the Data Catalogue tool (Collibra).</p><p>The Data Catalogue tool (Collibra) embeds the right governance guaranteeing that information is updated regularly by encouraging collaboration amongst colleagues. It is the single source of truth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*O4eb6ApiK9BpBR5y8GNZjg.png" /><figcaption>Buisness case</figcaption></figure><p>Business Challenge</p><p>The challenge that colleagues at Kingfisher are facing is the difficulty of finding terms/acronyms with the right information and ownership. Glossaries are stored in different locations around Confluence that are often not updated resulting in misinterpretation and misinformation.</p><p><strong>How can the Data Catalogue Tool (Collibra) Help?</strong></p><p>Workflows:</p><p>Collibra can use workflows. Workflows define processes and manage their execution. They coordinate tasks that are done automatically, or by users. This allows for business processes to be streamlined and collaborative decisions to be made in a guided and controlled way.</p><p>Workflows can be customised by the Data Catalogue system admins to fit the needs of the teams.</p><p>Browser Extension:</p><p>The Browser Extension provides seamless access to the Data Catalogue platform from within PowerBI, Confluence and other web apps. This works for Chromium-based browsers, such as Google Chrome and Microsoft Edge. The Browser Extension enables quick access to information in the Data Catalogue tool via a context menu.</p><p>Understanding whether a term is up to date or not:</p><p>Each term in the Data Catalogue Tool will be marked as Accepted, Rejected or Resolution Pending indicating whether a term is appropriate to use, not appropriate to use or awaiting a decision whether it’s appropriate to use respectively. Users will also be able to comment and rate the terms from 1–5 stars.</p><p>The Solution</p><p>All glossary terms were firstly identified and ensured that they are appropriate to be ingested into the Data Catalogue tool. All terms are located into one single location where users can search, filter, and identify what they are looking for.</p><p>A workflow was designed to ensure that users can propose new terms and acronyms. Any user will be able to propose a term or acronym which would then notify an owner to review all details of the term. Once reviewed the owner will be prompted to accept or reject the term by also providing a comment. The user who has proposed the terms will then be alerted about the decision from the owner.</p><figure><img alt="Diagram showing the workflow process from start to proposing new terms and reviewing the term." src="https://cdn-images-1.medium.com/max/852/1*IDXwNkDmoKARWC5vtjQ6Uw.png" /><figcaption>Diagram showing the workflow process from start to proposing new terms and reviewing the term.</figcaption></figure><p><strong>What did all this look like in reality?</strong></p><p>We had an initial meeting called by the Nucleus team to discuss the subject. While that meeting had a good attendance we ended up with a small but dedicated core of people. Over many weeks, we discussed the look and feel of the tool and how the glossary would actually work. How would we deal with acronyms that looked the same, how would we tag terms and other relevant questions. We then had to socialise the community. Change is not always welcome, especially when it involves changing work practices. We had realised that just creating a single source of truth was not enough. We had to get people on board.</p><p>One of those onboarding practices was to place a warning on all of those aforementioned glossaries, explaining that there was a new single source of truth. We also explained that the glossaries in the wiki would at some point be deleted. It was decided not to place a strict time frame on deletion to give people time to adjust and learn the tool.</p><p>We advertised in various channels on our MSTeams and provided a link to the Collibra personnel who would answer any questions that people may have.</p><p>There was push back of course. However we now have completed the main thrust of the work and are looking forward to the adoption of the project.</p><p>Conclusion</p><p>A single source of truth is essential for all documentation types. The Collibra team and colleagues have done sterling work in improving how we use the glossary in the company. It provides a means to cleaning up our wiki where we can now save space, have clarity, and move forward using this work as an example. We can improve the confidence in our glossary and save time due to not having to cross reference and double check. All in all it is a great addition to the tools we use.</p><p>If you are interested in joining us on our journey, please do check out our <a href="https://careers.kingfisher.com/">careers page</a>.</p><p>Thanks for reading</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e917d877db9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kingfisher-technology/there-can-be-only-one-e917d877db9a">There Can Be Only One</a> was originally published in <a href="https://medium.com/kingfisher-technology">Kingfisher-Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>