7. Who will be working on your account?
Too often the people who are front and centre on the website, in the pitch meetings etc are not the people actually looking after your community. It takes a lot of different expertise to run a successful Insight Community. There are different skills involved in having the right technology, recruiting and engaging the members, crunching the data and matching up community activity with company strategy. Whilst all of these roles can’t all be at a senior level…it’s important that the right people are looking after the health of your community. It’s also important to understand the size and shape of the provider. Where are their people based? Do they have a dedicated technical department? Who handles community engagement? How long have people worked there?
8. How does your platform handle segmentation?
Segmentation is a chunky piece of work and Insight Communities are a great way to bring segments to life to different stakeholders, carry out agile research and find out the best ways to tailor your messaging. (for more, why not check out our blog) One platform should be able to house multiple segments in a dynamic way. At a basic level this should mean that you can filter your members on different variables so you can assign tasks to certain demographics etc. It’s also important to have some level of filtering when looking at reporting across the community. At a more advanced level you may want to partition off your community, not only so it looks and feels different to different segments but so that those members get relevant tasks, have discussion rooms with similar people etc. As well as understanding the practicalities of how a platform will handle segments, these types of question can also help you to understand what type of clients a platform provider has, how they can appeal to different types of user etc.
9. Report turnaround
The ultimate success of an Insight Community is how well its adopted within an organisation. A key component of this is in reporting. It can be difficult to plan ahead and think about all the different way you might want to visualise your results. After all it’s not like you can go to your stakeholders and ask them how they’d like to see a report on something which doesn’t exist! Still, it’s good to have an idea of the probable outputs you might want from your community, what file formats you might need or integrations with existing dashboards. It’s also good to understand the likely turnaround to deliver reports. It’s no use if your provider will take a week to respond to a request and then another to complete the report.