SharePoint Hierarchy of Needs

Rescuing a SharePoint site is usually a matter of identifying the problems, fixing them, and then re-launching the site. The issues can by myriad, but typically they fall into a few categories.

sharepoint_hierarchy_of_needs

Some SharePoint problems are more substantial than others and the issues should be corrected in the right order. Start at the bottom of this adapted Maslow’s hierarchy of needs for SharePoint.

 

 

 

  • Design – Users like attractive sites. While function should be preferred over form, a fresh coat of paint can really help.
  • Usefulness – Find a couple of great applications for the product and develop tools that perfectly fit those needs. These “killer apps” will reintroduce the program to the company in the best possible light. See more ideas on solving problems with SharePoint.
  • Accessibility – Use Office integrations, andmobile access to accommodate the myriad of ways users will want to use the site.
  • Search and Organization – Content must be easy to find and use. Minimize the number of clicks needed to find any piece of content.
  • Stability & Speed – If there are technical problems that have led to downtime or lost data, resolve those first. Users won’t trust the site with their information if they think it might be lost. Users are accustomed to fast load times for Internet pages and instantaneous movement for desktop applications. SharePoint should be similar.

Once the site has been significantly changed, re-launch it with a full round of training, user groups, lunch and learns, and word of mouth marketing. Continually add developments to the site, solving a growing number of problems, and listen deeply to user feedback when prioritizing your efforts.

For more power Sharepoint technique see our Sharepoint Tips.

Once the site has been significantly changed, re-launch it with a full round of training, user groups, lunch and learns, and word of mouth marketing. Continually add developments to the site, solving a growing number of problems, and listen deeply to user feedback when prioritizing your efforts.