Qualtrics XM for Strategy and Research vs. ServiceNow IT Service Management

Qualtrics is a good medium for creating surveys and getting analytics back for it. I think it's easy to learn if you are in the business of creating surveys or if it's part of your studies. It can be a little overwhelming for a brand new user who has never created a survey for the first time. So onboarding could be better.

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.

• Qualtrics CoreXM is easy to use for quick one-time surveys or for measuring opinions over time
• It's great for sending/managing RSVPs for meetings or other gatherings or to collect important data like Conflict of Interest declarations.
• Qualtrics CoreXM's reporting and crosstab functionality is beefy and gets better all of the time. I'm always amazed at how easy it is to generate reports for sharing my survey response data and research.

Incentivized

• 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.

Incentivized

• The collaborate feature can be clunky and sometimes we have to remove access and add a person back in for them to see the survey in their lists
• We have a contract through our university and more than one person has created their account in the wrong place, causing some administrative headaches as that is fixed so that we can collaborate on surveys with them.
• I wish it was easier to organize my surveys into folders, there should be a more efficient way to do that.

Incentivized

• 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!

Incentivized

I was impressed a couple years ago when two heads of market research at Fortune 500 companies told me about them, and I've been even more impressed with the advancements I've seen in the last year. I like where the company is headed, and I look forward to using them again in a future role.

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.

All the menus are very user friendly and intuitive. I can always find exactly what I'm looking for and can change anything I need to with ease. All the elements of the survey are adjustable with very little effort and without confusion.

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.

We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.

Incentivized

For a massive system, page loads are reasonably quick, including searches.

Incentivized

Whenever we have had an issue with trying to figure out how to do something (even though the documentation is incredibly well put together) we have asked Qualtrics support and have always received our answer nearly immediately (I think in maybe 10 times, only once did a support person need to call us back). Qualtrics support is dedicated to solving customer issues right, and in the first contact, if at all possible

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.

Incentivized

I still use it. It does everything you need an online survey to do. From heat mapping to complex skip logic and display logic. I use it weekly and it never disappoints

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.

I like being able to easily integrate new colleagues by simply giving them a log in user name and password

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.

Incentivized

]Qualtrics] CoreXM is great if you want something that is a little more [long] lasting and impactful than a simple survey engine, but aren't quite ready for something that is a long term sustainable program. I would put [Qualtrics] CoreXM squarely in the large, defined project phase. CX is more of the program phase, and other lessor vendors are great for the pre-project definition phase

Incentivized

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.

Incentivized

ServiceNow works as an enterprise solution.

Incentivized

• Increased productivity due to the highly intuitive user-interface and template saving capabilities.
• Reporting and analytics are extremely valuable. Our team can track responses and share feedback/results extremely quickly.
• If a user has created a great template, they can share to external teams quite easily. It helps other departments!

Incentivized

• 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.

Incentivized