Hi Irene,This is a really great question that everyone in the company should be thinking about. Jarren makes some excellent points about both the value you will receive and the resources you'll need to commit.I've attached two diagrams that I have used over the years to help teams understand an embrace the VOC model. This is very important when you are designing a community. You and your leadership team will need to be aligned with the following:1) Why do we feel we need a community?2) What is the objective of our community program? How will we measure our success?3) What persona are we designing for (e.g. why type of customer, what type of company, other parameters?) (Hint: don't try to be all things to all people.)4) What content needs to be produced to support the community?5) How will we manage the community? (Who owns it? Who are the internal stakeholders? Who else (other than the owner) will commit to providing materials and guidance?If you can figure out the answers to these questions first, then the questions about technology will be easier to solve.One final thought: no community will survive without an owner and a curator. Just because you use SLACK as a tool does not mean that anyone will use it (they won't know how, why, or when). However, if you have a curator who poses a question each week to the community, you will spark interest and discussion.I am not a community manager, per se. However, my role as a Customer Advisory Board facilitator has allowed me to participate in many discussions between company leaders and their customers regarding the value of such a community. Happy to share notes if you'd like to connect 1:1.Hope this is helpful.