Through numerous years of eating, drinking and sleeping SharePoint I have come to realize that there is 1 thing that has never changed. That 1 thing is a question and the answer to that question is the most important thing in all of SharePoint. That question is "What direction should my organization be going and how do we get there?". The question or a very close form of that question is asked anytime something bad happens to the current environment or software, the current environment or software is up for renewal, new technology is introduced and last but not least, during yearly budget planning. Most companies will fall into one of the following categories:
• Current application is no longer suitable due to company growth, lack of functionality or
• Current application company that created & supported it no longer exists.
• Starting from scratch and SharePoint has been chosen now deciding which way to go and where to start?
• Currently utilizing SharePoint but not exactly the way Microsoft intended
• Need to upgrade to continue support
Regardless of the current situation your organization is in the end goal for all is success and success is measured by the usage of the application. Yes folks user adoption IS more important than being on time or under budget. Otherwise, what was the point of the entire project that I am sure took months and sometimes years to plan and implement. In this session I will take you through where to start, keys to choosing the right path for your organization and most importantly implement SharePoint in a way user adoption meets your goals and of course come in on time and on par with the budget.
5. Agenda
• Where to Start
– Want to be Successful or just waste time
and fail
• Planning
– Beginning
– Middle
– End
• Marketing
• Quick Wins
• User Adoption
• Governance
9. Joking is not an option!
• Install Pre-Reqs
• Install SharePoint
– Accepting all Defaults
along the way…
• Option to Configure
Manually or Automatically
– Why overwork ourselves
Automatic Please
• Create 1 Web Application
• Create 1 Site Collection
• Dump Content & #BOOM
SharePoint is Production!!!!
Star Wars SharePoint
10. Middle Pros & Cons
Star Wars
• Too many unanswered
Questions
• We didn’t know until 1, 2 & 3
were announced.
• What was George Lucas
thinking?
SharePoint
• No Governance
• No Consistency
• Everyone doing there own thing
• No Training
• So much dev its unsupportable &
un-migratable
• Multiple and conflicting
taxonomies
• Permissions Inconsistent
11. Notice There Were NO
SharePoint Pros!!
Star Wars is just a pro all the
time…
18. Planning
• Project DiscoveryCharter
• Project Timeline
• Project Plan
• Project Communication
–Different people communicate
differently
• Phone, Email, Meetings, Text
• Governance
19. Marketing
• Make sure the users/business stay involved
– Mockups
– Initial communications
• How much is marketing/communications
involved in the project, day to day, and
governance
• Early steps in User Adoption
• Outside Marketing (Fresh Point of View)
23. Quick Wins
• What is a quick win?
• Where do you find them?
• Examples
– Corporate Directory
– Birthday or Team web parts
– New Site
– Document Sets
– Search Web Parts
– Promoted Links
– Global Navigation
– Process Automation (Expenses, Vacation, etc.)
24. User Profiles
• Self-Service
• Whose Who (Meeting Prep)
• Corporate Directory
• Quick Information
• Learn About Your Company
• Builds Company Bonding
• Integration to Other Systems
• Customizable to Suit YOUR
Needs!!
25. New Site Setup
• Immediate Utilization
• Consistency
• Ease of Use (All Levels)
• Limit Non Best Practice Usage
–Custom Permission Level
• User Adoption
28. Immediate
Utilization
• Establish Go Live
• Marketable
• Team Focused
• Instant User Adoption
• Site Roadmap
• Set for Success
– Process Improvement
– Automation
29.
30. Consistency
Implement
• UIUX
– Dept. to Dept.
– Corporate to Dept.
– Project to Project
• Functionality
Impact
• Simplified Training
• Department Bonding
– Info. Share
– Knowledge Share
• Corporate Bonding
– About Us
31.
32. Ease of Use
• Out of the box functionality
– Keep it Simple
• Custom Development
– Time and a Place
• Training
– Easy to Access
– Repeatable
– Easy to Update
41. User Adoption
• Involvement from the Beginning
– Everyone’s Opinion Matters
• Implement Feedback
• Communication, Communication,
Communication
• Training
– Reoccurring (Turnover, job change, new features,
etc.)
• Internal User Groups
– Brown bag lunch
– Local community groups
• How To’s (Knowledge Base)
– Link on Home Page
• What’s Next?
– Roadmap
45. Management is Needed
• Express the Importance
– No Governance vs. Governance Examples
• Show ROI (Examples or Real Life)
– Find 2 or 3 Examples
• Management Involvement vs. No
Involvement
• Identify Needs for Success
• Seeing is Believing
46. • Environment Architecture
• Content Management
• Compliance
• Information Architecture
• Security
• Training
• Communication
Area’s of Governance
48. Features &
Functionality• Groups
• Teams
• Public Sites
• Intranet Usage
• Video
• Community Sites
• Team Sites
• Wiki
• Site Audits
• Naming Conventions
• Taxonomy & Suggestions
• Compliance
• Reporting
• Site vs. Sub-Site
• Quotas
• Development
• Hub Sites
• OneDriveMySites
• Delve
• Business Intelligence
• Security
• User Profiles
• Blogging
• Customizations
• Delivering Content
• Relocating Content
• Removing Content
• Site Creations
• Templates
Get it yet??
EVERYTHING!!
51. IMPACTS OF OFFICE 365
https://support.office.com/en-us/article/SharePoint-Online-and-OneDrive-for-Business-software-
boundaries-and-limits-8F34FF47-B749-408B-ABC0-B605E1F6D498?ui=en-US&rs=en-US&ad=US
52. Strategy Team
Consists of business owners
who provide insight and
direction to drive strategic
initiatives
Tactical Team
Consists of 3 sub-teams that
support the directives of the
Strategy team
• Operations
• Support
• Developers
Team Roles
53. Operations Team
• Help Enforce
Governance Plan
• Manage Routine
Maintenance Tasks:
• Nightly Backups
• Usage Monitoring
& Analysis
• Scheduled Task
Validation
• Security Release &
System Upgrades
Support Team
• Create Support System
with SLA’s
• Respond to questions,
bugs and other issue
resolution
• Provide typical
SharePoint Admin roles
such as:
• Site Provisioning
• Security
Permissions for
users and groups
Development
Team
• New features and
program management
while adhering to
standards.
• Develop customized &
personalized solutions
for departments &
division sites.
Whose job will be changing the most?
Tactical Team Responsibilities
54. Operations Team
• Enforce Governance Plan
• Manage Routine Maintenance
Tasks:
• Nightly Backups
• Usage Monitoring &
Analysis
• Scheduled Task Validation
• Security Release & System
Upgrades
• Oracle & DBA Role will be
eliminated
• Active Directory Role
could change (Ping
Identity, FBA, etc.)*
• No Equipment to Support
Support Team
• Create Support System
with SLA’s
• Respond to questions, bugs
and other issue resolution
• Provide typical SharePoint
Admin roles such as:
• Site Provisioning
• Security Permissions
for users and groups
Development Team
• New features and program
management while adhering
to standards.
• Develop customized &
personalized solutions for
departments & division sites.
* Indicates Change
Tactical Team
Responsibilities
55. • Determine initial principles and
goals
• Classify your business
information
• Develop an education strategy
• Develop an ongoing plan
• Keep Communicating to the
Users!!
Best Practice
56. • Knowledge Base
– Searchable
– Automate
– Linkable
• Governance Site (Center of Excellence)
• Don’t Reinvent the Wheel
• Auditing
– Quarterly, monthly, etc.
– Split responsibility so it is not overwhelming for
1 or 2 individuals
– Use 3rd party tool
Ongoing Support
File upload limit 2 GB per file.
File attachment size limit 250 MB
Public Website storage default 5 GB (However, Public sites are going away so beware!!)
A SharePoint admin can allocate up to 1 TB (the limit for a site collection).
An effective governance plan anticipates the needs and goals of your organization's business divisions and IT teams. Because every enterprise is unique, we recommend that you tailor a governance plan to your environment by using the following steps.
Determine initial principles and goals
Set a base line
develop a governance vision, policies, and standards that can be measured to track compliance
For example, your plan should identify SLA’s for both technical and business teams for support
- how long does your SharePoint Support/Admin have to solve an issue? 3 Business Days?
How is that Issue communicated?
What is the support structure?
Classify your business information
What are you going to track? What Key Terms do you have? What is your Taxonomy?
Organize or customize taxonomy - information that supports your business
Design an information architecture to manage it.
Workflow to remind of when a policy doc needs to be reviewed
Refresh Governance Team – New Perspectives