Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tag Social Business Society June 1, 2011

270 views

Published on

  • Be the first to comment

  • Be the first to like this

Tag Social Business Society June 1, 2011

  1. 1. Using SharePoint at an SMB to Get Stuff Done<br />TAG Enterprise 2.0 Meeting<br />June 1, 2011<br />
  2. 2. Who is MAG Mutual?<br /><ul><li>Company started in 1985 focused on insuring Physicians & Surgeons in Georgia
  3. 3. Headquartered in Atlanta, Georgia; Now with Offices in FL, SC, NC and VA.
  4. 4. Leading Medical Professional Liability writer in the Southeast – Ranked 9th in the country
  5. 5. Write other Commercial Lines, such as WC, BOP, General Liability and D&O, for the same market
  6. 6. Approx. $240 million in Direct Written Premium
  7. 7. Three Subsidiaries: Agency, Financial Services, Physician Services</li></li></ul><li>What makes an SMB different?<br /><ul><li>We’re smaller!
  8. 8. One primary location to support
  9. 9. “Walk & Talk” to each other
  10. 10. Centralized decision making – faster?
  11. 11. “Simpler” processes
  12. 12. More Control over Infrastructure
  13. 13. Less Revenue – Less Capital to invest</li></li></ul><li>What makes us similar to bigger companies?<br /><ul><li>We have processes
  14. 14. Mobile and remote employees
  15. 15. People Issues: Domains / Accountability
  16. 16. Compete for the same customers
  17. 17. Do the same stuff– Marketing, Sales, Operations, HAL (HR, Accounting & Legal)</li></ul>….. So we really aren’t that different!<br />
  18. 18. What was happening?<br /><ul><li>Backlog of I.T. requests was growing - “Do more with less” directive as a result of soft market (in year 5)
  19. 19. The Company developed a new 5 year Strategic Plan
  20. 20. Instituted formal I.T. Governance surrounding project and resource management – focus I.T. resources on Strategic Goals
  21. 21. Demand for smaller projects didn’t go away, nor did the backlog</li></li></ul><li>What was the Business doing?<br /><ul><li>Increased requests as demands placed on business units grew
  22. 22. Using Office for workflow and information, and contracted with third-party vendors for specific tasks
  23. 23. Realized there was no integration with corporate data, and no controls between departments
  24. 24. What a surprise!
  25. 25. Demands placed back on I.T. to respond – I had to do something!</li></li></ul><li>What were the Obstacles?<br /><ul><li>Resource Constraints: Skills / Staffing Levels / Money (remember the “Do More with Less”?)
  26. 26. Collaboration was NOT a corporate culture – everyone felt they were a silo and unique
  27. 27. Few commit the time to define what they want
  28. 28. Fewer have the ability to define what they want!</li></li></ul><li>What did I do?<br /><ul><li>High-level awareness about Collaboration, what SharePoint is and what it could do to address issues
  29. 29. Licensed SharePoint as part of another project (OCS), with an Enterprise CAL
  30. 30. Brought in help - ThreeWill (Alpharetta, GA) - for SharePoint guidance, resources and best practices
  31. 31. Conducted a series of meetings with each Department to identify their manual non-transactional tasks</li></li></ul><li>What did I do (continued)?<br /><ul><li>Identified 3 advocates – either used SharePoint at prior company or saw the value proposition
  32. 32. Developed high-level estimates / ROIs and prioritized candidate efforts for those folks
  33. 33. Convinced them (aka “I’ll pay the tab”) to let me automate their high-impact tasks (Operations Schedules, Employee On-boarding, Annual Report, etc.)
  34. 34. They said OK!</li></li></ul><li>First Steps…<br /><ul><li>Site Taxonomy
  35. 35. One Site Collection versus multiple Sites (Inheritance / Management)
  36. 36. Departments? Communities? Workgroups? All 3 (of course!)
  37. 37. Site Map
  38. 38. Public / Private Sub-Sites
  39. 39. Enhanced Security - An enabler to all of the above</li></li></ul><li>First Steps…<br /><ul><li>Navigation
  40. 40. Look & Feel
  41. 41. Left-side Navigation versus Frames
  42. 42. Forms</li></li></ul><li>First Steps…<br /><ul><li>Search / Tags / Metadata
  43. 43. Enterprise Search
  44. 44. Best-Match presentation
  45. 45. Tags by Department & Document Type
  46. 46. Shared Tags across Enterprise
  47. 47. Minimal Metadata (initially…TBD)
  48. 48. Used Network Drives / Folders as a Guide</li></li></ul><li>First Steps…<br /><ul><li>Content Management
  49. 49. End-Users manage their own content!</li></li></ul><li>First Steps…<br /><ul><li>Administration
  50. 50. Quotas
  51. 51. Retentions
  52. 52. Backups / Restores
  53. 53. Utilization Reporting
  54. 54. Templates</li></li></ul><li>How did we approach development?<br /><ul><li>Used Agile development to manage scope and see incremental and continual value
  55. 55. Involved early adopters – daily stand-up meetings and short work sessions
  56. 56. Lived the “80% is good enough” rule
  57. 57. Kept to the core capabilities of SharePoint – no custom coding or third-party tools
  58. 58. Listened to our partner…and they listened to us</li></li></ul><li>What were the Results?<br /><ul><li>Initial functions went live within 90 days
  59. 59. Transitioned skills in-house (still use ThreeWill for visioning and staff-augmentation)
  60. 60. SharePoint gets considered for new requests involving workflow and/or specialized databases
  61. 61. But…still haven’t obtained “cultural critical mass”</li></li></ul><li>What’s the Future for SharePoint?<br /><ul><li>Viral Growth – “the more you use it, the more uses you find for it”
  62. 62. Continue to foster Collaboration as a culture
  63. 63. New Sites / Functions identified:
  64. 64. Employee Intranet (default homepage for IE)
  65. 65. I.T. Projects & Service Tickets
  66. 66. Agent Portals
  67. 67. Risk Management Site Visits
  68. 68. Board of Directors
  69. 69. World Peace! </li></li></ul><li>In Conclusion….<br />Questions?<br />Thank You!<br />

×