Drupal 8

End-User Experience
The tool was relatively easy for the team to adopt and use.
Administrator Experience
The tool was relatively easy to set up to meet organization's requirements.
You can customize the administrator and user interface of this tool to your specific needs.
Basic Features
The "out of the box" features were as expected.
Average: 5 (1 vote)
New functionality or feature improvements are regularly introduced.
Average: 3 (1 vote)
Reporting & Analytics
You can access, use and report data in useful ways.
Average: 1 (1 vote)
Customer Service
The customer service experiences are timely, helpful, and resolved to satisfaction.
Average: 5 (1 vote)
Advanced Features
These features clearly differentiate the tool from other options.
Average: 3 (1 vote)
This tool ntegrates well with other systems.
Average: 3 (1 vote)
Vendor Maturity
The company offers training and user groups or similar foundation of support for the tool.
Number of Staff Regularly Using the Tool: 
Organization Type: 
Trade association
Primary Job Function: 
Years Using Tool: 
1-2 years
Organization Revenue: 
Don't Know

I've managed content on Drupal sites for several organizations over the years. Drupal 8 is certainly an improvement over Drupal 7, but I wouldn't recommend adopting D8 without reservations. The complexity and "box of legos" structure that can be built into anything imaginable is not the best fit for all organizations. A more turn-key CMS like Wordpress should be strongly considered before any organization commits to a Drupal build.

The good:

1. Endless customization possibilites: The structure of D8 is unrivaled in this area. If your organization has unique structural requirenments, or forsees the need to change strucuture in the future, D8 is a great choice.

2. Content moderation: D8 makes this very easy. The tool isn't perfect, but it works better than most moderation tools.

3. Security: D8 is among the most stable CMS platforms with frequent updates and a strong support network. 

The bad:

1. Complexity: The downside to the flexibility of D8 is that components, while easily initially built, require ongoing development tinkering to fine tune to the specific needs of the organization. This costs both time and money, and in many cases the end product is no better than an off the shelf component from a simpler CMS or 3rd party solution.

2. CMS interface: It's possible but difficult to limit the CMS components that are visible to different levels of editors. The default D8 view is the "kitchen sink", so many new editors can be intimidated by the CMS, hampering adoption.