A borrow is used when a team member is shifted from one team to another temporarily or assisting other teams part-time for an agreed-upon period of time.
There are two Borrow request options. Choose the one that makes the most sense for your situation.
Before a borrow takes place, make sure to have it approved by the appropriate director (Product Design, UX Research, or Technical Writing).
Utilizing these issues will help us understand the frequency and duration of borrows throughout the year. Tracking occurs by appending the
UX Borrow label to each issue request.
We conduct an annual team skills analysis based on a process recommended by Nielsen-Norman.
This allows us to see our strengths as a team and to identify team trainings that would benefit a large portion of the team, help us identify strengths we'd like to add when hiring new team members, and inform individual team member's growth plans. It can also act as a resource for matching mentors and/or design pairs.
Note: These are also in the template, which is the SSOT.
Whenever you need to update the area of the product a team member is supporting, such as on the Product Categories page, you'll generally need to update or review the following pages and projects:
For section-level updates you'll want to do the following:
For group-level updates you'll want to do the following:
For all updates you'll want to confirm that the person you've updated has a name reference in the category names file, otherwise it won't render correctly on the handbook page it's being called on.
In the GitLab team retrospective group, find the team members section and group, and add and remove team members there. This step is required so that confidential issues can be seen by team members.