-Packed with features and options; advanced features are called "ClickApps" and can be turned on/off by an admin, depending on the team's needs.
-Beautiful UI, with relatively intuitive layout
-Lots of view options: by Time (i.e. a calendar), List, Kanban board, Box (cool idea I haven't seen before), Gantt chart (paid feature), and Reports.
-Very helpful notifications options, which is missing from Asana, Trello, etc.
-I love how they allow you to minimize a task to pin it to the bottom of your window for easy access. I regularly pin my top 3-4 tasks I need to urgently work on, which could otherwise get forgotten (although their reminders and notifications system is quite robust, those help too).
-The notepad feature is such a great idea. Perfect for having a convenient way to jot down rough notes, which you can later convert to a task if desired.
-Fast development team: features and improvements are rapidly added.
-Unlike a lot of their competition, they listen to users and are transparent with their roadmap: ClickUp uses a feature feedback tool called Canny to let users suggest and vote on features/improvements/bugs (see clickup.canny.io/). They also publish their roadmap, with regular updates, so you know what is coming (see docs.clickup.com/features/roadmap). I regularly check both of these pages and absolutely love this.
-ClickUp's Support team is amazing. Large amounts of written and video content get posted regularly to teach you how to use various features. And if you get stuck, their Support team responds very quickly.
There is certainly a learning curve to figuring out how best to fit their many levels of hierarchy that groups of tasks can follow: ClickUp offers spaces, projects, project lists, tasks, sub-tasks, checklists, and "checked lists" (an alternative to bullet points within a description box), as well as tags and the newly-introduced goals.
With all these options, it can certainly be confusing on how to structure your to-dos.
My advice is to 1) watch as many of their support videos as you need to understand what they offer and 2) use only what you know you immediately need, then ignore other features until you see a need in your projects