Bloomfire vs. ServiceNow IT Service Management

Ad testing:

• PTS: needed to bring a new senior marketing team member up to speed on how we got to our current TV campaign
• Solution: Series featuring consumer insights, why specific spokesperson, agency brief, the entire creative process - scrips, animatics, rough cuts, feedback, and testing at each step. Including the actual creative from each step.
• Total time to build: 1 hour

Concept testing:

• PTS: things get lost, findable but version control
• Solution: everything in one placeConcepts, testing, IHUTs, verbatims, videos with transcripts. Reduces the possibility of missing something, helps with any builds (reuse), but gives us a the chance to dig deeper. Example: search on terms like "indulgent", or "crispy" or "share" much faster
• Total time to build: 1 hour

Incentivized

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.

• Quickly reach out to whatever employee segment you want to reach by posting a topic and it will send a notification to everyone in that group with a link to the posting.
• Bloomfire saves all of the previous posts so in your free time you can go to the site, and explore the various range of topics others have posted. The information on there will only be as good as the person posting it, but it will be people within your company and industry posting it. So it will always be helpful.
• Bloomfire is a place to be noticed by your peers. Have a great topic you want to express, my company allows all to post there as long as we keep it professional. So you can share your ideas or experiences in a safe and productive manner. But we do have some fun on there too!

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

• I would recommend adding a feature to combine different posts/series by job title (so in addition to the Revenue Ops category, there could be a structured walkthrough for Revenue Manager).
• Live Q+A sessions for group onboarding initiatives.
• Ability to label bookmarks by priority/job type.

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

Most likely we will renew, our team needs a refresher on possible opportunities to advance our usage and learning of opportunities to move this answer to a 10, can't live without it.

Incentivized

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.

Bloomfire is an easy-to-use platform for posting information and asking questions of my peers. It also has a user-friendly search capability. Yet like any other CMS, the secret to success rests in such items as the ability to use metadata to tag content or posts, and Bloomfire provides a wide range of options to make posting content and subsequently searching for it.

Incentivized

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

I have not needed to pose questions to the support team yet, as it is a very simple piece of software to use, however, its help documents and the bot ready to answer questions let me know I am in good hands. The help center could load a little quicker, but that's my only complaint.

Incentivized

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

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.

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

I like Bloomfire because it is more concise with the work I do whereas Google search engine would provide broader information. It has just been so user-friendly, and easier to use [than] I could have imagined. I would use this program over any other that I have tried in the past.

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

• Feedback from users in being able to perform transactions for members has greatly improved.
• There has been an increase in engagement of material presented in posts by learners in training classes.
• Reps and agents say they feel confident they can easily locate information if ever there is a need on the front line.

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