A common challenge when implementing SharePoint is clearly defining why the technology
is being rolled out in the first place. In order to achieve success, a clear definition
and understanding of the business value SharePoint brings to your organization is
necessary. This white paper walks through the process of assessing and prioritizing
business needs and properly developing requirements for SharePoint projects.
About the Author:
Dux Raymond Sy is a managing partner of Innovative-e, a SharePoint MVP, and author
of SharePoint for Project
Taking a generalized, fast food order-taking approach to a SharePoint implementation
is not effective in meeting business needs, yet countless IT departments frequently
make this fundamental mistake. That’s why in a lot of organizations, business users
often end up viewing SharePoint as nothing more than a glorified network share.
The key to meeting business needs is to first engage with the business users, understand
their pain points, and identify how SharePoint can provide the solution to address
these business-specific needs. You do not want to throw a set of solutions at business
users and then tell them to go look for a problem to solve.