Drupal vs. Jive

Overall, I would give my rating of Drupal a 7/10 because there is an easy user experience for those without a website background but there is some technology work required to build more website capabilities that aren't as user-friendly. Drupal is specifically well suited to update content (like changing Relationship Manager cards when there is employee turnover), post announcements (putting up a holiday banner to let our customers know the dates we will be closed over Thanksgiving, Christmas, etc., and creating a sophisticated website hierarchy of pages (for our firm, several dropdowns depending on if you're looking for personal banking, business banking, investment banking, about us, etc.).

Incentivized

It's definitely worth considering Jive for the type of application we've developed i.e. a central shared repository for all employees to host and discuss information. I can't say I have ever used a superior tool, but they may exist. I'm just not sure I would want to use it exclusively for file hosting, though. It does integrate with various other tools, so perhaps it would be fine if used in conjunction with another tool for that purpose.

Incentivized

• It has excellent security features and consistent updates.
• It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
• There is a large online community of Drupal users that consistently help answer any questions and issues

Incentivized

• Individual design
• Presence of Russian language (localization can be independently established)
• You can configure several information tapes with different themes. One for work, the second for communication
• A newly-arrived network user immediately receives a prepared block for beginners. After completing several game tasks, the user will receive the basics of using Jive.
• There is a template for each scenario. There is even a template for planning R&D, and there are more than twenty of them.
• Integrates with MS Office, Google Drive, Google Docs
• There are all platforms (even Winphone and blackberry)
• You can create forum threads

Incentivized

• Security and new release notifications are a hassle as they happen too often
• Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
• Steep learning curve, but worth it

Incentivized

• Search functionality is very weak
• The information architecture and taxonomy doesnt allow for easy discoverability of content
• It's hard to navigate the and find spaces/groups that I already know about
• The main profile/interface does not allow easy access to key tasks or common tasks.

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

There are always external factors that can impact this decision but currently, the Jive platform is maintaining its lead in the market place in this area. If the innovation in this space by Jive continues, then this number will remain high. Integration with other systems and adaptability to changes in the market or in client needs will also make this decision hard to predict more then 6 months into the future

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

It was harder to use that expected. The admin needs to be code savvy to truly customize the system. And users need to trained on the system and the setup. Trainings and monitoring need to continue to enforce use.

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

Uptime was OK. But there was one day that the system crashed for a whole day. Our company was unable to operate. And all the plugins to word/excel froze causing those systems to freeze.

Jive posted a statement to the media saying all customers were up, but we were not.

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

The product worked as designed. It just didn't work for our needs.

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

They did an OK job when I needed them. Except for the one day the system went down. Jive pointed the finger at the hosting company, and the hosting company pointed the finger at Jive. No reliable information came to us.

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Jive online training is there. It is OK/average. I feel some other companies are doing better. It is not a piece that is required to have a successfully implementation, but it could be useful to improve it

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

If I did this over, I would hire out the implementation. They know the best practices and could have guided us to make an easier to use setup.

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

We had a Google phone number set up before and Jive was a lot better option than that. It is more consistent and can be configured much easier and with more advanced settings. Additionally, based on the pricing as well as working with the rep on our account, it was a perfect option for us

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• reduce email traffic
• reduce amount of files/documents scattered & lost across shared drives
• increased discovery, awareness and interaction of historically more separated individuals & team functions across the organisation
• from an IT perspective, we've benefited from improved IT operations (e.g. troubleshooting info shared and easily searched/found with all team members - such that even junior team members can solve technical problems outside of business hours, lessening the burden for standby/call-in for more senior team members)

Incentivized