Notes from session w/Sean Squires and Lincoln Demaris
- Case Study: Knowledge For The Field - one of several systems for KM at Microsoft, repository of high-quality of field-ready content, intitial phase focused on content publishing and discovery
- 80K Microsoft employees might access the system to learn about a product, 45K sales/marketing/field might want to know how to sell the product, 1K subject matter experts might use the system as well
- Challenges/key takeaways: user experience (tough to cut across different processes), collaboration (different groups manage information differently), Info Discovery (search results are difficult to refine and validate)
- Wikipedia held up as very good KM solution
- Key Component: Publishing Site:
- Pages as storefronts
- Consistent wiki-like user experience
- Implicit structure
Key Component: Document Center
- High-value managed content
- Not a walled garden
- Submissions can come from anywhere
Key Component: Shared Services
- Enterprise consistency, taxonomy and folksonomy
- Content type, metadata, content analytics, social feedback
Planning for on term store for all of Microsoft, one feed store (?)
May have multiple term sets and taxonomies but centralized management and sharing
Demo
- Prototype Site: InfoPedia
- Search results include lots of metadata
- Refinement pane on left side - pulls metadata to be used as filters
- Custom control for Digg-lke voting
- Document center is a stylized content query web part out of the box
- Managed keyword control also shown
- You can use tagged filters relevant for a page to send into the content query web part of show different documents in the doc set based on the page and the tags on the page (if I heard the speaker correctly) - contextual content query then.
- Workflows associated with topic areas that are assigned to pages so participant contributions can be routed to page owner, subject matter expert etc.
Tagging is relied on extensively and works with content query web part - social tags and/or authorized tags - tags drive navigation, discovery, etc
Pages as storefronts vs nested subsites
Wiki editing and social features can help with user participation and contributions within a governance model to have contributions checked.
Document Center is strictly managed
Demo
- Document set can be thought of as a better folder model for collections of content
- Content Organization - folders, rules, poilicies
- Can now attach policies to location - location-based retention
Content Organizer ensures permissions and policies applied correctly
Overall impression: very well done for content-centric KM approaches.
Loading comments...