Add views to TechNet Wiki pages
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.
In Margriet's blog post, she mocks up with this feature might look like: http://blogs.technet.com/b/wikininjas/archive/2012/07/11/wiki-statistics-as-a-future-feature.aspx
Regarding the views... All versions. Per revision is just a bonus. Ultimately people would want a "Statistics" tab (like Tord mentioned) with numbers and a line graph that shows views increase and decrease, aligned to edits. But really, the bare minimum is to just put the views on the page. Currently you can track Blogs views, Forum views, and Gallery downloads, but you can't track Wiki views. This feature is expected now because it's in other tools (Blogger, YouTube, Twitter decks, etc.).
So I'd rather just get the basic views feature ASAP and then check business value on the full Statistics tab. For example, YouTube always had views, but it took a few years before they added their statistics tab.
AdminModerator (Admin, Microsoft ) commented
Ed, you are right, we cannot move items between sections, can you please re-post at: http://communityninjas.uservoice.com/forums/149974-technet-wiki
All: The issue is - what view number would you want displayed? The Page Views (PV) for the "currrently displayed version"? or the total PVs of "all versions"?
Note that tracking the SEPR of the wiki article would give the same data: if the wiki article title is *not* on the first page or two of search engine rank pages for a given number of related top search queries, does it matter what the PVs are?
Tord G. Nordahl commented
This would be awsome to have built into the article, maybe a new pane to the top where you have "edit" history" and maybe a new one named "statistics" ?
Here are two scenarios where this would come in handy:
- Microsoft Technical Writers (assess the impact of their contributions)
- MVP awardees (to report out on what they've been doing more completely)
Ha! Apparentely there's a TechNet Wiki section, where this belongs. Apparently you can't edit or move the ideas in this tool.