If you were talking to someone whose organization is considering Box, what would you say?
How would you rate it and why? Any other tips or advice?
My advice is to use this solution. Overall, on a scale from one to ten, I would give Box a rating of nine.
We like this solution, and we prefer to work with the Box consulting team. Basically, for a large company, we would recommend that people work with their professional services just to get things set up quickly and completely. It is possible to do this on your own, but it is faster if you have help from Box. Their pro services are very good. I would rate Box an eight out of ten. Eight is about as good as somebody is going to get. There is always room for improvement, but I don't have anything quantifiable to make it a ten.
On a scale of one to ten, I'd rank Box a 10. And I rank their customer service a 9.5. Because they're not as good as GravityZone, but they're better than anybody else out there.
It's a good tool for everything. It's very similar to SharePoint. I would recommend Box if you are going off-site to meet clients, for mobility purposes. If not, then I would suggest SharePoint. On a scale from one to ten, I would give Box a rating of eight.
I would rate this solution a seven out of ten.
My advice to anybody who is considering this type of solution is to first formulate the use case. Box has certain limitations, but it is very plain and easy to use. If you need collaboration in terms of document management then it provides a simple interface that offers differing levels of granularity in terms of access control. This is a good solution but it does not address all of the use cases for a content management system. I would rate this solution an eight out of ten.
This solution has evolved and improved over the past six years. Originally, we had some issues with locking files when somebody was using it. This has been improved. Also, we had a lot of issues with duplicate files because of the fact that two people were opening the same file and modifying it. We ended up having two versions of the same file and we needed to manually merge the changes that were made in both. This is something else that has improved a lot. The suitability of this solution really depends on the needs and requirements. Some of the former Google Docs users found the sharing complex, so it depends on where you are coming from and what you are looking to do. The biggest lesson that I have learned using this solution is that some people assume it's very simple to understand the pointers. However, there are some important things to understand with respect to the differences between how to share a file or folder, and some people find it a little complicated to use. It's really a matter of a five-minute instruction, and then they've got the right answers and can use it better. I think that the most important thing is to communicate to the users how to differentiate the best way to use it so that they understand the idea behind it. Also, to explain to people that there's a lot of independence, but you need to understand the use case to do it correctly. I would rate this solution an eight out of ten.
What do you like most about Box?
Thanks for sharing your thoughts with the community!