Kantata Cloud (formerly Mavenlink + Kimble) provides project management and collaboration software for small to mid-sized professional services companies. Features include resource management, project dependencies, time and expense tracking, file sharing, versatile user permissions, private messaging, planning and reporting.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
It is appropriate and even exceeds expectations 90% of the time. It makes project tracking very easy and visually accessible for most cases. The only occasion where Mavenlink came slightly short was for a special project that required more interaction options among project members. I am certain there are ways to work around that issue, but we did not find them.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
With Mavenlink when starting to assign tasks to people, set deadlines and milestones, and add files to our projects we can look at it all from a variety of perspectives, including a task tracker view and a Gantt chart view
Through Mavenlink each project also includes an activity stream where we can view all project details as they come up, as well as an activity feed for all the projects it is linked to.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
Although the company I currently work for does not use the product I have recommended that we do switch to Mavenlink. We will be opening some new sites internationally this year and I can see that Mavenlink would be a great product for us to use
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
I think Mavenlink is the most robust and best project management tool out there for an organization like ours. However, some of our staff feel like it isn't as user-friendly as it could be. From a Director point of view or a Project Manager point of view, Mavenlink is exceptional. From the point of view of a task-doer, it could be more visually appealing. Also, the mobile version isn't great.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
Very good integration with Google apps. Some complexity is called however in the synchronization between Google Tasks and Maven links tasks. This can sometimes lead to duplicate records in Google Tasks. It has been dissolvable that becomes cumbersome if not properly curated.
Mavenlink support is fantastic! Any issues that arise are always handled quickly and efficiently. Granted, we haven't had many issues to report. Typically, my team tends to only reach out to support if they need assistance remembering how to do something or asking about an improvement. We had Mavenlink build an integration when we first started using the software, and the support team worked hard to listen and improve the integration.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
We prepared questions in advance, and our trainer was an expert in what Mavenlink was and wasn't able to do. We were able to have multiple people trained at once.
The training was very well-organized. We were able to send questions in advance so the instructor knew what to cover, and the brought up related topics to maximize the usefulness of what they were teaching us.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Dedicate as much internal time to the implementation effort as possible, even if you're using a 3rd party or Mavenlink services. Your team knows your processes the best
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We have since switched over to JIRA and let me tell you, it was probably the best decision we have made as a company. We chose Mavenlink based on promises from the sales team about future roadmap work that really never happened. We thought Mavenlink would easily integrate with our billing software but we couldn't have been more wrong. We ended up never utilizing Mavenlink invoices as they don't even allow you to fully customize your invoices that go out to clients!
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Manvenlink is perfect for showing expenses and income over time and across people.
Manvenlink is adaptable for the integration and automation of the processes of each of our projects in order to optimize resources and improve operational performance.
Mavenlink allows us to determine if our projects are profitable or not, as well as save significant time by automating components such as recurring tasks and having templates, among other things.
Manvenlink is advantageous for our operations due to its simple portfolio management of our projects: manage several projects at once and receive a complete perspective of the development of each one at a glance.
Manvenlink kindly provides us with robust discussion threads, access restrictions, and built-in document management, allowing us to contextualize communications.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
