Try our new research platform with insights from 80,000+ expert users
it_user366102 - PeerSpot reviewer
Business Process Coordinator at a comms service provider with 10,001+ employees
Real User
Metadata is easy to index in the research engine. Wikis are limited and hard to use.

What is most valuable?

We are using metadata tags on documentation, indexed research, linked calendar to outlook, and controlled navigation.

We are not using libraries to classify information, but columns linked to metadata (customer, services, processes, and so on). We have generated a true document ID card, and metadata is easy to index in the research engine. We have a “Google-like” page dedicated to research, which includes refinement fields available to help in research.

How has it helped my organization?

We are only using it as a documentation storage system for around 500+ people, so we can find the right document at the right moment, as required. With metadata tags and acronyms, we were able to manage the company terms and create a common basis.

What needs improvement?

Various wikis are very limited; there is no integrated solution for communicators; master pages are too limited and require a developer; and libraries are sometimes useless.

Wikis are not simple enough and too hard to use. There could be auto links, for example, like you can implement in Confluence. A wiki should have an integrated table of contents and auto link to already available terms in the wiki, like Wikipedia works.

An integrated communicator would be an asset. You could use it to ask documentation owners when it will be available in the platform. It would work something like Facebook messenger.

Master pages are just too hard to manage because everything in SharePoint is linked. One level on one page might be a different level in another page; so you need time and failures before you succeed.

In general, it is a good product, but it has limited support and too much expertise required.

For how long have I used the solution?

I have used it since 2010. The company I work for has been using it since 2003.

Buyer's Guide
SharePoint
March 2025
Learn what your peers think about SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.

What do I think about the stability of the solution?

We never had any stability issues. In fact, our system is quite simple. We only experienced downtime three times in six years. This was only due to a VM management problem with human resources.

What do I think about the scalability of the solution?

We did not have any issues with scalability.

How are customer service and support?

Microsoft’s support is much too expensive and too complicated. We are not using their support at all. We are doing everything internally the best we can.

Which solution did I use previously and why did I switch?

We tried ShareDrive and Confluence. We stay with SharePoint because of the indexed content and corporate licenses.

How was the initial setup?

The initial setup was complex. We hired an external consultant to implement the Content Type Hub.

What's my experience with pricing, setup cost, and licensing?

I’ll strongly recommend to adopt metadata solutions, but with a SharePoint expert. This is expensive, but you save a lot of time.

Which other solutions did I evaluate?

We did not evaluate any other options because of corporate requirements.

What other advice do I have?

I recommend hiring experts and architects and preparing detailed business requirements for them.

Disclosure: My company has a business relationship with this vendor other than being a customer: Limited
PeerSpot user
it_user11634 - PeerSpot reviewer
Principal at a tech consulting company with 51-200 employees
Consultant
Choosing between SharePoint and Yammer

A caveat before we start: This post is referring to the current release of SharePoint – SharePoint 2013. If you are using SharePoint 2010 or older versions and want to introduce enterprise social networking (ESN) tools, your decision is more straightforward. Use Yammer or an equivalent product such as Jive or Newsgator, or do without until you upgrade.

Here’s the summary:

For organisations already using SharePoint 2013 for content management who want to leverage social networking features…

Use Yammer when: Use SharePoint when:
  • You want to use the superior social networking technology
  • You want a social network spreading beyond your organisation
  • There isn’t a good reason not to
  • You want to avoid confusing users with multiple user interfaces
  • You want to minimise identity management overheads
  • You have compliance needs that SharePoint meets but Yammer does not
  • You want an ‘on-premise only’ solution (and don’t want to use additional products)

Read on for the long version:

Do we have to use Yammer now instead of SharePoint for social activities and news feeds?

It’s a question I have been asked by many clients and event attendees who have invested in using SharePoint 2013 and/or Office 365 since the beginning of the year. The confusion has been caused by Microsoft seeming to be more in love with Yammer than SharePoint of late:

“In my customer meetings over the last few months, people have often asked, “What should I use for social? Yammer or the SharePoint newsfeed?” My answer has been clear: Go Yammer!”
- Jared Spataro, Director, Microsoft SharePoint Product Group1
“OneNote, Yammer, SkyDrive are growth drivers for Office”
- Kurt Delbene, President, Microsoft Office Division2

So the advice from Microsoft is pretty clear. If at all possible, choose Yammer.

There is also a specific reason for choosing Yammer over SharePoint:

  • You want to invite people into the network who are not licensed SharePoint/Office 365 users.

