I've been using Fellow for a few months now, mostly for our team's weekly 1:1s and project kickoffs. It's been solid for those structured, agenda-driven meetings. Lately, though, I've been wondering about its role for those quick, ad-hoc syncs that pop up multiple times a week.
My team has a habit of spinning up a dedicated Slack thread for a quick 15-minute problem-solving chat. We'll drop a few bullet points in the first message as a loose agenda:
* Status update on X blocker
* Decision needed on Y approach
* Next steps for Z
It's fast, familiar, and the conversation/decisions are automatically logged in that thread. Now I'm looking at Fellow and thinking: should we be using a "meeting" there for this instead?
Here’s my practical comparison so far:
**Slack Thread Pros:**
* Almost zero friction to start.
* Everyone is already there; no new tab needed.
* The conversation *is* the record, with context readily available.
**Fellow Pros (for this use case):**
* Action items are more easily captured and assigned *outside* the flow of chat.
* The notes/doc has a more permanent, findable structure outside of Slack's search.
* Encourages a tiny bit more preparation with the agenda, which can keep us focused.
My gut says the tool should fit the meeting's nature. For a truly quick, tactical sync, a Slack thread might still win. But if there's any risk of the discussion sprawling, or if clear, assigned next steps are critical, maybe taking 60 seconds to set up a Fellow note is worth it.
I'm curious—has anyone else navigated this? Do you enforce a rule like "if it needs an agenda, it goes in Fellow," or do you find ways to make Fellow lightweight enough for these quick chats?
Migration is never smooth.