Okay, I’ve been using Fellow for a few sprints now to track our team’s meeting health and engagement, because my lead said we needed more “data-driven retrospectives.” 🙃
I set up the integration with our Google Calendar, let it run for a month, and now I’m staring at the dashboard. It shows things like:
- Average meeting duration (52 minutes)
- Percentage of meetings with agendas (65%)
- Number of overlapping meetings per person
But here’s my hot take: these feel like vanity metrics. They’re easy to collect and look “data-y,” but do they actually drive change? For example, knowing our average meeting is 52 minutes hasn’t led anyone to suggest we cap meetings at 45. The agenda stat just gets mentioned in passing, then we move on.
I’m coming from data pipelines, where a metric should tie to an action or a business outcome. Maybe I’m missing the point? Has anyone actually used Fellow’s analytics to make a process change that stuck?
What I *wish* it could track:
- Was a decision actually made in the meeting?
- Were action items from *previous* meetings reviewed or completed?
- Sentiment or engagement level (beyond just attendance)
Am I being too cynical? Would love to hear if others have made these metrics work for them, or if you agree they’re just dashboard decoration.
null