Meetly
MeetingsAugust 8, 202611 min read

Does This Meeting Need to Exist? (Better Notes Won't Save You)

The productivity advice everyone gives is 'take better meeting notes' or 'run tighter meetings.' The contrarian truth: most meetings shouldn't happen at all, and an AI notetaker just makes a bad meeting easier to survive. Here's the framework for cutting meetings, and what to do with the ones that actually earn their place on the calendar.

Most meetings don't need better notes; they need a reason to exist. Before sending an invite, ask whether it is just information transfer, needs real-time back-and-forth, needs every person live, would resolve faster async, or recurs only because nobody cancelled it. Record only the meetings that survive, so fewer people have to attend.

Minimalistische illustratie van een lege vergadertafel met een zonnestraal erover

Every productivity newsletter has the same advice for meetings: write an agenda, start on time, assign a note-taker, send a recap. It's all reasonable. It's also treating the wrong problem. You don't have a note-taking problem. You have a meeting problem, and the meeting in question probably didn't need to happen.

In a survey of senior managers reported in Harvard Business Review, 71% said meetings are unproductive and inefficient. That's not a facilitation gap. That's a category of event that keeps getting scheduled for reasons that have nothing to do with whether it needs to exist: habit, hierarchy, and the fact that a calendar invite feels more like action than an email does.

The default advice treats the symptom

"Run better meetings" assumes the meeting is the right unit of work and the only thing missing is discipline. "Take better notes" assumes the meeting is the right unit of work and the only thing missing is memory. Both let the actual decision (should seven people stop what they're doing and sit in a room for thirty minutes?) go completely unexamined.

Asana's 2024 State of Work Innovation research found that individual contributors spend about 3.7 hours a week in unproductive meetings and managers about 5.8 hours a week, both well up since 2019. We are optimizing the wrong variable at scale.

The evidence of how badly the format has drifted is right there in the meetings that do get scheduled: recurring meetings that pull in seven or more people, meetings that start late, and agendas that, when they exist at all, get abandoned within the first few minutes. None of that is a note-taking failure. It's a demand-side failure. We are generating meetings faster than we are generating reasons for them.

Why "just get better notes" is the easy, wrong fix

Here's where it gets uncomfortable for a company that sells a meeting notetaker: an AI notetaker does not fix a meeting that shouldn't exist. It makes that meeting easier to sit through. AI meeting assistants for transcription and summaries are spreading fast, and that's a huge shift in how meetings get documented. It will do almost nothing to reduce how many meetings get scheduled.

If anything, it can make the problem worse: when attending a meeting costs you nothing (the bot takes notes, you skim the summary later), the friction that used to make people ask "do I actually need to be here?" disappears. Good notes are a painkiller. They are not a diagnosis, and they're definitely not a cure. If you want fewer bad meetings, better notes are the wrong lever entirely.

Meeting minimalism: the counter-trend that's actually addressing the cause

The more interesting shift happening right now isn't AI notetaking. It's meeting minimalism, an emerging discipline of treating the meeting as a last resort rather than a default. Teams practicing it ask one question before any invite goes out: does this need to be a meeting, or does it need to be a message?

Status updates, FYIs, and anything that's really just information transfer move to async channels: a written doc, a recorded loom, a thread with a deadline for replies.

What's left, genuinely, for live meetings is a short list: real-time debate where people need to react to each other, decisions with real disagreement that won't resolve over Slack, sensitive conversations that require tone and presence, and creative work like brainstorming that benefits from people building on each other's ideas in the moment. If a topic doesn't need synchronous, felt presence to make progress, meeting minimalism says: don't book the room. For a broader look at how these habits form (and why they're so hard to break once a team defaults to meetings), see our piece on back-to-back meeting burnout.

This is a genuinely contrarian stance inside most corporate cultures, because meetings function as a status signal as much as a work tool. Scheduling a meeting feels like doing something. Canceling one can feel like abdicating responsibility, even when it's the more responsible choice. Meeting minimalism asks managers to tolerate that discomfort: to treat an empty calendar slot as a sign of good judgment, not neglect.

A five-question filter before you send the invite

Before any invite goes out, run the meeting through five honest questions. Each one tests whether the topic needs people together in real time, or whether a written update, a thread or a decision with a deadline would get the same result. If a meeting fails most of them, it should probably be a message instead of a calendar slot.

  • Is this actually information transfer? If the goal is "let people know X," write it down. A meeting is the most expensive way to broadcast a fact.
  • Does it require real-time back-and-forth? If everyone would just state their position once and you'd tally the results, that's a form or a thread, not a meeting.
  • Do all these specific people need to be there live? If the honest answer is "some of them just want to be informed," cut the list and send a recap instead of inflating the room.
  • Would this resolve faster async, with a deadline? Most disagreements that feel urgent are actually fine to resolve over 24 hours in writing, and writing forces clearer arguments than a room does.
  • Is this recurring because it's still needed, or because no one cancelled it? Recurring meetings are the worst offenders for this: they outlive the reason they were created and nobody wants to be the one who kills a standing invite.

Run any proposed meeting through those five questions honestly and a large share of them fail before they're scheduled. That's the point. Meeting minimalism isn't anti-collaboration. It's anti-default. It just refuses to let "we've always had a Tuesday sync" count as a reason.

InviteQuestion it failsWhat happens instead
Monday status sync (9 people)Is this actually information transfer?A written update in the team doc by 10:00
Launch date decisionNone: real disagreement, needs live debateKept, 30 minutes, 3 people, recorded with consent
Weekly design reviewIs this recurring only because no one cancelled it?Cancelled; reviews move to comments with a 24-hour deadline
Client kickoffNone: tone and presence matterKept; the account lead records it so the rest of the team reads the notes
Fictional example: one week of invites run through the five questions

But some meetings really do need to happen. Then what?

This is where the cutting framework runs into its honest limit, and where most "just kill your meetings" advice gets glib. Real-time debate, sensitive one-on-ones, legal and healthcare conversations, and genuine brainstorming don't compress well into a doc. People need to hear tone, interrupt, read a pause. Those meetings earn their place.

The question for them isn't whether they should exist. It's whether they need everyone in the room live, and whether the note-taking burden should fall on a participant who's also trying to actually be present in the conversation.

That's a genuinely different problem than the AI-notetaker pitch usually admits, and it's the one place where recording, done right, is the actual fix rather than a band-aid. If a meeting is necessary, the goal shifts from "eliminate it" to "stop paying for it twice": once with everyone's live attention, and again with someone's attention split off to type notes instead of participating. A private, on-device recording means fewer people have to be pulled into the room in the first place: the two people who need to hash something out can do it, record it (with everyone's consent), and the others read the notes later instead of sitting through it live. And because the audio stays private on your own devices, it is worth considering for the sensitive conversations that meeting-minimalism advice usually keeps away from tooling. Those are exactly the meetings that most need to happen, and exactly the ones people are most nervous about recording into someone else's cloud. Your organization's own rules still decide what may be recorded.

For the meetings that actually need to happen Meetly records and transcribes meetings directly on your iPhone: no bot joins the call, and the audio is never sent to Meetly or an AI provider. For the conversations that genuinely require live presence (client negotiations, 1:1s), it means the person in the room can actually participate instead of splitting attention between talking and typing, and everyone who didn't need to be there gets the notes instead of an invite. Free download; core recording and transcription work without an account.

Download Meetly

The habit that actually moves the number

None of this requires a company-wide mandate to work. It requires one habit: before you hit "send" on a calendar invite, ask "does this need to be a meeting?" out loud, even just to yourself, and mean it enough to sometimes answer no.

Cancel one recurring meeting this month that nobody would notice missing. Convert one status update into a doc. Decline one invite where you're purely an FYI attendee and ask for the notes instead (see why so many meeting summaries never even get read for why that request often lands better than people expect). The meeting problem isn't going to be solved by any one person's calendar discipline, but your own hours a week can be.

Better notes are not nothing. For the meetings that survive this filter, a clean transcript and summary genuinely help, especially when they let a one-on-one stay a conversation instead of a dictation exercise. But notes are the last mile, not the fix. The fix is fewer meetings, chosen on purpose, for reasons you could defend out loud to the people you didn't invite.

Cut the meeting, not the memory When a meeting genuinely earns its place on the calendar, Meetly makes sure it only has to happen once: on-device recording and transcription in 90+ languages, with the audio kept private on your own devices and no account needed. Summaries on iPhone are an optional cloud step that sends only transcript text, with zero data retention requested. Fewer meetings, better records of the ones that count.

Download Meetly

Frequently asked questions

How many meetings is too many?

There's no universal number, but a useful signal is satisfaction, not volume: if you'd be noticeably happier with fewer meetings, you already have too many. Survey data backs this up broadly: in one survey reported in Harvard Business Review, 71% of senior managers called meetings unproductive and inefficient, and Asana's 2024 research found individual contributors spending about 3.7 hours a week in unproductive meetings. A practical test is to audit one week's calendar and flag any meeting where you could have gotten the same outcome from a written update or a decision made async. Then run the flagged ones through the five-question filter before they recur.

How do I say no to a meeting invite politely?

Ask what decision or output the meeting needs from you specifically. If the honest answer is "just keeping you informed," reply asking to be looped in via notes or a recap instead of attending live, and offer to weigh in async if something needs your input. Most organizers accept this without friction once they realize your attendance wasn't actually load-bearing to the outcome. Keep the reply short and specific: name the decision you would want to weigh in on, and ask for the notes or a two-line recap afterward. If the meeting is recurring, suggest checking in again in a month to see whether your seat is still needed. Declining this way signals that you take the meeting's purpose seriously, not that you are avoiding the team.

What is meeting minimalism?

Meeting minimalism is the practice of treating live meetings as a last resort rather than a default: asking "does this need to be a meeting?" before scheduling one, and defaulting to async written updates, recorded messages, or threaded discussion for anything that doesn't require real-time, synchronous presence. It reserves meetings for the narrow set of things that genuinely benefit from live back-and-forth: contested decisions, sensitive conversations, and creative brainstorming. In practice, a team adopting it moves status updates and FYIs into written docs or threads with a reply deadline, cancels recurring meetings that no longer have a clear purpose, and keeps invite lists to the people who need to react live. It is anti-default, not anti-collaboration: the meetings that remain are chosen on purpose.

Does an AI notetaker actually reduce the number of meetings?

Generally, no. An AI notetaker makes a meeting easier to attend and document, but it doesn't address why the meeting was scheduled in the first place. Some evidence suggests it can even increase meeting volume, since attending feels lower-cost when you know a bot will produce a searchable summary afterward. Cutting meeting count requires a decision filter applied before scheduling, not better documentation after the fact. Where a notetaker does help is with the meetings that survive that filter: it lets the people in the room participate instead of typing, and it lets the people who did not need to attend read the notes instead of sitting through the call. Used that way, recording supports a smaller guest list rather than a longer one.

Which meetings should never be cut?

Meetings that require real-time debate, genuine disagreement that hasn't resolved in writing, sensitive or emotionally weighted conversations (performance issues, health disclosures, legal or clinical discussions), and open-ended brainstorming where people build on each other's ideas live. These benefit from tone, timing, and presence in ways a document can't replicate. The goal for these isn't elimination; it's making sure only the people who truly need to be there live are, and that whoever's there can focus on the conversation instead of transcribing it.