You may have heard you can roll out a community platform in just a few days. What you have heard is 100% true.
But the platform is just the tip of the iceberg of successful community investment. The other pieces – even more important than the digital home itself – will take several weeks or even months. Done correctly, however, these are the most rewarding parts of a community-building journey.
I’ve learned this lesson the hard way, through small failures and big disappointments in my work, and then by hand-holding clients through the process so they do not make the same mistakes.
No matter what type of organization you work for, there is a major difference between the brands that say they want to invest in community and those that actually succeed in doing so.
Here are some of the most common mistakes that marketers make when launching a community:
With this guide, you’ll walk away prepped and ready to launch a marketing-focused community that is both valuable and exciting, that is not extractive and that helps you sleep better at night knowing you made something the world needs.
What real problems does your marketing team face right now? Start with a hypothesis of the top three (ranked) problems and challenges. Begin there.
If you’re stuck, try thinking along these lines, often used by marketing teams:
Remember, this is just a hypothesis. If you need to get approval on these priorities before moving ahead, give it another two weeks before you can get all the stakeholders in the same (Zoom) room to collaborate.
If you’re anything like me and the marketing teams I’ve worked with, you’ll be relieved to know you do not need to conduct months of research. Instead, start by listening to a few key people. Think about the different potential groups of people you would like to join your community. Then talk with at least 4-5 of the group that you think is most likely to be served by the community. Have a genuine conversation, and get to know this person.
If you feel overwhelmed by this, it’s okay to slow down. It is far better to spend this upfront time hearing, in their own words, people’s struggles, challenges, and needs. If you skip this step, you’ll end up redoing your work after investing based on assumptions.
Now that you understand potential members, it’s time to bring their needs together with what your business priorities are. Here are some examples:
Find ways that your members’ needs can also serve your organization. It’s much easier than you would expect. For instance:
Ideally, you do this phase of the project in three chunks:
While this is the ideal state, it is not always realistic. Go with what works in your organization and what is most efficient.
Now the tactical work begins. You’ll need to answer these questions:
You will spend about four weeks here, though it could be fewer if you use tools you and your team are familiar with, or if you have done prior tech research. This phase could be significantly longer if you need to go through an advanced procurement process.
If you are working with vendors, much of the heavy technical lifting will begin to move off of your plate so you can begin to plan community programs, train new hires, and set up operations.
In addition, create a list of the 10 or so folks you would like to have as beta testers (it’s a great idea to invite those you listened to earlier!)
If you are not working with outside vendors, plan at least two weeks to gather the team you need and plan the work ahead. The beta testing phase will likely be a bit more bumpy for those working with in-house teams, but the initial investment can pay off in the long-term as your team will be familiar with the tools.
Launch to a beta test group first (sometimes these are the same as your Founding Members). This should be a group of trusted collaborators whom you know will be involved in the community once it launches officially. Work with them over a few weeks to roll out changes, gather insight, and give them a peek behind the curtain into how you’re setting up the community.
At this stage, you should gather extensive feedback from these beta testers and implement the changes to the technology and management processes.
After you’ve gathered enough insight and feedback, you’ll focus on making big changes. The community should go from rough beta (where bugs and dead-ends and lackluster copy are acceptable) to a more polished community experience, complete with at least a basic onboarding and welcoming process.
Altogether, this process from idea to public launch takes about 4 months – if you move quickly.
So, yes, you may launch the platform itself in as little as a few hours. But you will be unsatisfied with the results until you’ve completed the above steps.