From Ning here (http://social.technet.microsoft.com/Forums/en-US/tnwiki/thread/0a066500-a72e-4a0b-9709-bc7c74a7bca8):

1. Evaluate the Discoverability of the solution

An issue is on top CSS Or Community list.
The community PM gets the estimated "# of impacted customers" or total views of the community thread, and requested a Wiki as the quick solution.
The community PM track the Wiki Views, to understand whether the impacted user actually find it.
Based on the result, the community PM decide whether additional optimization (Blogging, KB, Sticky notes, DL/MVP awareness, Keyword) is needed.
For Wiki, the discoverability is the top issue compared to online help/KB, the view # provide important data on evaluating how a wiki is **** on this.

2. The view trend helps to evaluate the impact of the issue, and whether additional action is needed from the product team

A wiki is provide as a workaround for a product issue
The volume of the wiki continue to go up, meaning a lot user is impacted and have to utilize the manual workaround
Community PM can use this data to request further code fix (hotfix, service pack fix etc.)
After the code fix is published, the wiki view should drop down, and provide confirmation that the issue is actually resolved.

3. The view trend helps to understand the impact of the issue, and whether additional action is needed from the community

A wiki is provide in response to a top community ask (FAQ, How to, etc)
The volume of the wiki continue to go up, meaning a lot user is impacted and have to utilize the trouble shooting skills or understand the background
MVP and community can use this data to prioritize their contribution, between provide new wiki and enhance existing wiki. (Additional community forum question might needed to clarify why the volume keeps up)
The Wiki is modified to improve the effectiveness and simplicity.
We want to provide guidance to community on where they should spend their time. Wiki view is one data point of the top utilized solutions.

Contributors cannot sustain without management buy-in, which is obtained by showing impact for effort. Currently, the integrated profile shows only the last N entries in the activity stream. The activity stream should function as a "log" that shows *ALL* activities, so that contributors can pull metrics and analyze/report results. If web page loading time is a factor, put a limited of N items per page on it, and allow anyone who desires to paginate back to the beginning of the list. Beyond this, it would be helfpul of the page views that drive the achievements were displayed here beside the page URLs in the acticity list display.