Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
SPSTCDC - SharePoint 2010 Adoption - Decade
1. A decade of SharePoint Adoption Strategies SharePoint Saturday the Conference August 2011
2. A Decade of SharePoint Adoption (S1A-101)Admin – 200 Chris McNulty & Mike Gilronan Knowledge Management Associates Welcome to SharePoint Saturday—The Conference
3. Welcome to SharePoint Saturday—The Conference Thank you for being a part of the first SharePoint Saturday conference Please turn off all electronic devices or set them to vibrate. If you must take a phone call, please do so in the hall so as not to disturb others. Open wireless access is available at SSID: SPSTC2011 Feel free to “tweet and blog” during the session Thanks to our Diamond and Platinum Sponsors:
4. About KMA Founded 1995 10 years of delivering SharePoint solutions Three Themes Collaboration, Insight, Productivity Two principal lines of business Professional Services SharePoint Consulting and Application Development Software Product Mekko Graphics advanced charting software One Technology Stack Pure-play Microsoft Partner
22. Hallmarks of good adoption Roadblocks or symptoms of bad adoption Tools and techniques that our clients have used to drive adoption Worst practices Q&A, Resources, Closing Today’s Session, in detail
29. Speed to market Over-governance Maintenance No/bad sponsorship Redundancy of content Too many documents "Field of dreams" mentality Roadblocks to Adoption
31. Lunch/Catering Application Dynamic, Targeted Content on Home Page Birthday List Today @ACME / Meeting Room Central Unique applications and solutions
32. Training Lunch and Learn Formal Training Internal External site Product vs Solution
33. Branding/Naming First rule of SharePoint – don’t call it SharePoint! E.g., Nebula Cramerville Shmoogle BaseCamp Segmentation Marketing
34. Survey Administrative Tools Feedback mechanism prominent on the front page Visible and available super-users or support staff Assessment
35. Departmental Approach Steering Committee (Cross-Functional) Move Fast Quick early successes count more Drive fast, take chances! Project Design
36. Support SharePoint for SharePoint Prepare Support Teams Self Service Support/Communities Team Leaders Support/Decentralized Tech Sheets – Quick one page tips or FAQs
37. “Big event” Usually a breakfast Sometimes a lunch Rarely an evening happy hour Gift bags/materials Training Contests and prizes, often with a scavenger hunt Public awards Giveaways – branded items with tips and helpful information Resources: “I Use SharePoint” Launch Events
38. Theory Y SLAs Chargeback incentives Viral Communications Social Communities Badges Miscellaneous Motivations Theory X Home Page Lockin Mandates “Burn the Boats”
39. 5 things to do after 3 months in production Usage/Search logs MySite self-population Content growth trends Repeat rollout training Re-evaluate roadmap “Accessory After the Fact”
40. Three things to never allow in your SharePoint rollout… Worst Practices! Three things to never allow in your SharePoint deployment aka “How to squash adoption in three easy steps”
46. From Microsoft: SharePoint Adoption tools: http://sharepoint.microsoft.com/iusesharepoint/landing.aspx From Others SharePoint Maturity Model (SPMaturity.com) – Noon, CN114 Susan Hanley (susanhanley.com) – great presentation on this yesterday From Chris SPSTCDC : SharePoint Business Intelligence 11:30M CT207 SPSTCDC: Managed Metadata and Taxonomies 3:00pm CN117 New Jersey SharePoint User Group September 14 (Business Intelligence) SharePoint Saturday NH – September 24, 2011 (Business Intelligence) KMWorld DC October 2011 (IT) From KMA (www.kma-llc.net) Blogs, presentations, news, and events Monthly webinars Resources - General
51. Thanks to Our Other Sponsors! Thanks to our Sponsors
52. Session Evaluation Please complete and turn in your Session Evaluation Form so we can improve future events. Survey can be filled out at: http://app.fluidsurveys.com/s/spstc2011-Sat-S1A-101 Presenter: Chris McNulty & Mike Gilronan Session Name: A Decade of SharePoint Adoption Session No.: S1A-101
SharePoint 2010 can be compared to a functional “firehose”, having grown from a simple tool for team documents and dashboards in 2001, to the rich multifunctional environment of SharePoint 2010. (BI! Workflow! Social computing! Data integration! Etc.) And if you can’t push on a rope, as they say, you really can’t push a firehose – users need to pull it in. Attendees passionately shared their stories about the major intrinsic enablers and roadblocks to SharePoint adoption.
CFM ROI: e.g. online collaboration reduces travel costsimportance of responsive, qualitative system performance for users to sustain enthusiasm.Rapid development and deployment of user-oriented solutions
CFMSpeed to market -- boil the ocean approach to solving too many problemsOver-governance: (e.g. too hard to get sites)Maintenance: Redundancy of content -- Documents duplicated in file systems and multiple sites – lack of operational governance and user guidanceField of Dreams– if you build it they will come.
[MG]Lunch Application –KMA clients use lunch or catering order application on SharePoint. Users seem to really emotionally bond to these solutions – it’s fun & essential and replaces slower, manual processes.Dynamic Content on Home Page – Offering a fresh cycle of new information on the home page is thought to be equally or more important to clean attractive design.Birthday List – another example of fun, unique and essential information that bonds users with the siteFind that first one! Think horizontal.
[mg] Branding/Naming – In particular when companies are launching or relaunching a SharePoint based project, it helps to brand the project with the name of the site (e.g. “I’m using MyCompany” instead of “I’m using “SharePoint”.Marketing & Segmentation – it’s important to understand that the adoption message needs to be distinguished not only for different groups of business users (power users/casual users) but also different IT constituents (developers/server teams/analysts & PMs)
[CFM] Survey – use SharePoint surveys to measure success and determine future directionsAdministrative Tools – measure what people are looking for
[mg] Departmental Approach – build success at a lower level first before tackling enterprise wide adoptionSteering Committee (Cross-Functional) – it helps when the project is accountable to a frequently meeting team of empowered business stakeholders drawn from multiple departments, not just IT and HR.Move Fast – quick early successes count more than long, late successes
[CFM] SharePoint -> SharePoint – use a SharePoint site itself to supply support to usersPrepare Support Teams – make sure Help Desks and customization teams are available and trained in advance to minimize the risk of failing to meet rising expectations.Self Service Support/Communities – some companies reports tremendous success using discussions, blogs, and wikis to help users help each otherTeam Leaders Support/Decentralized – Another approach is to decentralize support to power users or team captains in each logical group of usersTech Sheets – Quick one page tips or FAQs can be written and distributed to users and helps desk via email, web sites, print distribution or knowledge bases.
[cfm]Many users schedule a “big event” (usually a breakfast event in the morning, sometimes a lunch, rarely an evening happy hour) the day the site “launches”. In conjunction, these events often offer:TrainingContests and prizes, often with a scavenger huntPublic awardsGiveaways – branded coffee cups, mouse pads or wallet cards with tips and helpful informationResource: “Buzz kit” (2007) replaced by “I use SharePoint”Mother of Navy Seal Michael Murphy christening warship named for her son, posthumously awarded CMH for valor in Afghanistan, first to receive it since Vietnam War.
[mg] Douglas MacGregor @ MIT Sloan in 1960s developed thisSharePoint -> SharePoint – use a SharePoint site itself to supply support to usersPrepare Support Teams – make sure Help Desks and customization teams are available and trained in advance to minimize the risk of failing to meet rising expectations.Self Service Support/Communities – some companies reports tremendous success using discussions, blogs, and wikis to help users help each otherTeam Leaders Support/Decentralized – Another approach is to decentralize support to power users or team captains in each logical group of usersTech Sheets – Quick one page tips or FAQs can be written and distributed to users and helps desk via email, web sites, print distribution or knowledge bases.
Bonus: SharePoint Maturity Model. If you currently use SharePoint, use this model to baseline your maturity and adoption levels, benchmark them against similar companies, and track your progress over time.
[mg] This is one of my favorites. Usually, some senior person complains they can never find anything on the "H drive". Since SharePoint offers a searchable web interface, it has to be better, right? Sure - except if you just dump all that content in without thinking, all you get is a SharePoint site with top level folders called "bobtest". "newtest", "newtest 2", and “sales1997”. Same problem, in a new shiny package. Likelihood of project death – 50%.
[cfm] Just because you can doesn’t mean you should, and without proper training, you will only confuse people, at least, until someone goes in and simplifies it. SharePoint is powerful, often complex. Entering at the pinnacle of complexity management is a surefire way to alienate early adopters. We’ve seen this multiple times, and the result is almost always the same. Likelihood of project death – 75%, (until someone new comes in to clean up the complexity.)
[mg] This one is pretty simple – how do you define success? If success equals a well-used site, then this virtually guarantees failure. Simply sending around an email announcing your new site doesn’t cut it. People learn differently, and many folks need multiple “touches” before they feel comfortable. Death rate – 75%
CFMMulti-generational: Different generations adopt technology differently. Different ages have different comfort levels with web technology (corporate sites vs. social networking) and platforms (PC or laptop or smartphone)Multi-national: global audiences have different preferences for platforms, tools, bandwidth and site performance expectationsMulti-platform: mobile enablement
Give code word to Chris > 4:15 on Saturday for chance to win copy of MS-Project Professional 2010