The document discusses seven non-technical factors for successful SharePoint implementations: understanding requirements and limitations, estimating effort accurately, achieving buy-in, determining return on investment, implementing governance, adopting an iterative approach, and improving user adoption. It provides details on each factor, emphasizing the importance of clear expectations, effective communication, governance, and an iterative rollout process to achieve SharePoint success.

1. The Seven Most Important Non Technical SharePoint Success FactorsPresented By: Richard Harbridge@rharbridge

2. Who am I?I

3. Understanding the Non TechnicalThe Biggest ReasonsSharePoint Projects Fail?Is necessary to avoid poor…Shared Understanding of Requirements/Needs

4. Knowledge around Limitations of the Software (When to use it/When not to)

5. Estimation of Effort and Schedule Accuracy Our Goal Today…From Here To Here

6. What we will be talking about…Understanding the ‘Why’ & Making a DecisionAchieving Buy In and Setting ExpectationsDetermining and Supporting ROIImplementing Successful GovernanceApproaching and Supporting SharePointImproving User AdoptionPlanning for New Work and Growth

7. Understanding the ‘Why’ and Making a Decision

8. Meet JoeHi!

9. At Joe’s Company…

10. Decision Makers don’t have Enough Information

11. The CFO needs to Reduce Costs

12. IT Services Struggles to Keep Up

13. AndPeople Are Having Trouble Finding What They Need

14. So Joe has an Idea!

15. Since…Awesome! Not as awesome.

16. And Everyone in Joe’s Company uses Microsoft Office…

17. SharePoint is the Perfect Fit!

19. Map the needs of the organization to the right technology…

20. Perform in depth product comparisons and evaluations

21. Like this one…Excerpt of Product Comparison written by Richard Harbridge courtesy of Concept Interactive

22. This is important as Microsoft alone has a quite a few…Dynamics AX

23. Dynamics CRM

24. Dynamics GP

25. Dynamics NAV

26. Dynamics POS

27. Dynamics RMS

28. Dynamics SL2007OnlineOn SiteEven SharePoint has multiple options2010

29. It’s not just a feature to feature comparison

30. So Joe does all that good research and…

31. SharePoint is a part of his overall Enterprise Technology Plan

32. The OutcomeWithin the overall enterprise technology plan SharePoint meets specific business needs.

33. What to watch out for…We have to define our needs carefully if we want to pick the right technology.

34. Achieving Buy In and Setting Expectations

35. Before we begin…

36. Let’s Talk About Perceptions

38. People See Different Things

39. Perceptions Impact Motivation

40. Joe is on a mission.

41. Joe has to convince IT Services, the CFO and Decision Makers

42. We are going to help Joe out with an exercise!Thanks!

43. Two Key Groups Must Buy In and Have The Right ExpectationsIT ServicesDecision Makers

44. What is the most important thing to IT Services?

45. COST OF OWNERSHIP

46. What are some ways we can convince IT Services?

47. Cost of Ownership (IT)The Biggest Point to Share is:SharePoint eventually allows Business Users to develop and implement business solutions that use technology without IT’s involvement.The Reality:IT doesn’t want to learn/support a new technology.

48. SharePoint’s integration is invaluable to IT.

49. A unified application delivery platform like SharePoint can greatly reduce costs, time and effort for new work.Explain Information OverloadInformationInformationInformationInformation

50. Explain Platform Benefits

51. What is the most important thing to Decision Makers?

52. Add Value To Business

53. What are some ways we can convince Decision Makers?

54. Add Value (Decision Makers)The Biggest Point to Share is:SharePoint can help achievebusiness objectives by improving productivity, reducing waste, and improving visibility to help drive better decision making.The Reality:Business Objectives are often not specific enough to be achievable.

55. It takes time and investment to reach the point all managers and executives want. Prioritize and Plan

56. Paired Comparison Matrix

57. Map Solutions to Objectives Direct Relationship Indirect Relationship* Objectives should be more specific – Example purposes only.

58. SharePoint will be…Utilized by Business Users to develop and implement business solutions that use technology without IT’s direct involvement.

59. Our primary unified application delivery platform.

60. Our primary workflow/business process automation platform.

61. Our intranet and communication center for internal corporate communications.

62. …SharePoint will not be…Our (external) web content management platform.

63. Our primary document management platform.

64. Our contact management platform.

65. …What’s the expectationwe have to set?

66. It Takes Time

67. SharePoint Solutions (Evolution)*Super Simplified

68. The OutcomeJoe has achieved momentum and buy in.

69. What to watch out for…Joe must carefully manage expectations and maintain the momentum.

70. Determining and Supporting ROI

71. How do we get here?

72. Lets Talk Numbers (CFO/Finance)The Biggest Point to Share is:SharePoint is worth the initial investment and ongoing costs. The Reality:It is a costly investment and costly on going expense.

73. Money can be invested to always generate a return.

74. You need to have measurement, account for risk, and have some expectation of return (quantifiable) that makes it worth the initial investment/on going costs.Evaluating With Discounted Cash FlowShow expected cost and return over multiple time periods.

75. Remember to ‘discount’ values to account for cost of capital impact and the fact $5 dollars today is worth less than $5 in the future.Evaluating with Real Options Analysis

76. Evaluating with Monte Carlo Analysis

77. There are different ways of calculating ROIThis is kind of boring…

