I've been using Fellow to manage my team's 1-on-1s for a few months now. The tool itself is great for organizing talking points and keeping notes. But I'm hitting a consistent problem: my direct reports rarely add their own items to the agenda before we meet. The meeting ends up being mostly my topics, which defeats the purpose.
I’ve tried sending reminders a day before, and I always populate a couple of starter items. But it still feels like I’m pulling teeth to get them to engage with the agenda proactively. They’ll add things *during* the meeting, but the pre-work just doesn’t happen.
Has anyone else dealt with this? What actually worked to make the agenda a collaborative document? I’m wondering if it’s a process issue, a cultural one, or if there are specific Fellow features or integrations (like with Slack) that can nudge behavior more effectively. I’d like to solve this without it feeling like micromanagement.
Oh I've totally been there! It can be so frustrating when you've got a great tool but the habit just isn't sticking. A few things that worked for us:
First, I shifted the focus from "adding to the agenda" to "saving us both time." I started framing it as "Hey, if you pop your top 1-2 items in beforehand, I can come prepared with any relevant info or docs, and we'll have more time to actually solve things." That made it feel more like a mutual benefit.
Second, and this was key, I stopped adding starter items for a few weeks. The first few 1-on-1s were awkwardly quiet for the first five minutes, but it created the necessary vacuum. They had to bring *something* to talk about. After that, the habit started to form.
Have you tried explicitly asking in your reminder? Something like "Our 1:1 is tomorrow at 10. What's the one thing you most want to make sure we cover?" Sometimes a direct, simple question works better than an open-ended "add to the doc."
null
I've had to solve this exact problem, and while user1084's suggestions about framing and creating a vacuum are solid, I think you've identified a key element in your last sentence: integrations. The process often fails because it lives in a silo.
You mentioned Fellow integrations. If your team lives in Slack, Fellow's Slack integration can be configured to post the agenda link directly into your 1:1 DM channel a set time before the meeting. This is more effective than a calendar reminder because it lands in their active flow of communication. The notification can be tailored to say "Got your topic? Add it here so I can pull the reports," which links the action to a tangible outcome.
Beyond that, I've found success by making the agenda part of a broader, automated workflow. For instance, if you use a task manager like Jira or Asana, you can create a rule that automatically adds "Prepare 1:1 topics" as a task for them 36 hours before the meeting. It sounds like over-engineering, but it treats the symptom - the pre-work not happening - by attaching it to an existing system they already engage with. The goal is to reduce the cognitive load and decision point of "opening Fellow." Once the habit is built, you can scale back the automation.
Yes, the integration point is huge. You're spot on about cognitive load - the extra step of opening a separate tool is a real habit killer. I've seen the Slack integration work well, but with one caveat: the notification cadence matters.
If it fires too early, like 48 hours out, it gets lost in the noise. Too late, and there's no time to prepare. We landed on a Slack reminder 24 hours before, plus a quick calendar notification 30 minutes prior as a nudge. The calendar one just says "Check the shared agenda!" so the link is top-of-mind right as the meeting starts.
Your automated task idea is clever, but be careful it doesn't become another box to check. I tried that with Asana and found people would just mark the task complete without actually engaging. The magic happens when the integration *reduces* work, like auto-pulling their recent PRs or support tickets into the doc as discussion starters. That makes the agenda feel alive.
I think you're right to suspect this is partly a cultural or habit issue, not just a tool problem. The other replies about Slack integrations are great - the fewer clicks, the better.
But I'd also ask: are the items they add *during* the meeting typically urgent, tactical fire-drills, or more thoughtful, longer-term topics? If it's the former, they might see the agenda as a place for "formal" items, not the day's real problems. I had to explicitly say "Even if it's a 2-minute blocker you hit this morning, throw it on the shared doc so I don't forget." Lowering the bar for what "counts" helped a ton.
Also, do you review the *previous* meeting's notes at the start? We found that when we quickly scrolled through last week's action items, it naturally triggered "oh right, I wanted to follow up on X" and they'd add it right then. It became a rolling document.
Data doesn't lie, but dashboards sometimes do.
Absolutely, the distinction between "formal" agenda items and day-to-day issues is such a good catch. That mental model can completely sink the process. I had a report who only added "career growth" topics beforehand, saving all their pressing work questions for the meeting itself. Once we explicitly reframed the agenda as the landing spot for *anything* that's blocking them or on their mind, it clicked.
Your point about reviewing previous notes is gold, too. It turns the document into a living thread, not a series of disconnected forms to fill. That continuity builds the habit because it provides a clear prompt. I'd just add one gentle warning from experience: if you're dealing with performance issues or particularly sensitive topics, sometimes a fresh start each meeting feels safer. You have to read the room on that.
Let's keep it real.
You've correctly identified the three potential failure points: process, culture, and tooling integration. The other replies have covered integrations and habit formation well, but I'd analyze this from a data workflow perspective. The agenda is an input, the meeting is a transformation, and the notes are an output. If the input isn't arriving on time, you need to examine the upstream dependencies.
The issue of them adding items *during* the meeting is a critical signal. It shows the motivation is there, but the process has a high latency. This is a classic ETL problem where data arrives late because the extraction trigger is misaligned. Your reminders are a scheduled batch job, but their mental model treats the agenda as a real-time stream they only access at meeting time.
Instead of just Slack nudges, consider anchoring the agenda population to an existing, non-negotiable event in their calendar. For instance, mandate that the final 10 minutes of their Friday "wrap-up" block is for adding items to the following week's 1-on-1 doc. This couples the action to a ritual they already (hopefully) perform, reducing the cognitive load of a standalone task. It treats agenda building as a checkpoint within their operational workflow, not a separate administrative duty. The tool is less important than embedding the step into a habitual sequence.
Data doesn't lie, but folks sometimes do.
Your focus on integrations as a remedy for siloed process is analytically sound. I'd extend that by classifying integrations into two types: notification and enrichment.
The notification type, like your Slack example, reduces friction to *awareness*. The enrichment type, which you hint at with automated tasks, aims to reduce friction to *content creation*. That's where I've seen the most leverage.
For example, we linked Fellow to our project management tool via Zapier. It didn't just create a "prepare topics" task; it prefetched the user's assigned and recently updated tickets from the last week, formatting them as bullet points in the agenda draft. This transformed a blank page problem into an editing problem. The cognitive load shifted from "what should I talk about?" to "which of these items is relevant?". Engagement increased because the starting state was no longer zero.
The caveat is data privacy - you must ensure the integration only pulls data the report already has access to. But done correctly, this makes the agenda a reflection of existing workstreams, not a separate administrative artifact.
That's a really smart distinction between notification and enrichment integrations. The idea of transforming a "blank page problem into an editing problem" clicks for me. It lowers the activation energy significantly.
I've found this works well, but it can also accidentally reinforce a focus on *only* tactical, project-based topics. If your enrichment integration pulls solely from Jira or Asana, the agenda can become a status report by default. You might need to balance it with a prompt or a dedicated section for non-project items, like career questions or feedback, to keep the conversation holistic.
That privacy point is crucial, too. It's easy to overlook in the setup phase, but a misconfigured integration that surfaces the wrong info can break trust in a heartbeat. Great callout.
That point about the agenda becoming a status report when you auto-pull from Jira is exactly right. I tested an enrichment integration that pulled recent PR links. After two weeks, all we talked about was code review bottlenecks. Had to manually add a fixed first item: "What's one thing outside your immediate tickets?" to break the pattern.
Benchmarks don't lie.
>rarely add their own items to the agenda before we meet
>they'll add things *during* the meeting
That's the key signal right there. The intent is present, but the habit isn't. I've fought this same battle.
While the Slack integration nudges help, I had to explicitly shift the *value proposition* for my team. I started saying, "If you put it on the agenda, I'll research it before we talk." For a technical blocker, that meant I could pull logs or check configs ahead of time, making our 30 minutes way more effective. When they saw it turned the meeting into a solutions session instead of a problem-description session, engagement jumped.
One tactical thing from Fellow: we use the "Private Notes" feature heavily. I told my reports they can drop a raw, messy thought there if they don't want to formalize it into a public agenda item yet. Sometimes the barrier is just wanting to think out loud privately first.
Keep deploying!
Integrations are a great start, but I've seen the automated task approach backfire more often than not. Your Jira or Asana rule to create a "Prepare topics" task is a solid technical solution, but it risks becoming noise if the team's culture sees it as just another checkbox. I've built that exact workflow for a client, and the compliance rate looked great on paper - tasks were being completed - but the quality of engagement was hollow. People would mark it done with a single word like "ready" to clear their board.
The real magic, as you hinted at with linking the action to an outcome, is in making the *output* of that task visible and valuable. Instead of just creating the task, we modified the workflow so completing it required pasting the actual agenda topics into the task description. That way, as a manager, I could scan my own board the morning of the 1:1s and already be thinking about the themes. It flipped the script from tracking *completion* to enabling *my own preparation*.
One caveat on the Slack notification timing, though. You're right that landing in their active flow is key, but for some teams, a DM can feel like a pressure-filled ping. We got better results by posting to a private group channel dedicated to 1:1 prep, which created a slight social nudge without the direct-manager intensity.
Implementation is 80% process, 20% tool.
Your observation about the quality of engagement being hollow despite high task completion metrics aligns with research on Goodhart's law. When a measure becomes a target, it ceases to be a good measure. The modified workflow you describe, where pasting the actual topics is required, directly addresses this by shifting the observable output.
However, this still relies on a compliance model. A complementary approach is to structure the agenda itself to demand substantive input. For instance, using a template with fields like "Blockers: [require a link to a ticket or document]" or "Discussion Item: [what is your recommended action?]" forces a minimal level of elaboration that a single word can't satisfy. This creates a built-in quality gate.
The caveat on Slack DMs is valid. We found posting to a dedicated, low-traffic team channel for agenda reminders reduced the perceived pressure, as it framed the reminder as a team norm rather than a personal admonishment.
Nullius in verba
The template approach is a solid forcing function, I'll give you that. We tried something similar with a "Root Cause Analysis" field for any blocker topic, which at least filtered out the vague complaints. But it created its own problem: engineers started spending fifteen minutes writing mini-postmortems just to satisfy the field, which felt like bureaucracy.
Your point about shifting the reminder to a team channel is subtle but correct. Direct DMs frame it as a personal failing, while a channel broadcast normalizes the prompt. We use a dedicated #one-on-ones channel that's read-only for agenda nudges and template links. Takes the sting out.
The real trick is making the prep work visible to peers, not just the manager. When the agenda doc is shared in that channel an hour before meetings, there's a gentle social pressure that a private task can't replicate. No one wants to be the person with an empty doc when everyone else has a list.
You're correctly identifying the friction between intent and action. The fact they add items during the meeting is crucial, it shows the barrier is logistical, not motivational.
Your current process has a scheduling problem. A reminder a day out is a batch job, but their mental model is real-time. They think about the meeting when it's imminent. You need to move the trigger for agenda contribution closer to that moment, but with enough lead time for you to prepare. I've had success by making the agenda the first item in a pre-meeting workflow that starts one hour before. We use Fellow's Slack integration to post the agenda link to a team channel with a simple rule: if it's not populated by then, the meeting is a 15-minute coffee chat instead of a working session. This creates a natural consequence and frames their input as a prerequisite for a valuable outcome. It aligns their action with their immediate context.
Plan the exit before entry.