Our team of 25 recently completed a migration from Basecamp to ClickUp. The decision was driven by the need for more granular task management and integrated time tracking, which ClickUp's feature matrix seemed to solve. The projected TCO over three years was favorable, even accounting for the per-user cost.
However, the implementation revealed several critical friction points that weren't apparent during the RFP stage. The productivity gains we anticipated are being eroded by systemic inefficiencies.
What actually broke:
* **Performance degradation at scale:** With all 25 users active, loading workspaces and switching views (especially List and Board) introduces a 3-5 second lag. This was negligible in our pilot with 5 users.
* **Notification overload and lack of granularity:** The default notification schema is aggressive. We've struggled to configure it so that users are alerted to *their* task updates without also receiving a firehose of team-wide activity. The "Inbox" becomes a point of anxiety, not clarity.
* **Custom field instability in dependencies:** We rely heavily on custom fields for priority and client-stage tracking. When tasks are linked via dependencies, these custom fields do not always propagate or display correctly in reports, creating gaps in our analytics.
* **The "one tool for everything" tax:** ClickUp can theoretically replace multiple tools, but the forced workflow into its specific hierarchy (Space > Folder > List > Task) is rigid. Simple, Basecamp-style message boards or quick check-ins now require a formalized task structure, which increases overhead for non-project communication.
The core issue isn't feature absence, but integration and performance at our team size. We are now evaluating whether to:
1. Invest in a dedicated ClickUp admin to manage configurations full-time.
2. Decouple functions, using ClickUp for strict project tracking only and reintroducing a separate tool for communications.
3. Reassess the platform choice entirely for teams above 20 users.
Has anyone else hit a similar scale ceiling with ClickUp, and how did you quantify the decision to stay or leave?
- Mark
independent eye
That notification overload is a real productivity killer. The anxiety you described around the Inbox is something I've seen teams struggle with repeatedly.
While ClickUp's notification system is powerful, its default state assumes everyone wants full transparency. For a team of 25, that's unsustainable. The key is to move away from a *broadcast* model to a *subscription* model, but it requires manual configuration for each user or role. We had success by creating a few standardized notification "profiles" (e.g., "Project Lead," "Contributor," "Stakeholder") and enforcing them during onboarding. It's admin work, but it prevents inbox fatigue.
Have you explored using Spaces and Folders as notification boundaries? Setting most notifications to "Only for items inside the current Space" can drastically cut down the noise, though it might limit cross-project visibility you actually want. It's a tough balance.
Prod is the only environment that matters.