1.JBoye Web & Intranet Conference Aarhus, Denmark 7 November 2012CMS on a daily basis Marianne KayWeb Strategist, Web CMS Consultant

2. CMS on a daily basis User adoption Support Performance issues Caching Training Content modeling Archival Upgrades Governance and workflow 3. Business objectives for a CMS increase revenues reduce operational costs / increase efficiency reduce or eliminate risks consolidate multiple platforms, manageincreasing complexity simplify governance processes, automate record-keeping and archival 4. A CMS is right and the features are real when yourorganization is using it every day.http://www.cmsreview.com/Steps/ 5. User adoption 6. User adoption Point out benefits and usefulness Build training around user requirements /scenarios Provide assurance of training and support fromthe beginning of your project Start with pilot projects and promote successstories 7. CMS Developers 8. Support support from the vendor: annual fee of 20% of the licensing (negotiable!) for the life of ownership; provided to a limited number of CMS administrators only; insight into vendors own tips and tricks and roadmap escalate support requests to senior members of support team provide instructions on how to reproduce the problem mind the geographical location / working hours of the support team support from implementation partner tailored to project pragmatic, down-to-earth, sceptical, with budgets in mind expertise in related areas such as marketing and UX developer communities not always open, not always vibrant many customers, if approached directly, willingly share their experiences 9. Trainingtype of trainingdelivered by who forCMS product CMS vendor CMS administrators,training and CMS developers,certificationpower-usersProject-specific, CMS implementorContent contributors,scenario-basedor in-house expert Web editors,training ApproversTime it right! 10. TrainingWhat I hear, I forget.What I hear and see, I remember a little.What I hear, see, and ask questions about or discuss withsomeone else, I begin to understand.What I hear, see, discuss, and do, I acquire knowledge and skill.What I teach to another, I master.Mel Silberman (1996) 11. Performance issues internal performance(web editors) external performance(website visitors)The problem is with theimplementation, not theproduct vendors say... 12. Performance diagnosticsExamples: Sitecore Performance Tuning Guidehttp://sdn.sitecore.net/upload/sitecore6/64/cms_tuning_guide_sc60-64-a4.pdf Drupal Performance Tuninghttp://www.oshyn.com/landingpages/drupal-performance-tuning EPiServer CMS Performance Troubleshootinghttp://labs.episerver.com/pagefiles/114136/performancetroubleshooting.pptx 13. CachingCaching is difficult to implement properly.Things to consider: Which pages should be cached Cache full pages or page fragments How to invalidate the cached data 14. Backup and Data RecoveryYou must be pretty angry at yourselfright now for not doing the backup... 15. Content modelingDeane Barker, Gadgetopiawww.slideshare.net/gadgetopia/just-put-that-in-the-zip-code-field 16. Understanding content modelingDifferent content types are: structured differently edited and validated differently. displayed differently. managed differently.Content types often act as functional boundaries for:- Permissions- Workflow- Navigation- SearchDeane Barker, Gadgetopiawww.slideshare.net/gadgetopia/just-put-that-in-the-zip-code-field 17. Archival needsCMS versioning alone maynot fully address archivingand retrieval needs of alarge, regulatedorganisation 18. Ongoing development cost Securing funding for Phase2 developmentswill depend on Phase1 success stories Any new functionality / applications need tobe developed with the CMS in mind (thisusually implies extra development costs) 19. UpgradesThink carefully before you upgrade: customisations extensions integration points plugins refresher training sessionsNo such thing as an easyupgradeSeek other customers who have by Irina Gusevahttp://www.realstorygroalready upgraded. up.com/Blog/2111-No-such-thing-as-an-easy-upgrade-with-your-CMS 20. Governance and workflowCMS workflow functionality isrigid (linear, parallel...) while theprocess behind it is collaborativeand dynamichttp://www.brightlabs.com.au/page/Web-Design-Blog/Workflow_in_Content_Management/Workflow is one of the 8 CMS features customers wantbut never usehttp://jboye.com/blogpost/8-cms-features-customers-want-but-never-use/ 21. User access rights and permissions restrictions by asset types restrictions by admin functions restrictions by folder administrator access managing more than oneadmin role in the organisation beware of departmental silos what happens when staff leave? 22. SummarySmooth running of a CMS requires: effective training user adoption adequate funding for future development technical expertise content management skills governance commitment! 23. Thank you!Marianne KayWeb Strategist and Web CMS ConsultantEmail: marianne@mariannekay.comTwitter: @marianne_uaLinkedIn:http://uk.linkedin.com/in/mariannekay/