I think I understand what you are saying, that seems like a very good idea, in fact I like that approach so much I think I may end up implementing it myself into my company!
I’m just tossing some ideas around, I’d like to work with you on this, so that we can design a Mattermost setup that best fits your needs.
I had some thoughts that ran across my mind, and several ideas on how one could (maybe?) implement something to suit the needs you are looking for. I’ve had several different ideas on how this could be done, here is an outline in a “workflow” type-format. The thought in this, to me, is that starting from the top, and going down, the user responses are getting fewer, while at the same time getting longer, in a sense.
Mattermost Public Team 1 - General feedback/brainstorming channel, individuals who post in the main channel are asked to provide a two to three sentence, broad overview of the topic of change, and what they would do differently/how they would like to see things change.
Other users have the ability to read through these messages, and utilize reactions (such as potentially a simple up arrow and down arrow, to indicate if they support/agree with the subject matter, and maybe a third reaction to indicate interest in exploring this topic further)
For proposals in the above channels/teams, a set number of reactions in favor of additional discussion and or development is set. When a proposal reaches this number of reactions, it gets its own channel, to grow the topic through conversation, and ideas. This would be a great time to integrate with GitHub, which allows you to create and manage issues directly from the Mattermost chat, which will allow you to note important development or topic matter issues to another location where it can be triaged and tracked, as well as monitored in the server. In addition to the aforementioned, to be inclusive of the possibility that a venture is a dead-end, creating an additional channel for the topic that contains a message, with reactions, simply asking if the involved members still are persuing development and if it is still possible (or something along those lines) could allow you to quickly manage with simple visualizations the status and activity of a potentially large amount of topics.
As the topic/project nears solution, a private channel/group for the administration and or logistical/fine technical details could be added in addition, to enable the core group of developers to communicate effectively without their messages being rapidly lost in a channel with a large number of people communicating very rapidly, etc. Once the project has been completed, or the decision has been made to make the area public, you can always change the channel to be publicly viewable, of course.
My thought with this is that this method could be duplicated across several teams, as well as in a company-wide team. I say this in the sense that, as far as organization goes, it may be helpful to have a section for IT, a section for logistics, a section for the machinists or software designers, etc, as well as at least one “general” company-wide discussion group.
I personally developed this idea in the mindset that even if an employee is not particularly vocal with their thoughts, they are still enabled to provide feedback and make a direct impact to the movement of a project or idea simply based on the reaction indication that they select on a specific topic. This, to me, seems like it would help promote company-wide inclusivity, as well as the ability for all to provide feedback on all topics.
Getting staff to the correct channels can additionally be further automated with the Mattermost Welcome Bot which is free to use.
What do you think of this idea, does this sound at all along the lines of what you are envisioning? If you see things you would change, please don’t hesitate to let me know, I value your feedback and am excited to find a solution!