Give feedback to a colleague
What this achieves
Section titled “What this achieves”Feedback is a short written note you send to one colleague about something they did. You choose what kind of note it is, who can read it besides them, and whether your name is attached.
Required role: Any signed-in user.
- Go to Feedback & 1:1s → Continuous Feedback.
- Select Give Feedback.
- Search for the colleague under To and pick them.
- Choose the Type.
- Write the Message. It holds up to 1,000 characters and the screen counts down as you type.
- Choose the Visibility.
- Turn on Send anonymously if you do not want your name shown to the person receiving it.
- Choose a Linked competency or Linked skill if the feedback is about one. Both are optional.
- Add Tags (comma-separated) if you want the note grouped with others like it.
- Select Send feedback.
| Option | Description |
|---|---|
| Praise | Recognize great work. |
| Recognition | Celebrate an achievement. |
| Constructive | Suggest improvements. |
| Suggestion | Share an idea. |
The type is not decoration. It tells the person how to read what follows, and it is the filter everyone later uses to find this note again.
Example: Olivia Bennett telling James Whitfield that a release went well is Praise. Asking him to bring design decisions to the team earlier is Constructive. Sent as the same type, the second one reads as a complaint dressed up as a compliment.
Visibility
Section titled “Visibility”Visibility decides who can read the note besides the person you sent it to. It starts on Private.
| Option | Description |
|---|---|
| Private | The narrowest setting, and the default. The feed marks the note Private. |
| Manager visible | The note carries a Manager visible marker in the feed. |
| Public | The widest setting. Notes sent as Public carry no visibility marker in the feed. |
Choose this before you write, not after. It is the difference between a note that stays between two people and one that becomes part of how a third person understands your colleague.
Example: Sophie Clarke sending Tom Hargreaves a Constructive note about a missed handover keeps it Private. The same note set to Manager visible puts a criticism in front of his manager, which is a different act with a different effect on him.
Sending anonymously
Section titled “Sending anonymously”Send anonymously replaces your name with Anonymous for the person receiving the note, and in the team feed a manager reads. You still see the note in your own Given list, so you can tell which anonymous notes were yours.
Be careful with anonymity on a small team. A note that only three people were placed to write is not anonymous in any way that matters to the person reading it, whatever the screen says.
Example: an anonymous Constructive note to Daniel Okonkwo about last week’s forecast meeting narrows to the handful of people who were in it. Anonymity hides a name, not a context.
What you cannot do afterwards
Section titled “What you cannot do afterwards”There is no way to edit a piece of feedback and no way to withdraw it. Once you select Send feedback, the note stands as written, at the visibility you chose, and the person can read it.
Read it back before you send it. That is the only correction the product offers.
What happens next
Section titled “What happens next”The note appears in the recipient’s Received list, where they can Acknowledge it. It appears in your own Given list. Where you linked a competency or a skill, the note is attached to it, and the feedback becomes part of the running record a review can be argued from rather than a message that disappears.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved