Providing feedback to team members on work activity is a critical step to build a healthy dev culture. Botany is unique in collecting feedback from team members on work actions at the point that they occur. This is to build a responsive, transparent, and open work environment. We refer to this functionality as "Feedback Endorsements." This feedback process gives praise, insight, and increased motivation to the team members involved.
For example: Botany for example allows teams to be able to provide feedback on code or code reviews.
These can be either from tags that natively have pre-defined in our solution and custom ones that might be important to your team. (see scenario below)
As part of the Botany's conceptual model for software engineering teams, Botany can attribute points ("XP") from these collected tags to attribute them to the team's corresponding 'dimensions' within any related job responsibility. (Examples: "Writing Code," "Code Reviews," "Learning & Development," etc.) These tags add in specified points for these activities along with other points collected from source system interactions.
As a concrete example, endorsing with unblocked me (+5) from the tag list above, will award +5 points for the Participation dimension of the Reviewing Code area.
For someone doing a code review, it can be confusing to be asked to "give feedback" to a change author.
A code review is feedback, ideas, suggestions for the changes being reviewed.
Botany's feedback/endorsements are to thank/give praise/props/tags for the changes made.
Change authors also have an opportunity to endorse/thank code reviewers for their reviews.
