Strategy

From implementations to migrations
Below are strategies I apply when working with different SharePoint projects

Architecture

If deisgning an SharePoint on premise environment from scratch, a great deal of planning and preparation is needed ahead of time.

Branding

SharePoint branding can be a complex task depending on the level of customizations needed.

Migrations

Migrating from SharePoint 2003, Cold Fusion or file shares to moving to Office 365. Migrating to a newer version of SharePoint is never a bad descision!

Administration

Keep your environment in check and stable with up to date security patches and hardware requirements.

I could write a book about this topic. But there are already several out there and not very engaging. So I'll keep this short. I have seen some amazingly complex migrations into SharePoint. The only migration type I have not seen is a migration AWAY from SharePoint. With good reason. SharePoint provides you the ability to manage and maintain almost any content requirement, with the flexability to inject automation of your business processes. Over the years, I have migrated content from environments like Cold Fusion, file shares and even SharePoint 2003. There are few challenges I have not come across at least once in my career.

Be that as it may, there are always obsticals that need to be called out and planned for. Customizations, workflows, Managed Metadata, look up columns are just a few common "gotcha's" that have to be identified. That is where a good deepdive can help plan a successful migration. Equally important is the user adoption. Let's face it, without your employees knowing where their content is, a SharePoint adoption can fail before it gets a chance to start.

Migrations

Architecture

Hardware: This is one area I take great pride in. Having a positive end user experience starts at the core. Making sure your hardware and network structurally sound is critical for a stable and responsive environment. You must take into consideration your audience and how they are going to use SharePoint. Are they technically savvy? are they going to build out their own custom workflows? Add tons of content along with tons of metadata and site columns? Is the content going to be large content like Photoshop or AutoCAD files? All this goes into the planning of the hardware.

SharePoint Configuration: Every company uses SharePoint differently. Unfortunately, There is no cookie cutter environment that works for everyone. I prefer the less is more mentality. If clients are not going to be using Reporting or Translations or the App Store, keep it unconfigured. This keeps the farm complexity low. CPU and RAM cycles wil be low and when it comes time for patching the enviornment, the odds of a minimally deployed farm succeeding in patch updates are higher than a fully deployed farm.
But dont get me wrong, sometimes a SharePoint farm needs to be fully deployed. And with that sort of requirement, you need the hardware (see above) to match the configuration. In this regard the system admins that hold the keys to the hardware world, have to comply. Skimping on RAM or HDD space or CPUs will only cause inconsistancies in the farm to the point you need Sherlock Holmes to find the issue. In which case, Sherlock will tell the admins, "We need more RAM."

Taxonomy: This is a word used far too loosely in my humble opinion. It can be used to apply to the entire scope of site architecture all the way down to the site column metadata. I prefer to keep the scope of Taxonomy focused on the usage of Managed Metadata in a farm.
Managed Metadata is critical to a company where they want to keep their content organized and easy to find. Some clients have been scared away from using folders inside libraries and are then coerced to use strictly metadata to keep their content organized. To me this is a MASSIVE misconception that has some basis in truth WAY back in the early versions of SharePoint and 2010. Back in the day, it was almost impossible to code around folders because SharePoint saw a folder as nothing more than a single item. But SharePoint is much more functional now and I think Microsoft finally admitted that folders are simply not going away. With that said, Managed Metadata is a great way to be able to surface content when searching for a specific item. So when you utilize combinations of Filtering, folders and search, it becomes easier to locate content and you just saved the client several minutes of frustration and non-productivity!

Our Office

Branding

You can brand anything. SharePoint is no exception. However, with the roll out of modern pages and the integration of Teams and Group sites, it gets a bit more complicated. When it comes to the classic page layout however, the broad flexability of what you can do with the look and feel of the environment is almost endless.

With the deployment of modern pages, there are substantial limitations on how you can customize the look and feel of the environment. However, those limitations do come with a great deal of enhancement in features. Such as the integration of Microsoft Teams, simplification in security, dynamic responses of list columns, etc.

Our Office

Administration

Administration of a production SharePoint environment is something I take very seriously. When I am approached by a client to come in and "fix" their SharePoint environment, the first thing I do on exploration of the environment is the security. Often times, a misconfigured and poorly performing environment is due to the security that was setup.

Lorem ipsum dolor sit amet consectetur adipiscing elit sed tempor incididunt ut laboret tempor incididunt dolore magna consequat siad minim aliqua. Lorem ipsum dolor sit amet consectetur adipiscing elit sed tempor incididunt ut laboret dolore magna aliqua. Ut enim minim veniam exercitation laboris ut siad consequat siad minim enum esqudiat dolore.

Our Office
Top