diff --git a/.gitlab/issue_templates/Product Designer Onboarding.md b/.gitlab/issue_templates/Product Designer Onboarding.md
index 1a6dc8eca2db0fa4765451d8fee885bb3dd073a9..c4106838c2e2e124a5fccef92360e22a907ab960 100644
--- a/.gitlab/issue_templates/Product Designer Onboarding.md	
+++ b/.gitlab/issue_templates/Product Designer Onboarding.md	
@@ -75,7 +75,11 @@ To start off with, let's learn about and connect with the UX team here at GitLab
     1. Your PTO dates should now automatically sync with that calendar.
 - [ ] Read the [Product Design workflow](https://about.gitlab.com/handbook/product/ux/product-design/#product-design-workflow) which is important to get to know
 - [ ] Read the [design project and documentation](https://gitlab.com/gitlab-org/gitlab-design/blob/master/README.md)
-- [ ] Become familiar with [Pajamas](http://design.gitlab.com), which is our design system where we document all product design decisions and things to help us make those decisions, like [personas](https://about.gitlab.com/handbook/product/personas/).
+- [ ] Become familiar with [Pajamas](https://handbook.gitlab.com/handbook/product/ux/pajamas-design-system/), which is our design system where we document all product design decisions and things to help us make those decisions. Parts of the design system can be accessed through different platforms, with the aim to consolidate these further.
+   - [ ] [design.gitlab.com](https://design.gitlab.com) includes foundational design decisions and guidelines, component documentation and examples, and product design decisions and tools.
+   - [ ] [gitLab-ui](https://gitlab.com/gitlab-org/gitlab-ui) includes deeper information about component development and implementation, including a hosted [storybook](https://gitlab-org.gitlab.io/gitlab-ui/) instance.
+   - [ ] [gitlab-svgs](https://gitlab.com/gitlab-org/gitlab-svgs) includes our SVG Assets and the corresponding pipelines to create all of our SVG sprites for our icons, these can also be browsed using the [GitLab SVG Previewer](http://gitlab-org.gitlab.io/gitlab-svgs/).
+   - [ ] [Pajamas UI Kit](https://www.figma.com/files/project/3802635) includes Figma assets and styles for creating static design mocks. Updates match the company milestone cadence and are documented in the [release notes](https://design.gitlab.com/get-started/uik-release-notes). 
 - [ ] Around your third week, check in with you UX buddy about shadowing them for their daily UX activities. This is a good primer and a way to get more familiar with product designer workflows. You will serve as a second opinion and be included in meetings.
 
 ## Staying informed :mega:
@@ -182,6 +186,7 @@ Aside from adjusting towards the async workflow of GitLab please try to see if y
 - [ ] Once you have access to the GitLab organization in Figma, browse some of the teams and projects to see how we design in Figma. Check out the [GitLab Figma plugin](https://www.figma.com/community/plugin/860845891704482356) to upload designs directly from Figma to GitLab issues.
 - [ ] The [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit) allows you to install GitLab's development environment on your computer. This will enable you to test certain features that aren't available in production. It is highly recommended that you install the GDK and try checking out a branch to see how it looks running locally. Your UX buddy can help you with this and the `#gdk` Slack channel is there for you if you need help.
     - [ ] If you are not used to maintaining a local development environment like the one mentioned above, you can also use the GDK in [Gitpod](https://gitpod.io). This allows you to make/review changes exclusively in the browser. If you prefer this, read the [instructions on how to use the Gitpod GDK](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/gitpod.md) and watch this video that walks you through [how to review merge requests both locally as well as in Gitpod](https://www.youtube.com/watch?v=M7b19Dq-1tw&t=12s). The `#gitpod-gdk` Slack channel is here for you if you need help or have any feedback.
+    - [ ] Discuss with your group if you need a tier license for your GDK install.  If so, follow the steps in [Working in Gitlab EE](https://about.gitlab.com/handbook/developer-onboarding/#working-on-gitlab-ee-developer-licenses) to request a license.
 - [ ] Create your first [UX Scorecard](https://about.gitlab.com/handbook/product/ux/ux-scorecards/) documenting the current experience of a common job. Make sure to discuss this with your UX buddy beforehand. They can give you ideas and point to particular product areas that haven't been evaluated yet.
 - [ ] Collaborate with your UX buddy and make a change to this [onboarding template](https://gitlab.com/gitlab-org/gitlab-design/-/blob/master/.gitlab/issue_templates/UX%20Onboarding.md) to improve the onboarding experience for future GitLab team members.