<p>When I discuss SharePoint's value with various decision makers one thing always comes up: the value of using it as a single platform to fill multiple needs within an organization. Companies may have initially implemented SharePoint as a way to collaborate and share data, but then find they also have the tools needed for a corporate intranet or public website. An initial investment provides a path for multiple solutions. This, for many reasons, can be a very appealing approach.</p><p>A compelling business case for implementing SharePoint isn't hard when you look at these capabilities. But a good business case isn't enough to make for a solid and powerful SharePoint implementation. To realize the value, it will be important for your organization to embrace the changes required for success. I'd like to highlight some of the potential areas of concern I've seen in my work on SharePoint implementations with various organizations and show some ways to get past roadblocks or find detours to help you get to your final destination.Look at Things Differently</p><p>Most organizations have gotten things down to a science when it comes to deploying and implementing software. Typically there's an operations team that keeps the servers up and running; a team of developers building solutions; and a team that serves as a help desk for users. Some companies have groups that are dedicated to monitoring the network and others that look just at security.</p><p>All of these roles are wonderful to have within an organization and can provide great value. But what happens when a single platform touches every area of the organization? Who will own it and how will decisions get made?</p><p><a href="http://www.cmswire.com/cms/social-business/a-square-peg-in-round-holes-using-sharepoint-for-multiple-solutions-023859.php">Keep reading...</a></p>