Constant loop of quantitative and qualitative feedback in a Sales Enablement portal

My blog post ‘How the metrics of a Sales Enablement application help you to save sales people even more time’:

Today, I had a look at the usage metrics and statistics report gathered at a large enterprise that recently launched the BizSphere Sales Enablement application to replace more than 35 intranet portals. What I love about the report is that it not only tracks which content sales people view, download, rate (with up to 5 stars) or comment on (We actually also display all of the above in the front-end to show sales people where the good stuff is.), but it also tracks what they were not able to find. An anonymous list of all search queries that were punched in comes with the number of actual results that were displayed. That way the owners of the Sales Enablement application at our customers can take a look at all search queries that led to zero results and specifically address what must be a huge frustration for sales people who are trying to prepare a customer meeting.

Constant loop of quantitative and qualitative feedback lets you improve the experience

Knowing which way people search, what they are looking for, and to analyze whether the content does actually exist or still needs to be created is very insightful. Not only does it direct the content planning process (to invest marketing dollars only for content that will actually be used), but it also helps to focus on the important topics when optimizing your texts and their tags for indexing by the search. What I mean by this is that a search term that led to zero results can be added – visible or invisible – to the content that would had been the perfect match. An example from one of our early customers – Nortel – would be frequent searches for CS1k with the expectation to find content for the product CS1000. It is just fair enough that people search the way they speak and analyzing the metrics and statistics helps you to improve their search experience.

Enterprise 2.0 style collaboration

Besides the quantitative things to look at, you also have the qualitative feedback in form of comments under each piece of content. When people start to…

  • comment on a white paper why it did not resonate with customers in a specific industry vertical,
  • add competitive insight from the field on an internal presentation,
  • applaud or criticize the authors
  • and help each other with lots of comments etc…

…then each piece of content has its own blog.

A word, that is not an official term but keeps on showing up in these comments or in the log files mentioned above, can be added as an alias of a product/service/solution, region/country or resource/document type.

The real Enterprise 2.0 style collaboration starts to happen when your Sales Enablement application allows your employees or even your channel partners to share their own documents or links which they found helpful. When everything can be accessed from one place and is marked as ‘peer contribution’ or as ‘content approved by marketing’, then there might be a chance to ensure that everyone is always using the latest version and does not waste time emailing people for it.

The report – this ‘one place’ should show in real-time – tells you who contributed the content that gets a lot of love and the collaboration around it might reveal insights of the kind only employees touching the customer accounts gather and the marketing department usually finds out about late.

Enterprise 2.0 from a Sales Enablement point of view

Advertisements

3 thoughts on “Constant loop of quantitative and qualitative feedback in a Sales Enablement portal”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s