For my third research blog I decided to look to see what was wrong with using SharePoint. All programs have their flaws and I am certain this one is no exception. By reviewing the flaws we can be prepared for a couple of things. For one, we can review them to make sure that they are credible complaints and not something someone said to bring the image of Microsoft down. The second is that if they are creditable there might have been an update to the program in case someone asks. The third reason would be if it is a known problem with no solution at this time we can avoid mentioning it in a corporate white paper. Why make ourselves look bad? The purpose would be to inform and sell products. An educated consumerist could find this information out and then we could give a generic “They are aware of the problem and they are currently trying to fix it” answer.
Some complaints I had found were. “It’s a crappy mish-mash of multiple technologies.” This can be a problem as SharePoint uses various coding languages so that a programmer must be knowledgeable in at least a few. I believe that this would not have any effect on users who are just trying to create a team in the business world. My favorite complaint was, “There are two SharePoint products, which is confusing.” Any research done would show that one has fewer features than the other. Something one would point out in any marketing documentation about the product.
It’s always helpful to find out what problems exist with a program so that one can fix them in the future to create a better product than before.
Identify Sources
These blogs should identify researched sources, as the examples we provided do.