We provide solutions based on SharePoint for our clients. I'm managing a team that provides support. I am using SharePoint Online. Overall, I rate the tool an eight out of ten.
For collaboration, especially with large documents, it's a very good solution. Although, there's a learning curve. So, that's the only challenge. There's a learning curve, especially if you want to integrate with other solutions. Or if you want to make it full of workflows, there's a learning curve. Overall, I would rate the solution an eight out of ten.
I advise users to think about SharePoint's scalability if they have a huge use case. Otherwise, SharePoint is a good option to save internal and external files. Overall, I rate SharePoint a seven out of ten.
I give SharePoint an eight out of ten. We have 30 technical people that use SharePoint within our organization. I recommend that prospective users watch the instructional videos before searching extensively, as this will save them time. While the accompanying documentation may be lacking, many helpful videos can be found on YouTube and other platforms. I believe that investing time in these videos will ultimately result in time saved. We are a company that provides Microsoft cloud services and data sourcing. Our business involves reselling licenses and equipment.
My advice is SharePoint Online is good, but Microsoft does not recommend doing a lot of customization management. It is a good document manager, and content management system if they are using the out-of-the-box approach only. The out-of-the-box options are very good, but if we try to customize it a lot, then it's not recommended. I rate SharePoint Online seven out of ten.
In terms of what features I found valuable in SharePoint, I haven't found many. I had come from IBM and was very entrenched with Lotus Notes and the Lotus Notes environment. I love Lotus Notes. When IBM sold Lotus, we started to move away from Notes, and I didn't like it, and then I was made redundant. Now I've been outside of IBM, having to use Microsoft, and I hate it. My advice to people looking into using SharePoint for the first time is for them to look at how much data they have, and also look at the volume their data and data holdings are going to grow to. They should look at how long it would take to get to that point, then look at their ROI, and whether they would need to upgrade to another product in the near future. I'd say "Yes. Go for it.", but they should also look at the future, and how it would be long term. I'm rating SharePoint a seven. Yes, it's good for organizations to start on knowledge management, but you'd have to look at how quickly you think your data will grow, and how soon it would take to get to that point, because it can become unwieldy. Our company is a consulting partner of Microsoft. We're a service integrator that works in both the private and Australian Federal Government sectors.
IT business analysis, development and governance at a tech services company with 51-200 employees
Real User
2022-04-06T19:01:32Z
Apr 6, 2022
I'm using SharePoint as part of Office 365, using it as a part of Teams and under the hood of Teams, so yes, I'm still using SharePoint. SharePoint is deployed on public cloud. We have some projects where SharePoint 2019 is deployed as a server, but those are based on an integrations app, but mostly it's on Office 365, e.g. SharePoint Online. Microsoft is the cloud provider we're using for the platform. I want to highlight that some organic growth was missed with Teams, because there's still complicated switching between tenants, e.g. Teams and SharePoint users. In this case, Teams users may work in different organizations, or are guests of different tenants and different organizations. Switching between tenants, or the ability to streamline and organize identity management logging into the system, e.g. to the cloud, to Office 365 with one ID or organization ID should provide options to do work with many organizations at the same time. Currently, there is still the need to switch from one organization to another, to get the full toolsets of a particular tenant, so for users, that's quite annoying. For one organization that fits, and that works fine for an organization with guest users, but when we have multi-tenant situations, when people are collaborating on different projects, and when initiated or hosted by different organizations, switching from one organization to another should be improved. We have 40 to 50 users of SharePoint, and they are involved in various projects run by customers. We also add users from other organizations, so the total collaboration space may include 200 to 300 users. My advice to people thinking about using SharePoint, the very important lessons I learned during years of using the tool, is for them not to fight with it, e.g. they should not start to use it based on what they initially wished to use it for. It's best to first spend more time in getting a better understanding of the tool and its relevant capabilities. Learn SharePoint first. Spend time learning it. I would give SharePoint a rating of nine out of ten.
IT Manager at The Ventoulis Institute for Local Journalism
Real User
2021-11-16T18:08:00Z
Nov 16, 2021
I would say definitely go with it. I haven't had any issues with it for years, so go with it. SharePoint has always been good. Microsoft has always been great. I'll rate it a 10 out of 10.
My advice for anyone implementing this solution is to first try everything that you want to do in a virtual environment, with people who know how SharePoint is programmed. You need to understand the psychology of business users because most of them omit essential steps when they are creating the business process model. They are used to doing things in their head, but the machine is not aware of everything that they know so some steps are missed. Ideally, you want to buy a bunch of post-it notes and test your processes manually, by playing with different scenarios. You have to tune the business processes. I have seen projects fail because the debug phase of the business process design was not thorough. This solution is useful for optimizing usual business processes, like writing an invoice. For any organization with more than one person in it, if they are trying to organize things to let people in the company know what others are doing, then this solution is good for them. While this workflow operating system is better than others on the market, it is uncomfortable and expensive to really implement what you need. I would rate this solution an eight out of ten.
Compared with other products, SharePoint is very good. We do not have other products that are as good as SharePoint. SharePoint is definitely richer in features with functionality which helps us to get our work done. I would rate SharePoint a 10 out of 10. The solution is integrated with the entire Microsoft platform, from e-mail to Azure computing, so the solution as a whole is easy to manage and has a central administration that facilitates the view of the entire environment.
Workflow is helpful in the allocation of tasks in any close-knit teams, teams which are not sized beyond 20 to 25 at the most. If the workflow can be made more intelligent, adding value to the information rather than just pinging and cascading and shooting of alerts, that can really help with value-add and to save time. There was one techy who designed and implemented this. Currently he continues looking at what is required, but in terms of continued support I don't have any staff on it. When any fixes are required, he handles them remotely. We don't have anyone on staff to manage it. We expect the scale to go up and more business to pour in so we expect the number of users is going to increase. We would definitely be looking at a little more intelligent implementation of workflows so that we've got better control and better delegation of mandates. I would rate it at seven out of ten. It works for me. I haven't seen anything parallel.
Enterprise Architect Channels at a tech services company with 10,001+ employees
Real User
2018-12-10T08:29:00Z
Dec 10, 2018
When I am choosing a product, I think of the quality of service, economy of sale, licensing, implementation, the skill set of documentation, SaaS availability, and skill set. These are the constellations in mind when I'm choosing a product. I think SharePoint can definitely look at taking it to the next level of customer experience. It's not about how jazzy it looks and so on but it's more of how intuitive it is and how it can basically enable a user-friendly experience. When downloading a document, ask yourself how can you enable it? How can you enable some kind of a decision tree, and how can you have some kind of a bot in there which can do some assistance for the customer who was supposedly struggling to find the document, or is not able to find what to search. The bot can intervene and help the user with some alternate keywords and to clearly define what the user is looking for. Those kinds of things should be the next addition to SharePoint.
System Manager at a financial services firm with 11-50 employees
Real User
2018-07-29T06:51:00Z
Jul 29, 2018
My advice would depend on the use case. SharePoint, for us, is the most suitable because we use mainly Microsoft products. So for us, it's the way to go because the integration is solid. If colleagues have other products, it depends on what they're asking. Look at the best option. It's not that I'm saying, "You have to use this product because it's the greatest." Consider what you need, what you want. It's very stable. I don't call it a document management system, I call it a multifunctional document system. You can do a lot of things with it. It's just incredible how much. I really like that we have been able to automate a few steps that people had to do. Also, this process was only possible with SharePoint, because of the integration of other Office products. We're using the basic Microsoft suite and integration was a very big part of it.
SharePoint is a Microsoft-based platform for building web applications. It covers a widerange of capabilities and while it is appropriate for experienced webdevelopers, even non-technical minded users can easily navigate through thesystem and execute functions such as collaborating data, managing documents andfiles, creating websites, managing social networking solutions, and automatingworkflow. Major areas that SharePoint deals with are websites,communities, content, search, insights, and...
Overall, I rate the solution a seven out of ten.
We provide solutions based on SharePoint for our clients. I'm managing a team that provides support. I am using SharePoint Online. Overall, I rate the tool an eight out of ten.
For collaboration, especially with large documents, it's a very good solution. Although, there's a learning curve. So, that's the only challenge. There's a learning curve, especially if you want to integrate with other solutions. Or if you want to make it full of workflows, there's a learning curve. Overall, I would rate the solution an eight out of ten.
I advise users to think about SharePoint's scalability if they have a huge use case. Otherwise, SharePoint is a good option to save internal and external files. Overall, I rate SharePoint a seven out of ten.
I give SharePoint an eight out of ten. We have 30 technical people that use SharePoint within our organization. I recommend that prospective users watch the instructional videos before searching extensively, as this will save them time. While the accompanying documentation may be lacking, many helpful videos can be found on YouTube and other platforms. I believe that investing time in these videos will ultimately result in time saved. We are a company that provides Microsoft cloud services and data sourcing. Our business involves reselling licenses and equipment.
My advice is SharePoint Online is good, but Microsoft does not recommend doing a lot of customization management. It is a good document manager, and content management system if they are using the out-of-the-box approach only. The out-of-the-box options are very good, but if we try to customize it a lot, then it's not recommended. I rate SharePoint Online seven out of ten.
In terms of what features I found valuable in SharePoint, I haven't found many. I had come from IBM and was very entrenched with Lotus Notes and the Lotus Notes environment. I love Lotus Notes. When IBM sold Lotus, we started to move away from Notes, and I didn't like it, and then I was made redundant. Now I've been outside of IBM, having to use Microsoft, and I hate it. My advice to people looking into using SharePoint for the first time is for them to look at how much data they have, and also look at the volume their data and data holdings are going to grow to. They should look at how long it would take to get to that point, then look at their ROI, and whether they would need to upgrade to another product in the near future. I'd say "Yes. Go for it.", but they should also look at the future, and how it would be long term. I'm rating SharePoint a seven. Yes, it's good for organizations to start on knowledge management, but you'd have to look at how quickly you think your data will grow, and how soon it would take to get to that point, because it can become unwieldy. Our company is a consulting partner of Microsoft. We're a service integrator that works in both the private and Australian Federal Government sectors.
I'm using SharePoint as part of Office 365, using it as a part of Teams and under the hood of Teams, so yes, I'm still using SharePoint. SharePoint is deployed on public cloud. We have some projects where SharePoint 2019 is deployed as a server, but those are based on an integrations app, but mostly it's on Office 365, e.g. SharePoint Online. Microsoft is the cloud provider we're using for the platform. I want to highlight that some organic growth was missed with Teams, because there's still complicated switching between tenants, e.g. Teams and SharePoint users. In this case, Teams users may work in different organizations, or are guests of different tenants and different organizations. Switching between tenants, or the ability to streamline and organize identity management logging into the system, e.g. to the cloud, to Office 365 with one ID or organization ID should provide options to do work with many organizations at the same time. Currently, there is still the need to switch from one organization to another, to get the full toolsets of a particular tenant, so for users, that's quite annoying. For one organization that fits, and that works fine for an organization with guest users, but when we have multi-tenant situations, when people are collaborating on different projects, and when initiated or hosted by different organizations, switching from one organization to another should be improved. We have 40 to 50 users of SharePoint, and they are involved in various projects run by customers. We also add users from other organizations, so the total collaboration space may include 200 to 300 users. My advice to people thinking about using SharePoint, the very important lessons I learned during years of using the tool, is for them not to fight with it, e.g. they should not start to use it based on what they initially wished to use it for. It's best to first spend more time in getting a better understanding of the tool and its relevant capabilities. Learn SharePoint first. Spend time learning it. I would give SharePoint a rating of nine out of ten.
I would say definitely go with it. I haven't had any issues with it for years, so go with it. SharePoint has always been good. Microsoft has always been great. I'll rate it a 10 out of 10.
I rate this solution nine out of 10.
No
My advice for anyone implementing this solution is to first try everything that you want to do in a virtual environment, with people who know how SharePoint is programmed. You need to understand the psychology of business users because most of them omit essential steps when they are creating the business process model. They are used to doing things in their head, but the machine is not aware of everything that they know so some steps are missed. Ideally, you want to buy a bunch of post-it notes and test your processes manually, by playing with different scenarios. You have to tune the business processes. I have seen projects fail because the debug phase of the business process design was not thorough. This solution is useful for optimizing usual business processes, like writing an invoice. For any organization with more than one person in it, if they are trying to organize things to let people in the company know what others are doing, then this solution is good for them. While this workflow operating system is better than others on the market, it is uncomfortable and expensive to really implement what you need. I would rate this solution an eight out of ten.
Compared with other products, SharePoint is very good. We do not have other products that are as good as SharePoint. SharePoint is definitely richer in features with functionality which helps us to get our work done. I would rate SharePoint a 10 out of 10. The solution is integrated with the entire Microsoft platform, from e-mail to Azure computing, so the solution as a whole is easy to manage and has a central administration that facilitates the view of the entire environment.
No.
Workflow is helpful in the allocation of tasks in any close-knit teams, teams which are not sized beyond 20 to 25 at the most. If the workflow can be made more intelligent, adding value to the information rather than just pinging and cascading and shooting of alerts, that can really help with value-add and to save time. There was one techy who designed and implemented this. Currently he continues looking at what is required, but in terms of continued support I don't have any staff on it. When any fixes are required, he handles them remotely. We don't have anyone on staff to manage it. We expect the scale to go up and more business to pour in so we expect the number of users is going to increase. We would definitely be looking at a little more intelligent implementation of workflows so that we've got better control and better delegation of mandates. I would rate it at seven out of ten. It works for me. I haven't seen anything parallel.
When I am choosing a product, I think of the quality of service, economy of sale, licensing, implementation, the skill set of documentation, SaaS availability, and skill set. These are the constellations in mind when I'm choosing a product. I think SharePoint can definitely look at taking it to the next level of customer experience. It's not about how jazzy it looks and so on but it's more of how intuitive it is and how it can basically enable a user-friendly experience. When downloading a document, ask yourself how can you enable it? How can you enable some kind of a decision tree, and how can you have some kind of a bot in there which can do some assistance for the customer who was supposedly struggling to find the document, or is not able to find what to search. The bot can intervene and help the user with some alternate keywords and to clearly define what the user is looking for. Those kinds of things should be the next addition to SharePoint.
With this product, have a decent skill set in-house. Most important criteria when selecting a vendor: support.
My advice would depend on the use case. SharePoint, for us, is the most suitable because we use mainly Microsoft products. So for us, it's the way to go because the integration is solid. If colleagues have other products, it depends on what they're asking. Look at the best option. It's not that I'm saying, "You have to use this product because it's the greatest." Consider what you need, what you want. It's very stable. I don't call it a document management system, I call it a multifunctional document system. You can do a lot of things with it. It's just incredible how much. I really like that we have been able to automate a few steps that people had to do. Also, this process was only possible with SharePoint, because of the integration of other Office products. We're using the basic Microsoft suite and integration was a very big part of it.