i.e. you want your social network to spread beyond the organisation. You can invite external users to participate in content within SharePoint, but they don’t get a profile or any level of personalisation features. They just get access to the content. Yammer gives every participant a profile and personalisation such as an activity stream of who and what you are following.

But there are reasons to not use Yammer, at least for now if you are using Office 365:

  • Do not want the overhead of maintaining an additional set of users accounts
  • Want enterprise search and Office integration
  • Regulatory issues with using the service

Whilst Yammer is included for free within an Office 365 Enterprise plan subscription, it still has its own separate user identities. There is integration thanks to federated sign-on: logging in to one will also log you in to the other. But it’s still two separate identities to maintain which adds to IT overheads. This is due to be resolved in the Autumn.

The social features within SharePoint are fully integrated with search and Office. This means you can view people and conversations in search results, and can co-author documents direct within the browser using Office Web Apps. None of this is currently possible with content stored within Yammer. Office integration is slated for Spring 2014.

The final key blocker for now is regulatory issues. Office 365 has higher security credentials than Yammer. It goes beyond the basic EU Safe Harbor Agreement to also support EU model clauses which covers additional EU member state data protection legislation. In the UK, that means IL2 accreditation for UK government bodies. At the time of writing, there’s still no comment as to if or when Yammer will be IL2 accredited.

There’s a reason to not use Yammer specifically for on-premise deployments of SharePoint 2013, and that’s simply that Yammer is cloud only, it’s an online service. If you want social networking content restricted to on-premise services, then stick with SharePoint 2013 or use an alternative on-premise enterprise social networking tool.

And finally, there’s another reason to not use Yammer for now. And that’s the ‘keep it simple’ principle. If the preference is to keep the choice of technologies as simple and consistent as possible for users, and you are already using SharePoint sites for content management, then stick with SharePoint unless you have a compelling reason to use Yammer that SharePoint cannot satisfy. Running two solutions that look similar, with some overlapping features but also some fundamental differences, can be confusing and may increase training/support overheads.

Is Yammer the future? Microsoft seems to think so and given they spent quite a lot of money to buy it, you have to assume they are serious. Integration with the other Office 365 services – Exchange, Lync and SkyDrive – is on the cards, along with integration with the Dynamics range including CRM. But enterprise social networking tools are still immature and who knows what the future may hold. I’m surprised the likes of LinkedIn haven’t started to encroach on this space. For now, use the tool that offers the most value for your organisation today. Vendors will say what’s in their interests. That’s not always as in alignment with what organisations need.

References

1 Yammer and SharePoint: Enterprise Social Roadmap Update – Microsoft, March 2013

2 OneNote, Yammer and SkyDrive are the growth drivers for Office – Microsoft, February 2013

3 A short guide to business impact levels – HMGovernment G-Cloud

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
SharePoint
March 2025
Learn what your peers think about SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
Founder & CEO at Solution Enablers
Real User
The workflow is a valuable feature

What is our primary use case?

Collaboration.

How has it helped my organization?

Single window information sharing.

What is most valuable?

Workflow.

What needs improvement?

It should have a lighter interface.

For how long have I used the solution?

More than five years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Founder/CEO at a computer software company with 51-200 employees
Vendor
There are no happy customers, only happy contractors.

We have used SharePoint for more than eight years.

In the 10+ years of being in traditional IT, I have never once heard of a happy customer of SharePoint, only happy contractors and IT personnel who feel safe in their jobs because SharePoint never quite works. I’ve even tried to find a happy customer. I couldn’t. 

This is probably harsh criticism to some readers, but in my honest view, SharePoint is a system that only really works for IT departments and the contractors who develop SharePoint, because the solution is folded into the existing enterprise agreements. It’s free because it wouldn’t have value on its own. There are no happy customers of SharePoint, only happy contractors.

Let’s talk UX. Employees today have little time for systems that don’t address their needs. If a team needs the ability to share files and that system restricts them, then IT has failed. SharePoint doesn’t really help in today’s world of mobile access, collaboration and sharing of content. 

SharePoint doesn’t provide real workflow so common practices are always having to be redone. This frustrates end-users and always makes IT look less than capable, which is unfair, because it’s SharePoint.

When systems require lengthy timelines to spin up, require additional expert staff to create and then ultimately under-deliver solutions to end users who then feel constrained, force-fed and unable to use the system, then the only conclusion I can make is that the product is sub-standard. While Microsoft has no doubt put tremendous resources into developing SharePoint (and is now saddled with a massive contractor partner channel that refuses to change its ways), the world has moved on. 

SharePoint requires too much administrator-level effort in order to launch. Typical installations of SharePoint require conversations regarding hardware, storage and access permissions which slow business down. SharePoint requires all of these things because the architecture is — in IT time — ancient and inflexible. Once those lengthy conversations are finished then the actual work begins in order to ensure SharePoint can function. This takes business time, money, and contractors are usually very happy in making sure everything is just right. 

Software should not require additional effort to operate effectively. Business should not need additional outsourced expertise in order to get a fileshare running. Then there are the operating concerns of security, governance and collaboration. SharePoint offers only read or read/write ability to files which is far less than competitors offer for a lower price. 

SharePoint isn’t necessarily any more secure than anything else and doesn’t offer the level of governance required for many companies. It cannot report in-depth user activity or provide policy automation out of the box. Ultimately SharePoint offers less than what you need for more than what you bargained.

Competitors are solidly in the market who offer better workflow, security, governance and collaboration. Box.com offers higher degrees of collaboration AND Office integration than SharePoint. 

If you’re a business that needs to collaborate on content, and has the desire to share that content outside your building to your executives on their phones or vendors in other locations, SharePoint is not the solution for you.


Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Practice Manager and Solutions Architect at a tech vendor with 1,001-5,000 employees
Vendor
It has transformed the way departments collaborate.

What is most valuable?

Depending on the customer’s needs, one or more features become more relevant and important. If I were to generalize and extract the most common features that the customers have used, I would say:

  • Web\document content management
  • Integration with the Office suite
  • Collaboration over the content, sites, BI, search, and workflows
  • One or two-way integration with other enterprise applications

I see the strength of SharePoint working as an extendable framework/platform for customers of various sizes, on premise as well as on the cloud, but not as an independent niche product/solution around a specific feature.

How has it helped my organization?

Our Intranet is built using SocialXtend, a SharePoint based product.

It has transformed the way we do our daily tasks and the way the departments collaborate over projects, opportunities, and other operational activities.

Knowledge sharing and access to information has been highly simplified.

What needs improvement?

Almost all of the areas of the product have room for improvement; some more than others.

  • At a high level, mobile, custom development/testing frameworks, BCS, external services integration, and BI may need to catch up more as compared to the other feature sets.
  • SharePoint is a combination of multiple products working together. It has come a long way, and the improvements are being pushed at a much faster pace than they used to be earlier. This fail-fast approach of adding features quickly instead of a longer release cycle is a much better way to develop a product in my opinion.

For how long have I used the solution?

I have been using SharePoint since 2001 in multiple capacities, such as a solution host, or as a full-fledged enterprise solution for on premise, as well as on the cloud.

What do I think about the stability of the solution?

My personal observation is that if the implementations are done in the right way by following the recommended best practices and guidelines, the product works just fine.

To be clear, I am referring to all the underlying products (IIS, SQL Server) as well as to the O/S.

There have been genuine issues. However, we have used SharePoint and CU to address them.

What do I think about the scalability of the solution?

We have not had scalability issues in SharePoint 2010 and onwards.

How are customer service and technical support?

Technical support is good.

Which solution did I use previously and why did I switch?

We used solutions from the Java world. Those, as well as this one, are based on the customers' needs.

How was the initial setup?

For simple farms, things are pretty straightforward. But for complex farms, I have not yet had that experience.

To be fair, it’s not SharePoint all the time. It’s a combination of other environmental factors and third-party products as well.

Disclosure: My company has a business relationship with this vendor other than being a customer: We are Microsoft Gold Partners.
PeerSpot user
PeerSpot user
Senior Business Analyst at a financial services firm with 10,001+ employees
Real User
We like the synergy with other applications in the MS Office suite.

What is most valuable?

Synergy with other applications in the MS Office suite. For example, with a single click from the MS Lync client, you can create an email in the Outlook client and vice-versa, amongst many other similar integrations between applications that previously did not speak to one another.

How has it helped my organization?

Collaboration became a lot easier. Meetings happened more frequently between colleagues across different locations sitting at their desks and not in special video conference rooms.

What needs improvement?

Better mobile optimization and a similar experience level across device types (desktop, tablet and phones). For most applications, MS SharePoint included, users are treated to different experiences across devices. For example, Excel works slightly differently (has fewer features/capabilities) on mobile when compared to the desktop experience. It would be nice to close this gap as much as possible, such that a user may have no qualms transiting between devices.

For how long have I used the solution?

I have been using SharePoint for over four years.

What do I think about the stability of the solution?

We did not have any stability issues.

What do I think about the scalability of the solution?

We did not have any scalability issues. It is as easy as adding new licenses for new users.

How are customer service and technical support?

Technical support was not as good as expected. Sometimes request took upwards of three business days.

Which solution did I use previously and why did I switch?

We used several single purpose software tools for each area of our need. We switched to MS SharePoint/Office 365 for a number of reasons, including: the seamless integration between the many apps in the suite; colleagues (users) are familiar with the MS office interface from Excel, Outlook, Word and PowerPoint and that shortens the learning curve considerably.

How was the initial setup?

Setup was straightforward.

What's my experience with pricing, setup cost, and licensing?

For non-profits, seek out non-profit licensing.

Which other solutions did I evaluate?

We evaluated eleven others.

What other advice do I have?

It’s the best in the class, but make sure your existing solution doesn't already meet your needs before making the decision to go the MS SharePoint route.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Office 365 Consultant at a hospitality company with 1,001-5,000 employees
Vendor
Workflows transformed our paper processes into digitized and faster processes. Document libraries lack flexibility.

What is most valuable?

The ability to create workflows.

How has it helped my organization?

Using the workflow as an example, it has helped to transform the conventional paperwork processes into digitized and faster processes.

What needs improvement?

Document libraries. At the moment, they still lack the flexibility you get in conventional Windows file systems. However, it has lots of features that make it a good replacement.

For how long have I used the solution?

I have used SharePoint for two years.

What do I think about the stability of the solution?

The fact that it relies on the Internet and runs in a browser means it is bound to have performance issues.

What do I think about the scalability of the solution?

I didn't encounter any issues with scalability. What I do know is that, when this is required, you will need the right skilled IT specialist to make the change. Often the right skilled specialists are not easy to find.

How are customer service and technical support?

Microsoft provides both online and phone support. Phone support depends on the plan you are subscribed to.

Which solution did I use previously and why did I switch?

We did not have a previous solution.

How was the initial setup?

The initial setup is a simple process. However, planning requires more time in order to gather user requirements.

What's my experience with pricing, setup cost, and licensing?

Setup an initial trial account with a pilot group to ascertain what is best for your environment.

Which other solutions did I evaluate?

We didn’t look at other options.

What other advice do I have?

If your users are already familiar with an existing Windows product such as Office applications, you won't regret jumping in.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Test Lead at a comms service provider with 501-1,000 employees
Vendor
Team sites allow multiple consultants to collaborate on a team project. We use workflows for onboarding processes.

What is most valuable?

I have found team sites offer much value to our organization. As a consulting company, it allows multiple consultants to collaborate on a team project for a customer.

We use SharePoint for companywide document management.

Although workflow is limited in SharePoint, we have used it for many onboarding processes, PTO requests, etc.

How has it helped my organization?

SharePoint has streamlined many processes and provided additional organization for our company. It has become a central location for both documents and productivity.

What needs improvement?

I would love to see a more robust workflow. There are 3rd party products such as Nintex and K2 that can be used, however I would like to see it built-in.

For how long have I used the solution?

I’ve used SharePoint for 2 years.

What do I think about the stability of the solution?

Stability issues have been found with the database. From the infrastructure side, most people use dedicated databases for SharePoint so a simple reboot usually fixes the communication issues.

What do I think about the scalability of the solution?

SharePoint is extremely scalable but requires planning ahead of time. You must answer some questions about your environment to determine how many servers and what SharePoint function(s) they will serve to meet the demands of your organization.

How are customer service and technical support?

I have never used Microsoft technical support for SharePoint in particular, but Microsoft support is very good.

Which solution did I use previously and why did I switch?

We used to use simple file shares and emails.

How was the initial setup?

SharePoint can be very complex to setup initially (both infrastructure and back end design and implementation). The more scalable the environment, the more complex the setup will be. Generally speaking, a 3rd party consultant will be needed to implement the solution.

What's my experience with pricing, setup cost, and licensing?

There are two options with SharePoint. They have an on premises and a cloud solution.

Which other solutions did I evaluate?

We did not look at alternatives.

What other advice do I have?

Hire and communicate with a 3rd party consultant.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free SharePoint Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free SharePoint Report and get advice and tips from experienced pros sharing their opinions.