<?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 Kylie Goh on Medium]]></title>
        <description><![CDATA[Stories by Kylie Goh on Medium]]></description>
        <link>https://medium.com/@kyliegoh?source=rss-57f6351617f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TRoFNNrxpP57tjs_suaAZg.jpeg</url>
            <title>Stories by Kylie Goh on Medium</title>
            <link>https://medium.com/@kyliegoh?source=rss-57f6351617f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:22:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kyliegoh/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[The Future of Digital Identity: Decentralised Identifiers and Verifiable Credentials Explained]]></title>
            <link>https://medium.com/govtechsingapore/the-future-of-digital-identity-decentralised-identifiers-and-verifiable-credentials-explained-2cef2ba1c2ad?source=rss-57f6351617f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cef2ba1c2ad</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[govtech]]></category>
            <category><![CDATA[verifiable-credentials]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <dc:creator><![CDATA[Kylie Goh]]></dc:creator>
            <pubDate>Sat, 05 Aug 2023 05:59:21 GMT</pubDate>
            <atom:updated>2023-08-05T05:59:21.279Z</atom:updated>
            <content:encoded><![CDATA[<p>Decentralised Identity has been gaining traction as the future of digital identity management, with terms like Decentralised Identifiers (DIDs) and Verifiable Credentials (VCs) garnering attention as the building blocks of Decentralised, or Self-Sovereign Identity.</p><p>However, as this paradigm shift in digital identity is still building momentum and remains a nascent technology (for now!), it is not yet as well-understood as it should be.</p><p>In this blogpost, we’ll go beyond the buzzwords and explore DIDs and VCs in greater detail. We’ll investigate the relationship between DIDs and VCs, the potential applications of DIDs and VCs, and actually, what does blockchain have to do with all of this anyway?</p><ol><li><strong>What are Decentralised Identifiers (DID)?</strong></li></ol><p>DIDs are a new type of globally unique identifier that enable individuals and organizations to generate their own identifiers. Individuals and organisations can prove control over these identifiers using cryptographic techniques.</p><p>To illustrate the difference between DIDs and conventional identifiers, consider the personal identifiers that we acquire as we journey through the world today — communications addresses such as email addresses and social media usernames and government-issued identification numbers like identification card numbers, passport numbers and driver’s license numbers.</p><p>The majority of these identifiers are by default issued by external authorities and controlled by centralised identity management systems, whereas <strong>DIDs are created by individuals / organizations and controlled by themselves, without relying on a third party to manage their data.</strong></p><p>Let’s get into the nuts and bolts and learn more about how DIDs work:</p><p>The form of a <strong>DID</strong> is simple. It consists of three parts: 1) the <em>did</em> unique resource identifier (URI) that tells us we are looking at a DID, 2) the identifier for the DID method (as of this writing, there are 170 DID methods in development!), and 3) the DID method-specific identifier. The DID identifies its <strong>subject</strong> (which can be a person, group, organization, thing or concept).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*yLQyYf1oKBVtW28t" /><figcaption>Source: W3C Decentralized Identifiers (DID) v1.0 Core architecture, data models, and representations</figcaption></figure><p>This gets more complicated, so hang in there! With this DID (did:example:123456789abcdefghi), we can obtain a <strong>DID document</strong> which contains information about the DID. The process of DID resolution is intermediated by a <strong>Verifiable Data Registry</strong>, where both the DID and DID document are recorded. Examples of Verifiable Data Registries include distributed ledgers, decentralized file systems, databases, peer-to-peer networks, and any forms of trusted data storage. The DID is controlled by a <strong>DID controller</strong> (who can be the DID subject), who can make changes to the DID document.</p><p>Each DID comes with one or many <strong>public-private key pairs</strong>. The private key(s) are controlled by the DID controller while the public key(s) are stored in the DID document and enable the DID controller to prove that they control the DID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/0*Oc4MdPYSR-Ri_Sfh" /><figcaption>Source: W3C Decentralized Identifiers (DID) v1.0 Core architecture, data models, and representations</figcaption></figure><p>Using the public-private key pairs, DIDs can be used for a variety of purposes, including online authentication, secure messaging, and digital document signing.</p><p><strong>2. What are Verifiable Credentials (VCs)?</strong></p><p>At its core, a credential is a set of claims made by an issuer about a subject. Everyday examples include driver’s licenses, educational certificates, and passports. For many people around the world, these credentials are issued on paper. Unfortunately, such traditional credentials like paper-based certificates and ID cards are prone to fraud and can be easily counterfeited or tampered with. They are also difficult to manage and share, requiring individuals to carry multiple credentials and rely on central authorities to verify their authenticity.</p><p>VCs are digital credentials that can represent everything paper credentials can, but offer several advantages over traditional credentials. First, they are more secure, using cryptographic technology to ensure that they cannot be altered or forged. Second, they are easier to manage and share, allowing individuals to store their credentials in a digital wallet and share them with third parties as needed. Finally, VCs give individuals greater control over their personal information, allowing them to choose which credentials to share and with whom.</p><p>At this point, it is important to clarify that VCs are different from electronic representations of credentials (e.g. a scan of a paper credential or a PDF), which do not have additional protections against fraudulent modifications by default.</p><p><strong>3. What is the relationship between decentralised identifiers (DIDs) and verifiable credentials (VCs)?</strong></p><p><strong>DIDs and VCs are not the same thing</strong>. DIDs provide a unique identifier that can be used to verify an individual’s identity, while VCs provide information about their subject, such as an individual’s qualifications, skills, and attributes.</p><p>That being said, while DIDs do not depend on VCs and vice versa, they can be very powerful when used in combination. For example, a VC can use a DID to identify its issuer and/or subject, which then ties the information contained within the VC with a verifiable digital identity. Together, they can empower individuals to create a secure and decentralised digital identity that can be used across different systems and platforms.</p><p><strong>4. What does blockchain technology have to do with DIDs and VCs anyway?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XM400R4ZKafrpeWy" /><figcaption>Photo by <a href="https://unsplash.com/@theshubhamdhage?utm_source=medium&amp;utm_medium=referral">Shubham Dhage</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>DIDs and VCs do not require the use of blockchain technology. However, they are often associated, as public blockchains provide a transparent, immutable and decentralised way to store and manage data. Blockchains can be used to register and verify DIDs (playing the role of the <strong>Verifiable Data Registry</strong> in the diagram above), and to store and verify VCs. However, they are by no means the only option. Other Verifiable Data Registries utilised by DID methods include secure databases, the Interplanetary File System (IPFS), and the Domain Name System (DNS).</p><p><strong>5. What are some of the use cases for VCs and DIDs?</strong></p><p><em>Education Qualifications</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b3-9z-_oFoYjUdG9" /><figcaption>Photo by <a href="https://unsplash.com/@skillscouter?utm_source=medium&amp;utm_medium=referral">Lewis Keegan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>VCs can be used to issue tamper-proof academic certificates that can be easily shared and verified online. This was the impetus behind <a href="https://www.opencerts.io/">OpenCerts</a>, which is used by institutes of higher learning in Singapore to issue academic certificates and transcripts digitally to students. With OpenCerts, the authenticity of each digital certificate can be trusted, thus reducing costs, time and effort to verify. Such verifiable credentials can also be viewed, shared and verified internationally, which is especially relevant in our globalised world where it is common foru s to move for work and education</p><p><em>Health Records</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tpb2GLoXzm594EuD" /><figcaption>Photo by <a href="https://unsplash.com/@fusion_medical_animation?utm_source=medium&amp;utm_medium=referral">Fusion Medical Animation</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As VCs can be transmitted rapidly over the Internet, they are more convenient than their physical counterparts when trying to establish trust at a distance. This was especially true during the COVID-19 pandemic which saw the unprecedented closure of several borders around the world. As borders reopened, travellers were required to show proof of pre-departure tests or vaccination status, while immigration authorities needed a way to easily verify these assertions.</p><p>In response, <a href="https://www.healthcerts.gov.sg/">HealthCerts</a> was developed to provide travellers with easily verifiable digital certificates. Immigration authorities were able to easily <a href="https://www.verify.gov.sg/">verify</a> these certificates online by scanning a QR code on the digital certificate.</p><p><em>Cross-Border Trade</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0RbuBemna0lTtS2s" /><figcaption>Photo by <a href="https://unsplash.com/@william07?utm_source=medium&amp;utm_medium=referral">william william</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>VCs and DIDs are not limited to use by individuals. Companies, products and objects can also be the subject of a DID and/or VC. With <a href="https://www.tradetrust.io/">TradeTrust</a>, verifiable credentials are used to issue digital trade documents that can be easily verified and processed. By moving from paper to machine-readable digital credentials, many possibilities for automation of tedious processes are opened up.</p><p>The examples above are powered by the <a href="https://www.openattestation.com/">OpenAttestation</a> framework, which is an open-source framework to issue and endorse verifiable documents developed by GovTech Singapore. Interested? Get in touch with us to explore collaborations in this exciting new area of VCs and DIDs!</p><p>While VCs and DIDs hold great potential for transforming the way we approach digital identity, they are still a work in progress. One of the forums where this important work takes place is at the World Wide Web Consortium (W3C), an international standards organisation for the World Wide Web. W3C creates technical standards and guidelines for web technologies worldwide, including VCs and DIDs.</p><p>The OpenAttestation team from GDS will be attending the <a href="https://www.w3.org/2023/09/TPAC/">W3C Technical Plenary and Advisory Committee (TPAC)</a> in Seville, Spain from 11–15 September and presenting a break-out session on TradeTrust and OpenAttestation. To our fellow techies, we look forward to meeting and interacting with you at TPAC!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cef2ba1c2ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/govtechsingapore/the-future-of-digital-identity-decentralised-identifiers-and-verifiable-credentials-explained-2cef2ba1c2ad">The Future of Digital Identity: Decentralised Identifiers and Verifiable Credentials Explained</a> was originally published in <a href="https://medium.com/govtechsingapore">GovTech Singapore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First 90 Days — Reflections on Onboarding into a New Organisation, Team, and Role]]></title>
            <link>https://medium.com/govtechsingapore/the-first-90-days-reflections-on-onboarding-into-a-new-organisation-team-and-role-f7e893b16038?source=rss-57f6351617f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7e893b16038</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Kylie Goh]]></dc:creator>
            <pubDate>Sun, 15 Jan 2023 08:10:51 GMT</pubDate>
            <atom:updated>2023-01-16T10:41:28.288Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The First 90 Days — Reflections on Onboarding into a New Organisation, Team, and Role</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tnw0jQIUyaAbyALb" /><figcaption>Photo by <a href="https://unsplash.com/@studio_cj?utm_source=medium&amp;utm_medium=referral">Christine</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Three months ago, I started my journey @ GovTech’s Government Digital Services. From developing the legal industry and building international partnerships at the Ministry of Law, I now work with a team of talented developers and designers to build <a href="http://www.tradetrust.io/">TradeTrust</a>, a digital utility that aims to supercharge the global transition from paper-based to electronic trade documents.</p><p>These first 90 days have passed in the blink of an eye. Taking a moment to look back on this journey, here’s what I’ve learnt about onboarding into a new organisation, team, and role:</p><p><strong>1.</strong> <strong>Have a plan, but be prepared to iterate as you go along.</strong></p><p>As I was looking ahead to this new job, I sent out a call for advice to my Telegram support group of new and aspiring Product Managers, which really came through with tons of resources and useful advice (I’ve linked these resources below, along with other resources which I’ve found to be useful!)</p><p>The most common piece of advice was to make the first 90 days count. So, I dutifully drafted a 30–60–90 Day Plan, laying out my priorities and desired learnings.</p><p>On hindsight, not everything went according to plan. I found myself tackling things at an accelerated pace, and having to adjust the plan as I learned more about the product and the team.</p><p>However, as they say, plans are useless but planning is indispensable. The act of planning helped me manage my nerves about the transition. It also helped me hold myself accountable to what I had written down, which included arranging 1-on-1s with various GovTechies across the organisation. That brings me to …</p><p><strong>2.</strong> <strong>Get to know as many people as possible.</strong></p><p>People matter. Beyond getting to know your manager and team members, it’s a good idea to connect with other people in the organisation and to learn about what they’re working on.</p><p>One technique which I used to meet more people was to ask each person I managed to connect with who else I should talk to if I wanted to learn more about X or Y. Most would then offer to connect me with more people. Rinse, and repeat.</p><p>As an extroverted introvert, I alternated between the excitement and exhaustion of meeting new people. However, I’m glad I pushed myself to connect with more people, and I’m grateful to all my fellow GovTechies, who responded with openness and generosity.</p><p><strong>3.</strong> <strong>Observe</strong></p><p>The second most common piece of advice I received was to take some time to observe and ask why, before suggesting improvements.</p><p>New joiners bring a fresh pair of eyes to a team. There may be things which don’t make sense to us and which we will want to change immediately. This is valuable and important for an organisation’s development. However, there may be some context which is not immediately apparent, or some history behind a particular decision. Understanding this context / history will help us evaluate the issue and better shape our interventions to be more effective.</p><p>I think this is especially important for those of us whose jobs include acting as a Scrum Master. I hope I’m not offending any Scrum purists here, but I do believe that immediately enforcing a version of Scrum that is “by-the-Guide” can be counter-productive and damage the team’s ability to self-manage.</p><p><strong>4.</strong> <strong>Discomfort is a sign of growth</strong></p><p>Something that I feel is not said enough: transitions are tough!</p><p>I’ve definitely found these past 90 days challenging. However, knowing this^ has helped me sit with the discomfort, and take heart that it is likely a sign of growth.</p><p>What has also helped is taking things one day at a time and asking myself — What experiment can I try today? What can I learn today? Over time, I’m hopeful that those daily learnings will snowball into a big difference.</p><p>That being said…</p><p><strong>5.</strong> <strong>Ask for help</strong></p><p>Some discomfort is healthy, but you should not feel like you’re sinking. If you find that you’ve reached an impasse and you’re struggling, please reach out.</p><p>As a poster in our office proclaims, the definition of insanity is doing the same thing over and over but expecting different results. I’m sure you’ll find people in your organisation who can support and help, if you ask for it.</p><p>Resources:</p><ul><li><a href="https://woolly-atlasaurus-7a7.notion.site/Purity-Waigi-Product-Management-1-31c47251dc0d45839a7744d7c45178c9#a539d5ef6de34ae7aace14d914e515f7">Purity Waigi — Product Management Resource Catalogue</a> — Great compilation of resources for the first 30–60–90 days, plus other relevant topics</li><li><a href="https://akshayaag.medium.com/first-30-60-90-day-guide-for-product-managers-6020a25c229f">First 30–60–90 day guide for Product Managers</a> by Akshayaa Govindan</li><li><a href="https://debliu.substack.com/p/make-the-first-90-days-count">Make the First 90 Days Count</a> by Deb Liu — I used this lightweight template to draft my 30–60–90 day plan</li><li><a href="https://youtu.be/YLsxHa1dhSw">Overcome imposter syndrome and accelerate your career | Julie Zhuo (Sundial, Facebook) </a>— Shared by <a href="https://medium.com/u/db7cdbf5c7ff">Steven Koh</a>, I found this podcast to be so very insightful. There’s so much to unpack here, but especially relevant to this topic (point #4) is when Julie talks about how being in this uncomfortable position, where you’re going through a lot of change that is outside of your comfort zone, is also what forces you to do the work, learn, and become better.</li></ul><p>That’s been my first 90 days at GDS, and I’m looking forward to the next 90 days. If you’ve gone through a similar experience and have more tips / advice for navigating these transitions, please leave a comment down below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7e893b16038" width="1" height="1" alt=""><hr><p><a href="https://medium.com/govtechsingapore/the-first-90-days-reflections-on-onboarding-into-a-new-organisation-team-and-role-f7e893b16038">The First 90 Days — Reflections on Onboarding into a New Organisation, Team, and Role</a> was originally published in <a href="https://medium.com/govtechsingapore">GovTech Singapore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>