You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Process:
The buddy, the contributor or HR (Nico) will ask for feedback in the governance channel with the link
If HR sees there are few or no responses at all, HR will ask the Contributor and Buddy who are the top 3 contributors they closely work with, then ask feedback from the top 3 through the GC Problem:
We get less responses because not everyone fills out the Contributor Feedback form when @Unicorn is tagged Proposed Solution:
We create a Discord channel wherein the contributor will tag the top 3 contributors or more they have closely worked with and ask feedback from them (similar to the Praise format)
Example: /getfeedback from @Heather@freshelle@ahmad
Then a bot will DM the tagged persons to fill out the feedback form saying like “Hey @user, this contributor wants to get feedback from you etc etc. Fill out here - [link]”
The text was updated successfully, but these errors were encountered:
Reminding Peer Feedback Forms
Current Process:
The buddy, the contributor or HR (Nico) will ask for feedback in the governance channel with the link
If HR sees there are few or no responses at all, HR will ask the Contributor and Buddy who are the top 3 contributors they closely work with, then ask feedback from the top 3 through the GC
Problem:
We get less responses because not everyone fills out the Contributor Feedback form when @Unicorn is tagged
Proposed Solution:
We create a Discord channel wherein the contributor will tag the top 3 contributors or more they have closely worked with and ask feedback from them (similar to the Praise format)
Example: /getfeedback from @Heather @freshelle @ahmad
Then a bot will DM the tagged persons to fill out the feedback form saying like “Hey @user, this contributor wants to get feedback from you etc etc. Fill out here - [link]”
The text was updated successfully, but these errors were encountered: