- Jessica Bontjes, Account Executive , Microsoft
- Ash Chaudhury, Collaboration and Voice Product Marketing Manager, Microsoft
- Sarah Cook, Lead Developer, 360 Insights
- Alex Garin, Enterprise Architect, BMO
- Rob Hoogkamp, Consultant, Capgemini
- Jon Horner, Partner, Technical Consultant – O365 with CSS Partner Enablement, Microsoft
- Anna Khloudeneva, SharePoint expert, Texodi
- Moustafa Refaat, Solution Architect, Loblaw Companies
- Jon Studsrud, Delivery Excellence Director, Microsoft
- Greg Zelfond, SharePoint expert, speaker, SharePoint Maven
- 6 anonymous contributors
- Organizations have and generate overwhelming amounts of information, proliferating in a number of disparate systems.
- The new generation of content management systems are designed to personalize the user experience with great selections of features and add-ons. But choices mean understanding business goals and information requirements and carefully planning how this new powerful system will look and feel.
- Many content management teams assume they should just transfer folder structures and existing content into SharePoint, but getting maximum power out of SharePoint means moving away from folders and org chart-based silos and toward a meaningful user experience powered by good structures.
- Information governance and information architecture are complex ideas to grasp and implement. They need time and special expertise at the table. A successful rollout of SharePoint depends on good, thought-out structures.
- SharePoint is primarily a business platform. It’s meant to be configured and maintained by business leaders who know their operations best, needing less dependency on IT. This transfer of responsibility and culture shift requires an effective training plan and the active presence of executive sponsors to help the business bridge that chasm.
- Include Teams in the plan. Microsoft's vision for its set of services means defining how SharePoint fits into the information landscape along with OneDrive and Teams. Look at the package deal to ensure all the services align.
Impact and Result
- The business leads decisions about structuring content.
- There is a standardized set of structures, rules, and practices for managing and growing content services in SharePoint.
- A management team of business information owners leads the structure and ongoing development of the content management system, supported by IT and SMEs.
- Users are informed and engaged, with clear instructions for interacting with SharePoint documents and guidelines for creating team sites.
- The organization understands its information communities and requirements.
- Project and governance leads understand concepts such as unstructured data and records.
This guided implementation is a nine call advisory process.
Guided Implementation #1 - SharePoint Governance
Call #1 - Scope SharePoint program and identify priorities and vision.
Call #2 - Identify stakeholders.
Call #3 - Review governance committee roles and makeup.
Guided Implementation #2 - SharePoint Information Architecture
Call #1 - Understand information mapping and inventory activities.
Call #2 - Review use cases and information flows.
Call #3 - Review sample information architecture structures (e.g. metadata best practices, site structure, teams).
Guided Implementation #3 - SharePoint Migration
Call #1 - Understand changes (e.g. features) and requirements.
Call #2 - Review content and site inventory.
Call #3 - Review migration plan.
Book Your Workshop
Onsite workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost onsite delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.
Module 1: SharePoint Foundations
- Introduce key SharePoint and ECM concepts.
- Build a management team/governance committee of decision makers from the lines of business.
- Define how to communicate major change to users.
- Create vision for SharePoint content services.
Key Benefits Achieved
- Accountabilities assigned for during the project and ongoing
- Understanding of the size of the work involved in building the SharePoint solution
- Rules and guidelines for the setup and use of SharePoint
Review SharePoint and ECM concepts.
- High-level information landscape
Identify governance committee members and SMEs.
- ECM governance charter
Develop the vision for the SharePoint program.
- SharePoint vision and mission statement
Determine approach to engaging and educating users.
- Communication plan
- SharePoint policy (or information management policies)
Module 2: SharePoint Information Architecture
- Understand current information communities and workflows.
- Outline information architecture work items.
- Understand concepts like metadata, records management retention, standard terminology.
Key Benefits Achieved
- Best practices approach to building information architecture
- Plan for building content structures
- Understanding of expertise and time required to build IA foundation
- Management team has the knowledge to negotiate with technology and service providers
Gather key use cases.
- List of each stakeholder’s top three priority use cases
Decide scope from among use cases.
- Pilot scope workflows
- Pilot scope documents
Audit key content.
Review IA best practices.
Module 3: SharePoint Inventory and Migration
- Identify which documents are to be migrated and build a structure for organizing them in the new environment.
Key Benefits Achieved
- List of documents to be migrated
- Framework for building a content structure in the new SharePoint system
- Support decisions about approach to migration (e.g. third-party service, Microsoft API)
Inventory documents to be migrated.
- Content audit
Develop migration plan.
- Migration plan
After each Info-Tech experience, we ask our members to quantify the real time savings, monetary impact, and project improvements our research helped them achieve. See our top member experiences for this Blueprint, and what our clients have to say.