This presentation is from a tutorial held at the J. Boye Aarhus 13 conference. See http://aarhus13.jboye.com/tutorial/the-art-and-science-of-selecting-the-right-cms/ The goal is to help you and your team understand Web Content Management technologies, architectures, and the marketplace. Janus Boye led an intensive, fast-paced and vendor-neutral introduction to Web Content Management functionality, product categories and specific vendors. The tutorial concluded with a roadmap for product selection. The 3-hour tutorial also presents a practical approach to selecting a CMS, based on marketplace realities and the experiences gained in many selection projects. While it is easy to document dozens of functional and technical requirements for a content management system (CMS), writing more requirements actually makes it harder to select a product.

1. The art and science of
selecting the right Web CMS
Janus Boye
jb@jboye.com @janusboye #jboye13
J. Boye Aarhus 13, Denmark

2. Gartner Magic Quadrant

5. Q: What are the biggest
challenges related to CMS?
• Editor interface too heavy
• Vendors too slow at adding new features
• Lack of support and development from
IT
• Poor back-end performance
• Finding good, local system integrators
• To actually leverage the technical
potential of the platform
• …

6. Q: Which things are most
important regarding CMS?
•
•
•
•
•
User friendly: For end-users AND editors
Time-to-market
Performance and stability
Flexibility and open architecture
…

8. ”People don’t want a
drill machine,
they want a hole in
the wall”
- Philip Kotler

10. 1. Getting started

11. Homework for customers
•
•
•
•
•
•
•
•
•
•
•
Editors, content and information
Time-to-market
Project plan
Strategy & governance
Internal ressources
Unique requirements
Budget
Technology stack
Stakeholders
Project methodology
Interoperability

12. •
•
•
•
•
•
•
IT
Communications
Marketing
Web team
Legal + procurement
Management
?

13. xxx

14. PS: Budget
xxx

15. PS: Learn from
others
xxx

16. •
•
•
•
•
Is it just a CMS project for a web site?
Is it only for the intranet?
Mobile-first?
What are the expectations of the project?
Including a blog or newsletter solution as well?

17. It’s not much use to
know what is happening
if you don’t know why
You can’t know why
things are happening if
you don’t know what is
happening
Lou Rosenfeld: ”Marrying Web Analytics and
User Experience” (J. Boye Philadelphia 2009)
15

18. • How to be smart about gathering the
requirements?

19. • What’s the characteristics of good
tender / RFP?

20. ”The nice thing about
standards is that there are so
many of them to choose from”
Andrew S. Tanenbaum

22. • What’s the characteristics of a
winning proposal?

23. Don’t let vendors rush
the decision!

25. 2: Process
overview

26. WHICH IS THE LEADING

27. WHO WILL BUILD IT?

29. About the organisation
Project details, scope and goals
Project timeline
Important use case scenarios (max 10)
CONTENT
Selection criteria
Vendor-related requirements
Related projects
Characteristics and technical architecture

30. O P E N S O U RC E

32. SYSTEM INTEGRATORS

33. License models and pricing
xxx

34. Vendor
Vendor
Vendor
Vendor
Vendor
A
B
C
D
C
Scenario 1
OK
OK
-
Scenario 2
OK
OK
OK
OK
-
Scenario 3
OK
OK
OK
-
SCORING

36. Demo & test drive
xxx

37. Tips for the process?
xxx

40. 3: Marketplace
xxx

42. ”Trust, but
verify”
-Ronald Reagan

44. 2007 elephants:
- EMC
- IBM
- Interwoven
- Open Text
- Oracle/Stellent
- Vignette
2013 elephants:
- Adobe
- Autonomy (HP)
- EMC
- IBM
- Microsoft
- Open Text
- Oracle

45. •
•
•
•
•
•
•
•
•
•
•
Composite
Drupal
Dynamicweb
EPiServer
Microsoft SharePoint
Plone
Sitecore
Synkron Via
Typo3
Umbraco
…

46. •
•
•
•
•
•
•
•
•
•
•
CoreMedia
e-Spirit
Getit / Onion
Imperia
Infopark
OpenCMS
Pirobase
RedDot (Open Text)
SDL Tridion
Typo3
…

47. What about XYZ?
xxx

48. How to navigate
the marketplace?
xxx

50. Janus Boye, J. Boye
jb@jboye.com
@janusboye +
The international community
for web and intranet professionals