Implementing Collaboration And Social Computing Into The Enterprise Microsoft
1. Implement collaboration and social computing into the Enterprise How we embraced collaboration Scott Carruth Vice President Information Systems Gina Sandon Vice President Marketing
2. Topics About Initiate The Business Opportunity The Unique Challenges we faced The Solution Expected Results Where do we go from here Key Takeaways
3. Initiate Systems, Inc. We enable organizations to strategically leverage and share critical data assets “Initiate Systems…the most productive live customers.” Leading pure-play CDI/MDM vendor Established 1995 Cited as “leader” by Forrester Cited as “visionary” by Gartner 200+ customers across 10 market segments Private and Public Healthcare,Healthcare Exchanges Finance, Retail, Hospitality, High Tech,Manufacturing State and Local Government, Intelligence,Law Enforcement Offices in U.S., Canada, EMEA, Asia-Pacific “Initiate…delivers fast timeto value and a relatively lowservice-to-software cost ratio”
4.
5. We are at Work When You… … Purchase PC & Software … Pick Up Your Prescription … Apply for a Loan … Earn points, loyalty program … Identify Risks … File Insurance Claims … Register a Patient
6. Established & Proven with Blue-Chip Organizations Healthcare Government COMMERCIAL HEALTHCARE PUBLIC SECTOR PARTNERS
9. Our Challenges (and most likely yours as well) Trying to get everyone on the same page Trying to educate everyone on content and information management Different departments had for so long been responsible for their own needs; trying to change this has been a challenge; we still have some silos to take down Unstructured knowledge (wikis) are the thing – easy to use, hard to filter, hard to track change Documents were plentiful, “Which version do you have?” and “Where did you find that presentation?” Individuals and departments would not be receptive to change Individuals would resist
12. 13 Initiate Systems – Roadmap Roadmap MOSS Website Enable Web analytics within SharePoint Lead Management Web HostingModifications RSS Feeds MOSS Audit Search Engine Optimization MOSS Intranet/Portal Prospect Portal Insight Intranet to MOSS (Intranet Foundation) Project Portal Customer Knowledge Center Portal Partner portal Trade Show Portal Enable Document Management Exchange Assessment External User access Prospect-to-customer hand-off Active Directory & ExchangeManagement Competitive intelligence blog for sales Content & Information Architecture Video Sharing & Podcasts Identity Management / single sign on SAVO/MOSS/SFDC/QuickAarow/ LMS Information Strategy Define Company-wide Information Architecture How do I do my jobcontent Competitive intelligence blog Create sales enablement repository QuickArrow reports w/o heavy lifting Internal Communications Company-wide Calendar Corporate Event Management Customer wins template Employee newsletter (in MOSS) Combined Communication Plan Notifications that something is down Online Facebook / My Sites External Communications Customer Advisory Board Forum Multiple user controlled opt/ out preferences. Eloqua Email Blast Best Practices IT CommunityCollaboration Package Pickup Controlled forums for community customer feedback External blogging to promote thought leadership Workflow Services Methodology Workflow Deal Approval Workflow Content Workflow PHASE 1 PHASE 2 PHASE 3
14. Requirements, Specifications and Scrum Methodology Requirements Elicitation Information Architecture Governance Model Stakeholder Interviews Functional Specifications Product Backlog Defined Sprints
28. Expected Results Improve collaboration amongst individuals and teams by providing Web 2.0 functionality Ideas Social networking, communities Wikis, blogs, status Improve the capturing of tribal knowledge and experience Individuals would contribute if there was an avenue to do so Individuals would contribute if their ideas were actually seen and voted on by their peers Provide a place where all project and team content is captured Improve our ability to find information
30. What’s Next We have a few more phases to complete on our internal site Phase 2 will add additional web parts and functionality for Products and Development, Customers and Projects, etc. Phase 3, will add additional functionality, including a dashboard rollup that is tied to our key initiatives Customer and Partner Portal We will create a my.initiate.com site for customers and implementation partners to engage, this will be tied in with our Customer/Projects site collection We will create a partner.initiate.com portal that marries Salesforce.com and SharePoint Content
32. Key Takeaways Remember, in this day and age, its about the employee and their contributions, not the company Continue to push information to keep staff informed; but allow the employee to control how information is received, control the spam Allow folks to contribute to the stream of knowledge Govern your content and your data; once you allow content to enter without meta data; you have lost control Keep it Simple! Don’t over engineer it!
As our company grew, we quickly outgrew our existing ‘departmental’ CMS which was really only built for R&D and SupportOur existing site was build on Open Source, we had no one to truly administer the site and there was no governance around the content (GIGO)You could not find anything that was posted up there. Countless times it was like performing an archeological dig to find the right content.As a result, each department was implementing their own solutions to meet their department needs without truly solving the overall problemWith multiple repositories and remote resources to serve we needed a way of consolidating our content and have a solution that fostered collaborating on projects in a more efficient manner
Last year, we held a stakeholder meeting with RightPoint and developed the following Top Initiatives for Initiate Systems
Which resulted in a prioritization map; the things in green were identified as the easies to accomplish; and for the most part, they are mostly done.
We then spent some time gather additional requirements, documenting our information architecture, our governance model and specifications for what we wanted. This resulted in a Product Backlog of requirements. We then secured the budget, formed the team and trained everyone on Agile/Scrum Methodology. We took the backlog and formed 5 ten day sprints. It was planning well worth it.
The result of the stakeholder interviews and functional specifications was a series of wireframes that described what we wanted to get accomplished
As part of our requirements elicitation process we worked with RightPoint to identify, priority and wireframe our solution. Through this effort, we have created a unified content management platform that promotes collaboration It is focused on the employee, communities and teams over the standard stale corporate Intranet Individuals are responsible for managing their own sites as defined within their specific areaContent and Knowledge is searchable throughout our the siteGovernance of Data and Sites has been established. Which means that certain sites are setup by the individuals, but communities are controlled. Content types have been established and training will be pushed through content leaders
Our design principles are based on standard web site designBe consistent in color and brandingBe consistent in menu structure and layoutMake it easy to get to the information that you are after
We have a multi faceted approach towards content management. As such, we have extended our branding so that it is integrated across all of our employee sites and solutions. Initiate Knowledge Exchange is actually three separate systems that are integrated. There is the obvious integration between MOSS, Exchange and OCS. But then we extend the integration to IKE Live (our employee training portal) and IKE SE (our Sales Enablement Portal). When an employee accesses IKE 2.0, they see sites and content that start with their immediate needs and that then expands in focus towards the functional areas. They will be able to see who has posted what content and whether they are available via OCS presence. From there we will extend the integration to our external sites (customer, prospect and partner), which utilize a different brand altogether.