Alright, let's get this out there. The hype around Fellow as the "single source of truth" for meetings had me rolling my eyes, but my CTO bought in. So I pushed it on my 15-person engineering and security team for a quarter. The promise was less meeting chaos, better accountability, and streamlined workflows. The reality is, unsurprisingly, more nuanced.
On the positive side, the forced structure did kill the "what are we doing here?" meeting start. Having a shared, editable agenda that people can contribute to beforehand actually works. The action item assignment, with its direct Slack integration, means fewer things get lost in the chat ether. For audit purposes, having a searchable record of meeting notes, decisions, and assigned owners is genuinely valuable. It checks a box for us, especially when demonstrating due process for certain compliance frameworks.
Now, the friction. The "one tool to rule them all" approach runs into our actual workflow. We use Jira for tickets, Confluence for deep docs, and Slack for comms. Fellow becomes another place to *look* at things, not necessarily *do* them. My security team hates that sensitive data from risk review meetings now lives in another SaaS app, despite their SSO and encryption assurances. It's another vector, another audit log to monitor. The mobile experience is clunky, which killed buy-in from our always-on-the-go infrastructure lead.
The biggest miss? It assumes everyone wants to be a diligent meeting citizen. The engineers who already hate meetings just see it as more bureaucracy. Forcing them to populate action items they could have just typed in Jira feels like a step backward. The "pulse" and "feedback" features are utterly ignored—classic case of feature bloat.
So, is it a silver bullet? Absolutely not. It's a moderately useful overlay for teams already disciplined about meetings, but it adds overhead and creates data sprawl. We're keeping it for now, but only for specific project syncs and leadership meetings. For the daily grind, it's often bypassed. The search for a meeting *process* that doesn't feel like a tool-enforced straitjacket continues.
—Greg
Trust but verify
That friction point about Fellow being "another place to look" really hits home. We had a similar tug-of-war between Notion and our CRM, where the meeting notes lived separate from the actual customer data we acted on. The searchable record is great, but if it creates data silos or duplication, you're just shifting the chaos.
Your security team's concern is super valid, too. Once you start logging sensitive discussions, you're on the hook for securing that data just like any other system. That's an extra layer not everyone considers during rollout.