Improve Your Partner Community: Applying Feedback

In yesterday’s blog post, we discussed gathering feedback from your partners in order to improve your partner community user experience. Now, in light of Salesforce announcing a preview of the new Partner Central Community in the Summer ’17 release, let’s dive into the data and come up with some solutions on how to address common pain points.

“When I need to download the latest white papers on products, they are always in different spots – there’s no consistency!”

What this says about your community
: Navigation isn’t clear; content is too buried or there’s no pattern to where content lives
Solution: You want your partners to access information efficiently by providing them intuitive navigation that requires minimal clicks. Review what pages are most visited and make sure those are easily accessible from the homepage or with minimal clicks from the navigation. You can often find places to simplify navigation into just a few main categories (Sales, Marketing, Resources, Training, etc.) and make sure the content under each of those is appropriate for the subject matter.

“I keep seeing content and downloads that are for partners in the US, but I’m one of a few partners in France, and I can’t seem to find French information easily.”

What this says about your community
: Your content is not tailored to the right audience and/or you haven’t developed the content for your partner types/regions/languages.
Solution: Review all your downloadable collateral and announcements and categorize them based on partner type, tier, region, language – however you bucket your partners. Utilizing Salesforce Content and public groups is a great way to organize your content and surface it to a set of users. In addition, you can also use page variations in Lightning Communities to show different page content to different profiles.

Originally posted on Perficient’s Salesforce blog, I encourage you to read the rest of the article by clicking here.

Leave a Reply

Your email address will not be published. Required fields are marked *