Embed Size (px)
Citation preview
Seven Deadly SinsWeb Content Management
Introduction
Buying Enterprise software is often complex The foundations of a project are set in the procurement It’s not uncommon for procurements to be compromised And for projects to fail... maybe slowly.
Sometimes buying the finest product from a reliable partner is not enough...
Seven Deadly Sins
Some advice on how to avoid some of the common pitfalls on your implementation, but particularly how start it well with a good procurement process.
Followed by a case study.
LustDon’t get distracted from your objective
Define requirements before you see the shiny stuff
Requirements must have a business value to your organisation
Make sure you can defend these requirements
Prove and test through business scenarios
1
GluttonyFocus, deliver what the business needs
Keep it lean - through tight, measurable requirements
Stay focused on non-negotiable “must haves” needs
Always refer back to these “must haves” throughout the project
Demonstrate delivery of musts to the business
2
GreedKeep it simple, don’t boil the ocean
ECM? Or a solution set that matches your requirements?
Remember core “non-negotiable” requirements
Manage a tight proof of concept
Deliver demonstrable value in phases throughout the project
3
SlothMotivate the business to participate
Empower your authors - people generally want to be published
Ensure the processes and tools fit the way they work
Author adoption is critical to a projects success
Maintain your energy and investment as the project matures
4
WrathDon’t fail the business
Build a resilient and reliable solution you can maintain
Deliver on your business requirements
Measure and communicate that success throughout the project
Spread the risk/reward with your stakeholders
Be agile, keep pace with changing business needs
5
EnvyDon’t envy your competitors, let them envy you.Don’t forget your audience, delighting them is your objective
You are building a business communication tool, or a community – not an IT system
Enable your business users to create cool stuff, let IT focus on core business innovation
6
PrideBe inclusive, involve the business, your vendor and your audienceGet business backing early in the project
Encourage people to participate, become stakeholders and business sponsors
Associate owners to requirements and keep them in the loop
7
So, contrived biblical references aside..Seven Deadly Sins of Web Content Management
Case Study - AstraZeneca
The task– 250+ AstraZeneca Websites. – Support for websites in 27 languages– 400 globally located site owners and content editors. Mixture of AZ
and external agency content editors.– 1 million registered website users– 100 million page views per annum– 3000 term taxonomy (in 27 languages)– ”AA” Accessibility (or better) websites
AstraZeneca – Selection Process
RFP– Over 700 functional, non functional requirements, each with a
business owner– Use Cases provided to add context
Scenario based demonstration day– All had to deliver demonstrations based on the Use Cases – Attendance by all major stakeholders, from 5 geographies
Pilot– 4 diverse websites focused on ‘Must’ requirements– Gained business confidence in the project – Proved technical architecture & relationship
Conclusion
Who owns the website? Involve and enable the business users from the start Invest time in building strong, measurable ‘must have’
requirements that you refer back to throughout the programme
You’ll find people that want to be published - user adoption is critical to your success
Devolved management is critical to your agility Choose a partner, not a vendor Don’t forget why you are doing what you are doing..
![[Drum] Joe Morello - Rudimental Jazz.pdf](https://img.pdfslide.us/doc/110x75/577c80b51a28abe054a9d86c/drum-joe-morello-rudimental-jazzpdf.jpg)
