<p>As I help people build out their SharePoint solutions many groups use the phrases "one single location to access content" or a "single source of truth" to describe their end goals. These are great goals and can play a huge part in successful SharePoint implementations, but in many cases it overlooks one key point: the context of the data.</p><p>The last thing that you want to do is provide a solution to your users that is simply a replacement for the current solution. Why go to all the trouble of moving your content to a SharePoint solution without taking the time to look at things differently and provide a solution that aligns with the daily needs of the users? Ideally your solutions are going to provide a way for users to work through a process with your solution supplementing and guiding them along the way. Your solution should be a tool that allows them to be guided through the actions required of them for the task at hand.</p><p>One scenario that I have seen lately is one department providing services to another department within a large company. This is common and could apply to any organization. The first department has created a word document that other groups complete and then return via email. This is an old process and as time has passed, the company has grown but the process has remained the same.</p><p>The group responsible for providing the services is now feeling overwhelmed and looking for a different solution. They had ideas around creating a central spot to complete and manage the forms. The thought was if we could point people to one spot, the process would be much easier.</p><p><a href="http://www.cmswire.com/cms/social-business/driving-user-behavior-within-your-sharepoint-solutions-021239.php">Keep reading...</a></p>