I’ve been through many SharePoint projects in the last 2 years and learned many lessons and seen good/bad practices. When I’m talking to Customers I always mention the four pillars (or four quadrants) of successful SharePoint deployments – it helps to put a structure around what I want to articulate. These are my quadrants:
In a little bit more details:
As a conclusion: I hope that this article helped to understand the four quadrants. The funny thing (maybe not funny at all) is that I’ve realized that there are many failed SharePoint implementations (some of them are not failed officially, but nobody is using it – which is a failure to me) because companies tend to focus only on the first quadrant (the Infrastructure). Ping me if you have any questions, anything to add or if you need any help (including explaining the importance of these areas to your project manager/boss :) ) We also have very good experience deploying SharePoint and delivering these important areas – ping me if you want to schedule a meeting! Thanks!
PingBack from http://www.anith.com/?p=1708
Great post, I'm somehow agree you, your first quadrants, I would like to say stability, any service has to be stable to be use by users, no matter how strong we are designing and implementing a new service, included SharePoint implementation, just one or two downtime or wrong functionality is enough for users to leave that service, and come back to their traditional service, and I believe that they are right. your new value service need to be stable, and off course infrastructure is very important for stability. I personally prefer to propose clients really simple, but value added and stable services, than a complicated and high level technically solution that might be down sometime, or a little hard for users to use them.
about the governance, off course it's very important, and I'm still waiting to reed your second part ;)
User Adoption, I also experienced lots of failed projects, I think there is a key, users or clients has to need those services we are proposing them, I meant, really requirements, not just as a luxury service, not just because any companies are using SharePoint, so we are going to implement it ! after implementation they are not going to use it really. specially when SharePoint market demands is so high, I personally trying to understand real requirements, real business needs, I will choose them, then it will be a really successful project.
Those peoples sited outside of IT department, I love to work with them, they know the exact requirements and business value. presenting on the value proposition instead of technical details is the key. I don't like to discuss with technical peoples, they always looking for a new, complecated, complex, innovative solutions, witch is not necessarily busiess requirement.
I believe, SharePoint, itself, has value for the business, so just an stable implementation, and governance planning, and demonstrating value added services in comparison of old service, and as you said, getting senior manager's satisfactions and their support will guaranty your success, and I'm suggesting couple of shots tequila for that day ;)
Thank you very much for those who came to see our session on the UC&C conference. These are the resources