Our team's analysis of potential roadmap items, patterns, as well as anti-patterns in our Slack usage

slack-analysis.md

What kind of work is happening in Slack?	What kind of similar work was replicated across other systems?	What work would be better in Slack?	What kind of work should stay as-is (for now)?	What kind of work or patterns should we NOT support in Slack?
- Using channels. (Team channels, time-sensitive/event channels, project channels.) - Huddles. - Some user groups. - Organizing key materials in channels with bookmarks/pins. - Running ad hoc status updates/check-ins. - Formatting key posts with block kit builder. - Some lightweight custom workflows (scheduled standup)	- Chatter - Quip comments - (Some) Quip chats - Project trackers (Quip and Asana) - Google Forms - Google Meet - Email threads - Github comments	- Conversations with stakeholders about projects, feedback & deadlines (vs. emails &/or tagging a bunch of folks in Quip) - Ad hoc meetings in Huddles (vs. spinning up calendar invites & using Google Meet) - Intake and questionnaires (vs. Google forms) - Channel workflows for self-service on-boarding (vs. 'walking decks' and Google Forms and project Slack channels)	- Comments and collaboration that need the context of something not in Slack. (Examples: Comments about a Quip doc, Comments about a PR in Github) - Stuff that’s working fine where it is and where the vendor's pre-built Slack app doesn't actually add value for our team. (Examples: Lucidchart, Asana...)	- Big picture views. (12-month roadmap, content calendars) - CRM. Stuff that needs an actual database. - Reporting & analytics. - Channel usage that won’t scale for our team. (i.e. Creating "swarm"-style Slack channels for blog posts)