78. ROI Advice and Tips

79. Excel has wonderful Formulas

80. There are really only two ways of using ROI1. For Prioritization2. To Improve Return

81. 1. For PrioritizationThe Simplest ROI Formula EverEstimated ValueEven I can do it!Estimated Difficulty

82. 1. For PrioritizationExamplesI have a difficult requirement. It’s an 8 in difficulty (out of 10).

83. I have an easy requirement. It’s a 2 in difficulty (out of 10).

84. The expected value of the difficult requirement is 4 (out of 10).

85. The expected value of the easy requirement is 6 (out of 10).Estimated ValueEstimated Difficulty

86. 2. To Improve ReturnROI (traditionally) Measures Financial Impact

87. 2. To Improve ReturnROI analysis often misses 'non-financial impact’ or ‘increased potential’STILL IMPORTANTImproved RelationshipsImproved Know-HowWebsite/Intranet VisitorsImproved MoraleImproved SkillsUser ComplaintsIncreased ConnectionsPositive Word of MouthInnovationClick-throughsEmployment ApplicationsCommentsNegative Word of MouthBetter Reputation

88. 2. To Improve ReturnExample of Non-Financial Measurement

89. IS Use them.

90. SharePoint Deployment Planning Services (SDPS)https://www.partnersdps.com/Pages/ToolsSupport.aspx

91. Rapid Economic Justification Guidehttp://www.microsoft.com/business/enterprise/value.mspx

92. MEASURE THE RIGHT THING

94. What you don’t want.Don’t lose perspective.

95. Public Statisticscan help…Typical workers produce 3+ GB of data per year.

96. 30% of a typical workers day is spent searching for information.

97. In a 1,000 employee company lost productivity costs approximately $5 million a year.Source: “The Enterprise Workplace,” IDC, 2005Source: IDC, 2003Source: “Hidden Costs of Information Work,” IDC, 2006

98. Statistics within the Organization are better.20% of our IT Support people who travel do not have access to our IT policies and support documents when travelling.

99. 4 out of 5 of our workers do not know that we have an employee disaster relief fund.

100. Currently we pay for full licensing on 7 different enterprise document management solutions.Source: “Support Review Q4,” IT, 2010Source: “HR Employee Benefits Survey,” HR, 2010Source: “Financial Audit of Licensing Costs,” Finance, 2010

101. The OutcomeJoe is measuring effort effectively to better prioritize or to improve return on investment.

102. What to watch out for…Fear of bad estimation leading to not estimating at all. Vaguely right is better than precisely wrong.

103. Implementing Successful Governance

104. What is Governance?

105. GOVERNANCE IS REQUIRED

106. What does that mean?Without effective governanceorganization, performance, andcapability are significantly reduced.

107. Without Governance

108. So how do we do it?

109. Teamwork is KeyThere are typically 5 teams for SharePoint Governance:Business Strategy Team

110. Initiatives/Technical Strategy Team

111. Tactical Teams:

112. Tactical Operations Team

113. Tactical Development Team

114. Tactical Support TeamIdentify patterns.Plan for patterns.Execute patterns.

115. I think I see a Pattern.

116. Executing Governance

117. The Result:

118. Governance DocumentationAggregate/Reference Document(Contains all SharePoint Info – Single Point of Reference)

119. Objectives/Priorities (Tech/Business)SharePoint will be…Utilized by Business Users to develop and implement business solutions that use technology without IT’s direct involvement.

120. Our primary unified application delivery platform.

121. Our primary workflow/business process automation platform.

122. Our intranet and communication center for internal corporate communications.

123. …SharePoint will not be…Our (external) web content management platform.

124. Our primary document management platform.

125. Our contact management platform.

126. …Operations DocumentationObjectives/Priorities

127. Disaster Recovery Plan

128. Deployment Process, Policies, and Schedule

129. Storage and Quota Policies

130. Monitoring Plans

131. Maintenance Plans

132. Service Level Agreements

133. Etc…Support DocumentationObjectives/Priorities

134. Site Classification and Platform Classification

135. Site Provisioning Process/Questionnaire

136. User Expectations Agreement

137. Roles and Responsibilities

138. Support Agreement(s)

139. Training and Communication Plans

140. MySite Policies (Pictures)…Development DocumentationBranding Guide

141. Workflow Policy

142. SharePoint Designer Policy

143. Development Standards

144. Testing Requirements

145. Etc…IS Use them.

146. Governance Checklist

147. TechNet, Community and More..

148. With Governance

149. The OutcomeEveryone Achieves a Shared Understanding of SharePoint Related Processes

150. What to watch out for…Not just documents, policies, and procedures. It is an active and ongoing process.

151. Approaching and Supporting SharePoint

152. What is the best approach for SharePoint Implementations?

153. ITERATIVE APPROACH

154. Why Iterative?SharePoint is a very large platform.

155. It takes time to understand SharePoint.

156. SharePoint is great for rapid prototyping, and for proof of concept work.

157. It ensures there is enough time to review, adjust, and communicate.CommunicationPlanning

158. TheCommunicationPlanWill act as a binding agreement (forces you to carry through).

159. Helps keep communication focused.

160. Helps prevent unwanted surprises.CommunicationTipsUse pictures and more pictures.

161. Explain as much as you can (Pros/Cons).