Why I’m Always the One Taking Notes in Meetings

Before Taking Notes Was “My Thing”

In the early days of calls and meetings, I didn’t think much about note-taking. Someone had to jot things down, sure, but I didn’t see it as a role or an identity. It was just something that needed doing in the moment.

If a chat thread started to wander, I’d gently summarize what had been decided. If someone asked a question and people talked around it, I’d try to capture the outcome so there was something to refer back to. I did it because it felt useful, not because I was asked to.

At first it felt incidental—like holding the pen at the right moment. But over time, I began to notice how often I ended up with that pen.

It reminded me of patterns I’ve read about before, like in Why My Work Is Assumed, Not Recognized, where labor becomes invisible because it’s expected rather than acknowledged.

What was once a simple action gradually turned into something that felt like an unspoken responsibility—not because anyone told me it was mine, but because it kept happening that way.

How It Became the Default

The shift was subtle. In one meeting someone might ask, “Did anyone take notes?” and I’d instinctively start typing. In another, someone would ask me afterward what had been decided, even though a recording existed. One day someone else began forwarding meeting summaries to others with my name attached, almost automatically.

No one ever said, “You’re the note-taker.” There was no explicit expectation written into any documentation. It just became the quiet pattern—because I always did it first, and no one else seemed to step in.

There’s a familiar feeling in that pattern: labor that becomes assumed through repetition rather than assigned through acknowledgment. It doesn’t feel like responsibility so much as inevitability.

And because it’s unofficial, it never shows up in any formal understanding of contribution. It doesn’t get counted. It doesn’t get evaluated. It doesn’t become part of anyone’s narrative about “what was done.”

The Invisible Labor Beneath the Notes

Taking notes isn’t just transcription. It’s interpretation. It’s deciding what matters, what will matter later, what needs to be captured so someone doesn’t have to replay a call later and reconstruct the threads in their memory.

Sometimes I find myself listening two layers deep: to what’s being said, and to what’s going to matter later when everyone tries to remember it. Which parts will people refer back to? Which decisions will haunt someone if they weren’t clearly captured? What nuance will matter when the chat thread scrolls into oblivion?

That’s labor that doesn’t show up in a slide deck or a deliverable. It just shows up later when someone needs to retrace steps—or when someone realizes they forgot something important.

And yet, because it’s not a formal role, no one ever says, “We value this.” They just forward the notes and assume someone will continue doing them.

It’s a pattern similar to what I’ve seen described elsewhere in my reading: work that bridges gaps and prevents future confusion, but that never produces an artifact anyone can easily celebrate or acknowledge beyond a functional summary.

Before, During, and After the Pattern Emerged

Before this pattern emerged, I didn’t think about “taking notes” as a contribution at all. It was just something that happened when a conversation needed to be captured. I wasn’t tracking it or thinking of it as part of my role.

During the shift, I began to notice how quickly the pattern solidified. In one meeting I’d take notes, in the next someone would ask me to share them, in the next someone would thank me in chat without anyone else even offering to do it themselves.

There was no conversation about this becoming a responsibility. It just became one through repetition: I did it, and others began to rely on the assumption that I would do it again.

After the pattern was established, I started noticing how much of my attention went into capturing not just what was said, but what wasn’t said. Which questions were avoided. Which decisions were tentative. Which topics were deferred. That deeper layer became part of how I took notes because it felt like the only way to make them actually useful later.

That labor doesn’t show up on a to-do list. It doesn’t show up in performance evaluations. It doesn’t get mentioned in retrospectives. It just lives in the quiet text of a document no one reopens until someone needs it.

The Cost of Invisible Note-Taking

There’s a subtle cost to doing this work consistently. On the outside, meetings look calm and organized. On the inside, there’s a sense of always listening for what will matter later, always translating live conversation into something that can be referred back to, and always doing it without being asked.

When I think about what I actually did during the day, it’s easy to list the meetings attended. But harder to account for how much mental energy went into capturing the essence of those conversations so others don’t have to replay them in their heads later.

And because no one ever frames this as a contribution, it feels like something I do out of habit rather than something that matters. Which is part of why pieces I’ve read about invisible labor resonate so deeply—the work feels essential in experience but disappears in recognition because no one anchored it into the formal story of what was accomplished.

That pattern of invisibility doesn’t feel like critique so much as observation: when something becomes invisible because it functions well, it also becomes easy to overlook the labor that made it function that way.