Project

General

Profile

Feature #17176

Think about how to implement and live a feedback culture in the project

Added by u 25 days ago. Updated 23 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Project
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

A feedback culture is, essentially, a workplace culture that is focused on honest feedback between workers, regardless of their place in the project. One, among many benefits, is to improve communication, openness and trust.

As we do not have such a culture, and I'm not talking about technical feedback here, it might be interesting to try and implement this into our everyday and regular communications. e.g. in each team after every meeting, or every day at a sprint have a moment where workers can give each other feedback about what is going well and what needs improvement.

Maybe creating this ticket on Redmine is not the exact right place to talk about this, but maybe it's a start.


Related issues

Related to Tails - Feature #16640: Set up a process for continuous HR & management 1-to-1's Confirmed

History

#1 Updated by intrigeri 25 days ago

  • Category set to Project

Hi (again :)

Thanks for putting this explicitly on our collective radar. I appreciate that you're doing it openly (while I have the tendency to think about this sort of things alone or privately, and to implement incremental changes without much announcements, which has some advantages… but not only — both for me and for the project).

Maybe creating this ticket on Redmine is not the exact right place to talk about this, but maybe it's a start.

IMHO:

  • Redmine is not a good place to have discussions in general, let alone one like this (no threading, no way to tell which sub-thread has reached a conclusion or not, etc.).
  • Redmine is the best place we have to track what discussions we need to have (possibly elsewhere). But so far we had no way of classifying such tickets and I'm afraid that this one will get lost in the middle of the currently 642 tickets-without-category that we have: without knowing that it exists, and remembering some matching search string, there's no way to find it. It turns out that all categories we had so far were about the Tails product and none were suitable for issues about the community/workplace that builds this product. So I've just created a "Project" category and its custom query. I'm of course open to switching to different semantics or terminology: what matters to me is to have some way to see the list of such tickets, so more than 2-3 people can find them.

#2 Updated by u 25 days ago

intrigeri wrote:

Thanks for putting this explicitly on our collective radar. I appreciate that you're doing it openly (while I have the tendency to think about this sort of things alone or privately, and to implement incremental changes without much announcements, which has some advantages… but not only — both for me and for the project).

Yes, much of this work has been done invisibly in the past.

Maybe creating this ticket on Redmine is not the exact right place to talk about this, but maybe it's a start.

IMHO:

  • Redmine is not a good place to have discussions in general, let alone one like this (no threading, no way to tell which sub-thread has reached a conclusion or not, etc.).

Fully agreed.

  • Redmine is the best place we have to track what discussions we need to have (possibly elsewhere). But so far we had no way of classifying such tickets and I'm afraid that this one will get lost in the middle of the currently 642 tickets-without-category that we have: without knowing that it exists, and remembering some matching search string, there's no way to find it. It turns out that all categories we had so far were about the Tails product and none were suitable for issues about the community/workplace that builds this product. So I've just created a "Project" category and its custom query. I'm of course open to switching to different semantics or terminology: what matters to me is to have some way to see the list of such tickets, so more than 2-3 people can find them.

Thanks! That is great.

#3 Updated by u 25 days ago

  • Type of work changed from Discuss to Research

Changing the type of work to Research, as I think there needs to be some more thinking done before a proposal to discuss can be built.

#4 Updated by u 25 days ago

  • Related to Feature #16640: Set up a process for continuous HR & management 1-to-1's added

#5 Updated by intrigeri 23 days ago

  • Status changed from New to Confirmed

FTR I'd like to try this during (at least the next) sysadmin team meeting, so I've added this to the agenda:

Feedback round
==============

We could try to explicitly make space in our meetings to give each
other's feedback. For background, see
https://redmine.tails.boum.org/code/issues/17176

This could happen either at the beginning of the meeting or at the
end:

 - Doing it at the beginning has the advantage that we're less tired,
   and thus in a better shape to nicely give and receive
   constructive feedback.

 - Doing it at the end of the meeting has the advantage that we can
   also give each other feedback pertaining to the meeting itself.

#6 Updated by u 23 days ago

Let us know how it goes!
This could be helpful: https://www.seedsforchange.org.uk/feedback.pdf

Also available in: Atom PDF