These are my session notes from the SharePoint Conference 2009:

• Presenter: Jessica Alspaugh, Program Manager, Enterprise Search Group, Microsoft
• Business problems: Hard to find the right person; People working on redundant work; Enterprise search doesn't adapt.
• Social search is about connecting people to people, as well as, adapting dynamically based on usage patterns and available metadata.
• People search supports phonetic and common nickname match.
• With OCS, SharePoint supports contact card mouse-over.
• View recent content option opens AJAX window containing links to the most recent documents created by the person.
• Knowledge Mining provides keyword suggestions from Exchange 2010. Uses phrases that the person uses often in email. Person has complete control over what items are added to their profile page.
• In SharePoint 2010 colleagues are indexed for ranking purposes.
• Encourage photos. It makes a big difference in enabling interaction. People are less likely to engage with someone who doesn't have a profile photo.
• Microsoft makes it easy to add custom properties to the profile.
• Use the Managed Metadata Service to ensure consistency of terms. Manages metadata fields support dynamic type-ahead suggestions.
• Check out the "Go behind the Search Box" slide for a list of social search features.
• Vanity Search helps users build a profile and create search terms that other people find them in a search.
• Default search order was changed from relevancy to social distance, though you can override.
• If you add a new column and index it, SharePoint Search will automatically create dynamic pivots on the left navigator of the results page.
• If search quality is good, people have more confidence, which leads to increased usage, which further increases search quality.
• Pre-Query Suggestions are built from high click-through queries, and appear dynamically before the search button is pressed.
• Post Query Suggestions appear on the right side of the result set page, under Related Searches.
• Social definitions - "what people are saying about..."
• Check out Social Tag slide - Social tagging will improve search quality.
  

These are my session notes from the SharePoint Conference 2009:

• Presenter: Sean Squires, Program Manager, Enterprise Content Management Group, Microsoft
• Lincoln DeMaris, Program Manager, Enterprise Content Management Group, Microsoft
• Microsoft Case Study: 1TB of knowledge data, ~100K documents. Used across Microsoft.
• "Microsoft isn't doing [their own] internal knowledge management very well."
• Need to balance two opposing forces: Discoverability and authority versus empowering users to contribute. (See KM on SharePoint 2010 Goals slide.)
• Microsoft's KM solution architecture: Publishing site + document center + shared services for content types, managed metadata, analytics, and social feedback. (See Key Elements of Our Solution slide.)
• An explicit page owner is critical. Microsoft assigns owners to specific topic areas.
• Use tagging/categories and the Content Query web part to automatically surface related pages.
• Anyone can edit a page. However, it is stamped "unapproved" until the owner approves.
• The owner receives a task when someone edits their page.
• Documents must be strictly managed, yet may come from anywhere.
• In SharePoint 2010 you can set policies (such as workflow, retention, and permissions) on a folder basis.
• Folders are available to meet business needs. They are no longer needed to get around scalability limitations.
• See the "Wrap Up" page for a good summary of features and takeaways.

Theses are my session notes from the SharePoint Conference 2009:

• Presenters: Gail Giacobbe, Principle Program Management Lead, Microsoft; Ted Pattison, SharePoint MVP, Critical Path Training
• People see wikis as yet another place to store information. They say, "Please don't give me another place!"
• Microsoft used a wiki to enable 400 people to create 15,000 pages of documentation in four months.
• The SharePoint Publishing powers the Enterprise Wiki.
• You can customize the enterprise wiki using SharePoint Designer.
• The relevant content within wikis comes to you through the social networking features of SharePoint's news feed.
• Enterprise wiki: Easy page editing, wiki-linking with auto-complete, cross-brower rich tect editor.
• Features: Page templates (content types & page layouts), Categories (managed metadata), Ratings (web analytics), Tagging and Comments
• Contrary to my earlier understanding, SharePoint 2010 Enterprise Wiki does not include an out of the box table of contents feature. It is something that Microsoft says can be easily customized. (Ugh!)
• The enterprise wiki is designed to be customized and scalable.
• Anything available within SharePoint is easily integrated into the enterprise wiki.
• Leverage SharePoint's compliance (policy, records management) and content management (workflow, approval) capabilities within the wiki.
• You can easily integrate web parts into a wiki page.
• Edit in place, live preview
• Support for "reusable content"
• Insert images and media files directly from your computer. You do not need to upload them to a SharePoint library first.
• When you start a link by typing "[[", a list of all the existing wiki links appear, so you can quickly select the one you want or create a new one.
• The My Site news feed is a critical part of the power of the enterprise wiki, since that is where you are notified of new relevant content and activity of the wikis you visit. (I wonder how you control being inundated with news feed items when you are associated with a very busy enterprise wiki.)
• Working with CSS is "much easier" than it was in SharePoint 2007.
  

The following are session notes from SharePoint Conference 2009:

• Presenter: Daniel Kogan – Sr Program Manager, Microsoft
• Metadata and management content types are really about governance, management consistency and standardization: Is it the same, what is it? Where is it? What happens to it?
• Content types are no longer trapped in a site collection. In SP210, they can apply to the entire enterprise.
• Example: If all blog posts use the same content type, and there is a retention policy applied to the blog post content type, that retention policy will automatically apply to all blog posts across the enterprise.
• Any errors associated with site collection being unable to consume a published content site will be aggregated at the content type hub.
• The Enterprise Metadata Service publishes enterprise content types and the managed enterprise taxonomy.
• You can tag content through the browser, rich Office client, or through custom/3rd party applications.
• The Managed Keyword field dynamically checks existing terms, makes suggestions, and may allow for adding new terms.
• Example: You set a managed metadata field for months of the year, to ensure that the month format is consistent throughout the enterprise. The managed metadata field is created, and associated with the enterprise month default label. You can also associate "other potential labels." Now, when a user is filling out the Month field, they could enter "3" or "Mar" or "March." However, the managed metadata field will ensure that the value is consistent set to "March" across the enterprise. You can also enforce the sort order of metadata so that March is always listed before August.
• Microsoft provides an Excel-based schema that so you can easily import your term set into SharePoint.
• You may distribute ownership of portions of the enterprise taxonomy – term stores.
• The taxonomy hierarchy is available in the column filtering dialog.

Session notes from SharePoint Conference 2009:

• What do end-users care about? Personalization, easy access, ease of use, clear objectives, and management buy-in.
• Think about adoption strategies from the beginning and throughout a social computing initiative.
• Identify and leverage champions.
• Engage HR, legal, compliance, and security.
• Don't force people to use social computing. That will usually backfire.
• Brand and market your social computing solution. Get people excited. Use posters, multi-media, etc.
• Used a phased approach. Don't overwhelm users with too much. Introduce new tools one at a time.
• Take feedback into consideration and implement improvements.
• Social computing is not a fad; it is the evolution of collaboration.
• SharePoint will mine Exchange email messages propose additions to your profile (Interests or Ask Me About fields).
• You can declare blog and wikis items as business records.
• Deloitte: A name that appears in the enterprise is no longer just a name. It is linked to a profile, IM, and email. This creates a much richer sense of connectedness.
• Accenture: If someone views a profile that doesn't have a picture, an e-mail will be sent to the owner and let them know that someone checked their photo-less profile.
• Deloitte: 45% profile creation. Focus on first year was on profile creation. Goal for year 2 is 75%.
• Deloitte: Measure the number of colleagues per end-user. The goal is a minimum of four colleagues, and membership in at least two communities. They also measure the number of profiles views.
• Both Deloitte and Accenture have social computing advisory boards.

Session notes from SharePoint Conference 2009:

• Knowledge Management Issues within the enterprise are still looking for a solution, and social computing might be part of it: Rapid response to problems, capturing knowledge to ensure business continuity, and reducing transition costs. Although social computing may be part of the solution, it is not THE solution to knowledge management.
• If we manage by commitment, and employees meet their commitments, do we really care when, where, and how they do it?
• The evolution of Social Computing: Facilitated Knowledge Management, to collaborative workgroups, to social enterprise.
• We do social things regardless of whether we have social computing tools or not.
  If you're not measure ROI of social computing investments, you're not alone. No one else is either.
• See the "What's the ROI" slide for a great list of social computing benefits.
• Work life is very different than personal life. So, the way we use social media in work life is very different than in personal life. How work differs: Time constraints, negotiated priorities and commitments, processes, functional silos, physical and virtual spaces, regulatory and legal requirements, document centricity, legacy systems, performance evaluations, productivity, control, and knowledge retention.
• When all of your economics come from the industrial age, everything is measured like a factory.
• "Six Sigma almost killed 3M."
• Knowledge work is an iterative process.
• The reason you cannot calculate the ROI of social computing (or telephones, or e-mail), is that you have no idea how people are going to use them. You cannot know who will communicate with whom, what they will talk about, whether they will talk about business, or how much time they will spend communicating.
• Social computing increases the frequency of "knowledge accidents" within a company – which is a good thing.
• Take look at the "Future Vision" graphic slide.
• Plan for success: Create a organizational social media charter, understand how people are using or want to use social computing, determine how social computing can augment existing processes and systems, create awareness, document and share successes.
• Be strategic. Align the social computing goals with the business goals.
• Check out slide on measuring social computing effectiveness.
• Experiment – Monitor – Learn
• If you don't build it they will go somewhere else.
• Social computing is really just a shift in communication channels. It is not something to justify, but something to navigate through, embrace, and leverage as a new capability and manage as a new risk.
• "The anti-social organization is ultimately non-productive." – Chris Howard, Burton Group.

Session notes from SharePoint Conference 2009

• "Enhanced presence" goes beyond just availability. It encompasses location, skills, capabilities, and other attributes that help people and applications find the right person at the right time.
• Microsoft is not sharing anything about Office Communicator Server 14 yet.
• The contact card feature is a summary of a person's info. It appears when you hover over a presence enabled name. It is available throughput Office 2010 and SharePoint 2010. However, it is dependent on OCS.
• From Microsoft Office Communicator (MOC), you can launch an HD video chat. (Cool, but I wonder how much bandwidth that uses.)
• Virtually any UCC functionality available in MOC, is available through an API for developer to embed communication capabilities into business applications (Communication-Enabled Business Processes - CEBP).
• Exchange 2010 voice mail is auto-transcribed into email message. Not perfect, but you get the gist.
• OCS is nicely integrated into Outlook. One click to join a meeting from the invitation.