Reality -- Actually, I believe it was. Many companies today are discovering that SharePoint has led to a rapid and uncontrolled spawning of user-created portals, just like that cute but pesky first pair of tribbles that spawned so many offspring so quickly that they almost overwhelmed the starship Enterprise.
I have heard many companies report to their astonishment that after deploying SharePoint, they had thousands of SharePoint sites thrown up by employees. One company recently told me, as they tried to work through a degree of shock that suggested the need for professional therapeutic intervention, that they had determined just that morning that there were 30,000 SharePoint sites on their network. Surely a team of programming tribbles produced such an application.
Reality -- You cry out, “How can this be a myth?” Before SharePoint, there was the option of central document repositories focused on tasks like market research, competitive intelligence, or technology research. Everyone would know where to go to find the company's material in the relevant domain. Now, with SharePoint sites being created by every department, geographic division, functional area, project team, committee, brand team, company softball team, and even individual staff members worldwide, there might be scores, hundreds, or thousands of places on the company intranet with just a little bitty piece of the puzzle. The easiest way to not share something is to obscure its location from people that might want it by scattering it against a giant backdrop of other material. Presto, hidden in "plain sight!"
Reality -- Who thought of this one? Once again, the easiest way to keep people from finding what they need is to put it in the middle of a lot of stuff they don't. If there are hundreds, thousands, or tens of thousands of sites posting content mentioning products, organizational units, competitors, marketing programs, development projects, employees, job titles, and everything else with no versioning, aging, quality control, strategic focus, or semblance of overall organization, the high-quality material fades to obscurity on search results, diluted way down by the mass of material, no matter how good the search technology.
Reality -- Yes, dear reader, SharePoint can implement traditional enterprise security models that are often effective for securing file directories, applications, and entire document repositories. But there are whole categories of content that do not easily fit into standard enterprise security constructs.
For example, consider licensed external research reports from industry experts and analysts. Such reports and content feeds often carry severe restrictions on who can seem them. A particular Gartner research report might be licensed only to one person, while another report from Gartner might have been purchased with the rights to share it internally. Or one Forrester content collection might be restricted to a department, while another is enterprise wide. SharePoint is totally uninformed on third-party licensed and purchased content usage restrictions.
Make SharePoint your collaboration platform for licensed external content and kiss your business rules goodbye on who can see what. I have been told of multiple cases of invoices for hundreds of thousands of dollars being delivered to companies by third-party information providers for single reports purchased with seat restrictions and then posted by well-meaning but clueless employees on generally-available internal SharePoint sites.
Reality -- This is my favorite myth about SharePoint. SharePoint is supposedly easy enough to use that anyone can create a personal, team, or department portal. And that is maybe true for a rudimentary portal that posts some documents and does light-weight RSS reading. But if a user with average computer skills decides to do anything more -- like install a Web Part, create a vertical content feed, or set security levels for documents -- the likelihood of success drops to roughly the equivalent of trying to hike Death Valley in the summer without a map. Rescue by experts will be required.
So get yourself 5,000 SharePoint installations on your intranet, and you also get yourself 5,000 new applications that need IT support. But since IT budgets are unlimited and IT staff is sitting around all day reading gear-head magazines because there is no IT backlog to work on, that shouldn't be a problem.
s