Collective feedback: how to disclose what everyone is talking about

With regards to the way in which the ABCD is used or not supposed to be used....or how the FSSD is not the SSD framework, or that there is not an SSD package? Or that SSD is more general and what we have learned is a framework? Questions, conversations arise- and there is some miscommunication and feelings of animosity towards the way information feels cryptic or slightly secretive- or not wholly sure of itself? How do we go out into the world and share what has been learned without being fearful of misrepresentation? And with uncertainties flowing throughout- how might one leave the program feeling confident, feeling like a contribution has come from the growing pains of the program? How many will recommend the program now? Is this somehow related to the confusion over these issues?

What is the best way to disclose information that everyone seems to be talking about? How can top management best receive this information to be able to consider its importance and faciliate participation from those who are feeling violated, uneasy, fearful, or angry? What if feedback came from one representative, and the thoughts of the collective were distilled in a clear way to be shared... Is this not practicing transparency? Or is this self-organization? Are the givers of the feedback then disconnected- at which point they turn responsibility over to one? Is it better that each individual share? Is this cumbersome- does each individual need support of his/her fellows to feel that their opinion is valid? What is the vision of success for the group? Why do they want to be heard? Is it that they want to be understood or are they looking to prevent the same from happening to others... or to themselves in the future? What is the delay involved? And how many assumptions are underlying each persons thoughts and opinions? How is it framed in a way that is not blame?