Twelve Common Pitfalls to Avoid (and Best Practices to Follow) When Embarking on a Web Content and Experience Management Project
Pitfall 8: Underestimating hardware needs
Get more server power than you need today.
Web CMS packages -- even those at the departmental level -- are notoriously resource intensive, on both management and web tiers.
On the web or "delivery" tier, if you get creative with things like personalization and metadata, your database will fill up with all kinds of interesting and potentially useful records that could grow to dwarf the storage size of your actual content. You do yourself no good to design and implement the perfect CMS, only to find that your server performance is prohibitively slow for internal and external users alike.
That's why clustering and load balancing aren't just for the largest Web CMS installations anymore. Even if you license a cloud-based Web CMS, you may need to replicate some capacity or capabilties on-premise. So if you are a mid-sized company or larger make sure your CMS vendor and IT department are on board regarding adequate hardware needs.
Pitfall 1: Selecting a Web CMS package before developing solid requirements and a business case. Read the details of Pitfall 1 here.
Pitfall 2: Not getting a clear mandate from the top. Read the details of Pitfall 2 here.
Pitfall 3: Thinking a web content management package will provide a full CMS solution. Read the details of Pitfall 3 here.
Pitfall 4: Not involving internal Web CXM stakeholders from the very beginning. Read the details of Pitfall 4 here.
Pitfall 5: Involving only internal stakeholders. Read the details of Pitfall 5 here.
Pitfall 6: Spending insufficient effort describing and organizing content, and underestimating migration times. Read the details of Pitfall 6 here.
Pitfall 7: Picking a CMS package that doesn't play well with other company applications. Read the details of Pitfall 7 here.
Pitfalls 9-12: Coming soon...