Hello,
Problem statement: Various movement processes, programs, often request feedback, suggestions or comments. In the process, they get feedback and questions through different channels such as mailing lists, office hours, talk pages etc. Now, sometimes it remains unclear what happens next. Sometimes it remains unclear if a requested feedback is taken/incorporated or not (and why?). And sometimes feedback and questions remain just unanswered. Possible solution: "Feedback was requested" and "Feedback is received" — now this loop needs to be closed. Closing the loop in a consultation process is important. (narration below)
A technology policy analyst spoke at Wikimedia Summit 2019. I'll quote a part from the video[1]. He told— "The core of responsive regulation is community consultation processes. However, closing the loop on the consultation process is critical, otherwise participants feel that they have wasted time providing feedback. For example, the Indian telecom regulator first issues a consultation paper. Then solicits the first round of feedback, then solicits a second round of counter comments, then they hold round tables, and, finally, they issue the recommendation or the regulation. But when they do that, they make sure they close the loop. They provide reasoned explanations for why suggestions were rejected... ..."
When any important major Wikimedia process comes forward and asks for feedback or suggestions, there might be different results such as feedback/suggestion accepted, partially accepted, rejected, not actionable, kept on hold etc. However, closing the loop in this process is important, example: "we received "this" feedback and this feedback was not incorporated or was not actionable "because _______"..."
How can it help? "Closure of a feedback loop" can: a) help to understand how a feedback/suggestion was taken/noted, and what were the observations? b) show respect to the people and their feedback, and most possibly encourage people to share feedback and ask questions in the next consultation process c) eliminate duplication. If a particular feedback is taken to a conclusion, several other people don't need to suggest the same thing in future.
I am posting this as an individual, and over-all this is a process-related suggestion/feedback. If the major Wikimedia processes or programs soliciting feedback or questions consider this, I think that will be very helpful. Regards, User:Titodutta
References [1] Video: https://commons.wikimedia.org/wiki/File:Wikimedia_Summit_2019_-_Key_listener... (quoted timestamp: around 3:40 of the video). Used as a general citation from resource available on Wikimedia Commons
It would be great if each person who posts the first post in a thread asking for feedback, closes the loop. Request all our Indian Wikimedian friends to adhere to this best practice. :)
AshLin
Hey Tito,
Just wanted to say that we (the Community Relations Specialists at the Foundation, who often ask for feedback around the technical development of the wikis) appreciated this reminder. Thank you.
//Johan Jönsson --
On Wed, Dec 22, 2021 at 12:02 AM Tito Dutta trulytito@gmail.com wrote:
Hello,
Problem statement: Various movement processes, programs, often request feedback, suggestions or comments. In the process, they get feedback and questions through different channels such as mailing lists, office hours, talk pages etc. Now, sometimes it remains unclear what happens next. Sometimes it remains unclear if a requested feedback is taken/incorporated or not (and why?). And sometimes feedback and questions remain just unanswered. Possible solution: "Feedback was requested" and "Feedback is received" — now this loop needs to be closed. Closing the loop in a consultation process is important. (narration below)
A technology policy analyst spoke at Wikimedia Summit 2019. I'll quote a part from the video[1]. He told— "The core of responsive regulation is community consultation processes. However, closing the loop on the consultation process is critical, otherwise participants feel that they have wasted time providing feedback. For example, the Indian telecom regulator first issues a consultation paper. Then solicits the first round of feedback, then solicits a second round of counter comments, then they hold round tables, and, finally, they issue the recommendation or the regulation. But when they do that, they make sure they close the loop. They provide reasoned explanations for why suggestions were rejected... ..."
When any important major Wikimedia process comes forward and asks for feedback or suggestions, there might be different results such as feedback/suggestion accepted, partially accepted, rejected, not actionable, kept on hold etc. However, closing the loop in this process is important, example: "we received "this" feedback and this feedback was not incorporated or was not actionable "because _______"..."
How can it help? "Closure of a feedback loop" can: a) help to understand how a feedback/suggestion was taken/noted, and what were the observations? b) show respect to the people and their feedback, and most possibly encourage people to share feedback and ask questions in the next consultation process c) eliminate duplication. If a particular feedback is taken to a conclusion, several other people don't need to suggest the same thing in future.
I am posting this as an individual, and over-all this is a process-related suggestion/feedback. If the major Wikimedia processes or programs soliciting feedback or questions consider this, I think that will be very helpful. Regards, User:Titodutta
Thank you Johan Jönsson.
Hello, In 2021 we have seen several important major processes such as board election, grants strategy relaunch, human rights policy, community wishlist etc, Some of these and other processes asked for and received feedback and questions.
This is important to close the feedback loops with rationale, as much as possible. Otherwise the number of unclosed feedback/questions thread keeps on increasing.
In my opinion, there might be several ways to take this forward: a) General method: Attempt to work on this. Be more watchful in future. b) Stop, and work on the process: Please do not initiate another major process soliciting feedback, until there is a working mechanism in place. c) Case-by-case attention: Every major process while soliciting feedback can add a section in the same email/post explaining how the feedback will be treated or the loops will be closed. While soliciting/giving feedback, it would be good to inform/know how feedback will be tracked or treated.
ইতি,/Regards টিটো দত্ত/User:Titodutta (in volunteer capacity) (মাতৃভাষা থাক জীবন জুড়ে)
বৃহস্পতি, ২৩ ডিসেম্বর, ২০২১ তারিখে ৭:০৬ PM টায় তারিখে Johan Jönsson < jjonsson@wikimedia.org> লিখেছেন:
Hey Tito,
Just wanted to say that we (the Community Relations Specialists at the Foundation, who often ask for feedback around the technical development of the wikis) appreciated this reminder. Thank you.
//Johan Jönsson
On Wed, Dec 22, 2021 at 12:02 AM Tito Dutta trulytito@gmail.com wrote:
Hello,
Problem statement: Various movement processes, programs, often request feedback, suggestions or comments. In the process, they get feedback and questions through different channels such as mailing lists, office hours, talk pages etc. Now, sometimes it remains unclear what happens next. Sometimes it remains unclear if a requested feedback is taken/incorporated or not (and why?). And sometimes feedback and questions remain just unanswered. Possible solution: "Feedback was requested" and "Feedback is received" — now this loop needs to be closed. Closing the loop in a consultation process is important. (narration below)
A technology policy analyst spoke at Wikimedia Summit 2019. I'll quote a part from the video[1]. He told— "The core of responsive regulation is community consultation processes. However, closing the loop on the consultation process is critical, otherwise participants feel that they have wasted time providing feedback. For example, the Indian telecom regulator first issues a consultation paper. Then solicits the first round of feedback, then solicits a second round of counter comments, then they hold round tables, and, finally, they issue the recommendation or the regulation. But when they do that, they make sure they close the loop. They provide reasoned explanations for why suggestions were rejected... ..."
When any important major Wikimedia process comes forward and asks for feedback or suggestions, there might be different results such as feedback/suggestion accepted, partially accepted, rejected, not actionable, kept on hold etc. However, closing the loop in this process is important, example: "we received "this" feedback and this feedback was not incorporated or was not actionable "because _______"..."
How can it help? "Closure of a feedback loop" can: a) help to understand how a feedback/suggestion was taken/noted, and what were the observations? b) show respect to the people and their feedback, and most possibly encourage people to share feedback and ask questions in the next consultation process c) eliminate duplication. If a particular feedback is taken to a conclusion, several other people don't need to suggest the same thing in future.
I am posting this as an individual, and over-all this is a process-related suggestion/feedback. If the major Wikimedia processes or programs soliciting feedback or questions consider this, I think that will be very helpful. Regards, User:Titodutta
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/... To unsubscribe send an email to wikimedia-l-leave@lists.wikimedia.org
wikimedia-l@lists.wikimedia.org