Having just wrapped up a six-month engagement where the client's primary "transformation" was a forced rollout of Fellow, I feel compelled to weigh in. The sales pitch is always the same: "It will bring discipline, accountability, and alignment to your meetings." What I saw was a different reality.
The premise is that a dedicated tool for agendas, notes, and action items—bolted onto your existing calendar and video conferencing stack—will cure the disease of bad meetings. My cynical take? It often just changes the symptoms. You're not solving the root cause (a culture of unfocused, over-invited, decision-avoidant gatherings); you're adding a new layer of mandated documentation. The overhead isn't trivial.
Consider the new workflow it imposes:
* **Pre-Meeting:** Someone must now populate an agenda in Fellow, not just the calendar invite. This either becomes a rushed, pro-forma list of bullet points copied from the last meeting, or it doesn't happen at all, making the tool's first feature useless.
* **During Meeting:** Someone is designated the "note-taker" in the tool, which distracts from actual participation. The pressure to capture every "action item" in the correct box, assigned to a person with a date, turns a conversation into an administrative exercise.
* **Post-Meeting:** The auto-generated "meeting recap" emails become just another piece of corporate noise, ignored alongside the 47 other automated notifications. Action items live in yet another system, separate from the project management tool or CRM where work actually gets tracked.
The brutal truth is that a team with good meeting discipline can achieve 90% of Fellow's value with a well-structured Google Doc template and a modicum of follow-through. A team with poor discipline will simply have poor discipline *inside* Fellow. The tool becomes a scapegoat—"Why wasn't that in Fellow?"—instead of addressing the real questions like "Why are we having this meeting?" or "Why does no one read the pre-read?"
Where I *have* seen it add marginal value is in very specific, recurring cross-functional meetings (like quarterly business reviews with external partners) where a persistent, shared record is genuinely needed. But for the daily stand-up or the weekly team sync? It's over-engineering.
So, before you sign that contract, do the hard cost-benefit:
* What is the *specific* meeting dysfunction you are trying to solve?
* What percentage of your meetings are truly "decision-making" versus "status update" or "information broadcast"?
* Are you prepared to enforce the new process, including calling out leaders who don't prepare agendas?
* Have you quantified the admin time added versus the theoretical time saved from "more efficient meetings"?
Otherwise, you're just buying a very expensive, beautifully designed notepad that will frustrate your team and provide another dashboard for management to gaze at, wondering why velocity hasn't improved.
-- Carl
Test the migration.