One of the bigger shifts that have occurred in the modern workplace is the ability for team members to work remotely.
In one of our recent blog posts, we explored why it is critical to prioritize SharePoint intranet features. Now, we will discuss another important principle to follow while implementing a SharePoint intranet. This is feature balance.
There has been a lot said and written lately around the SharePoint world, and frankly, it’s daunting for anyone starting out on a SharePoint journey to make heads or tails of it all. I am constantly asked questions about functionality from version to version, Office 365, Yammer, the app store, migration planning, governance models, and, of course, adoption tips to ensure that what you’ve built actually gets used once implemented. The issue many are having is that it’s near impossible to draw a definitive line in the sand and proclaim not only how SharePoint should be implemented, but also be strategically used by the organization overall.
When I last wrote on project-management topics in 2012, the SharePoint world was different, and my focus on was the tactical implementation of the product. Many customers had recently converted from 2007 to 2010, and there was a relative silence about enterprise features and deployments.
Topics: project management