Challenges of project management in Slack channels
TL;DR
On a quest to understand the typical project management (PM) challenges among Slack users, we turned to analysis of posts on Reddit. Here is what we found:
- We clustered all posts on the Slack-dedicated subreddit r/Slack into 12 open-ended themes, 4 of which contained project management topics. Zooming in on those four and filtering out irrelevant posts, we estimate that 10.5% of all posts on r/Slack are related to issues of project management.
- Among those, posts explicitly calling out the need for Task Tracking and the feasibility of using AI for automating text summarisation and task extraction dominated the discussion. These were followed by conversations on Information Overload, the need for Decision Documentation (scattered across different Slack channels) and for Cross-Tool Data Sync (e.g. between Slack and a task tracker).
- The signal is clear: Slack users want their conversations to turn into tracked work without changing how they communicate. ONIQ is building exactly that — listening to the Slack channels you pick and turning actionable requests into tracked, prioritised tasks. Join our early access program to try it.
Methodology
To answer this question, we collected 1,226 posts from the r/Slack subreddit (top/all, top/year, hot) and clustered them via a two-stage LLM analysis.
In the first stage, we asked the LLM to cluster the content of the posts, resulting in 12 top-level themes (Figure 1). These contained a variety of topics from technical and UI issues to admin questions and feature requests.
Out of those, we manually labelled 4 as potentially PM-related (Workflow & Automation, Team Communication Practices, Use-Case Advice, and a binary-filtered subset of App Promotions), forming a candidate subset of 298 posts.
In the second pass, we used the same approach on the candidate subset (this time, augmenting the 298 posts with 3,074 comments) and derived 16 sub-themes. After discarding many of these as irrelevant to project management, we ended up with 5, which accounted for 43.3% of the candidate subset, or 10.5% of the entire dataset.
Findings
Many conversations in this final PM-relevant subset explicitly called out the need for capturing and formalising tasks scattered across different Slack channels. This was followed by another large cluster of posts around AI automation. Interestingly, the enthusiasm around such tools coincided with trust and safety concerns about over-relying on AI.
Information overload and loss of knowledge were two other prominent topics in the data. The pattern of losing important decisions or messages buried in channels was frequently called out.
Last but not least, there were concerns about failing to keep state in sync between different systems — Slack and task tracker — and the patches and integrations teams build to work around this.
| Topic | Description | Share |
|---|---|---|
| Task tracking & action items | Capturing, formalising and tracking work requests and action items that originate in Slack conversations before they get lost, including routing into downstream PM tools. | 37.8% |
| AI & automation feasibility | Whether AI tools can reliably solve Slack-side PM problems — summarisation, action-item extraction, agent workflows — and the trust and safety concerns that come with them. | 21.7% |
| Information overload & notification fatigue | Managing cognitive burden, notification volume and context-switching in Slack so genuinely important messages surface without constant anxiety. | 18.7% |
| Decision documentation & knowledge loss | Capturing and preserving decisions and institutional knowledge discussed in Slack so they don't disappear into chat logs. | 12.4% |
| Cross-tool data sync | Keeping project and task state consistent between Slack and external systems (Notion, Airtable, Jira, HubSpot, Sheets, Salesforce). | 9.2% |
Conclusion
At ONIQ, we are on a mission to sort out many of these challenges. ONIQ listens to the Slack channels you pick, identifies actionable requests, and turns them into tracked, prioritised tasks — no behaviour change needed. Our Slack integration is currently in private beta and we are looking for design partners to work with us on testing. If you are interested, get in touch.