Vinder Singh
← All agents

Oct 21, 2026, 4:21 AM

LinkedIn Thought Leadership Post

Brief

I'm a project manager at a mid-sized company, and I write for people early in their careers and for other managers. Topic: how to run meetings people don't dread. I've sat in far too many meetings that could have been an email.

Editor

Done3.5s

The brief gives a clear author, audience and topic, so I'm sending the Researcher first for evidence on meetings people don't dread.

🧭 Editor → 🔎 Researcher

Topic: how to run meetings people don't dread (author: project manager at a mid-sized company, audience: early-career professionals and other managers; the author's view: too many meetings could have been an email). Find 5-7 verifiable facts, numbers and named examples (studies, company policies such as meeting-free days, async experiments, surveys) with source and date, favouring the last 2-3 years. Include the strongest counter-argument (e.g. when meetings beat email, or evidence that cutting meetings backfires). Flag anything unverifiable. Return concise bullets with sources and dates.

Researcherbehind the scenes

Done24.6s

Editor

Done2.5s

Evidence is in, including a useful counter-argument. Now the Angle Strategist will propose three personal points of view for you.

🧭 Editor → 🧠 Angle Strategist

Propose 3 distinct first-person angles for the author (project manager, mid-sized company; audience: early-career people and other managers; topic: running meetings people don't dread; they've sat in far too many meetings that could have been an email). Use the Researcher's evidence, including the counter-argument that meetings help junior people learn (Deming et al. NBER 2026). Don't invent personal experiences. Each angle: a name, a one-line stance, the evidence it leans on, and what the author should admit not knowing.

Angle Strategist

Done15.9s

Three angles on running meetings people don't dread

Each angle works from what the brief gives us: a project manager at a mid-sized company who has sat through many meetings that could have been emails. None needs an invented story. I've kept to the Researcher's verified material and noted where a figure is weaker.


Angle 1: Fix The Meeting

  • Name: Bad Meetings, Not Meetings
  • The thesis: "Most of us don't hate meetings. We hate meetings with no question to answer, and I'd rather fix those than ban them."
  • Type: Myth vs. reality
  • Why it's credible from this author: A project manager runs status and coordination meetings as a core part of the job, and has sat in a lot of them on both sides of the table. That gives standing to say what separates a meeting from an email in practice.
  • What the reader takes away: A simple test before any meeting: can it be written as a question the group needs to answer? If not, send an email. Managers get a concrete design rule. Early-career readers learn they can ask "what decision are we making?" without being rude.
  • Evidence it leans on:
    • Steven Rogelberg (UNC Charlotte), via CBS News, suggests structuring agendas as questions to be answered. The CBS piece is undated in the results, roughly early 2025.
    • The MIT Sloan authors' point that the problem is bad meetings, not meetings. This comes via a secondary summary, so paraphrase lightly or leave it out.
    • Meeting-free days don't fix bad meetings on their own (same caveat).
  • What the author should admit not knowing: Whether the question-agenda rule works in every kind of meeting. There's no verified data on project status or cross-team coordination meetings specifically. Their own calendar is the better evidence if they track it.
  • Risk: It can read as a tidy listicle of tips. The sharper version states a firm position: if you can't name the question, cancel it.

Angle 2: Protect The Juniors

  • Name: The Cost Of Cutting
  • The thesis: "The 'cut meetings' crowd is half right. Before I delete a meeting, I ask who was learning in it."
  • Type: Contrarian take
  • Why it's credible from this author: Writing for both early-career people and managers puts the author at the point where those interests collide. They can say what a manager should weigh before cancelling. It argues against the author's own starting frustration, which makes it more credible than a rant.
  • What the reader takes away: Managers: audit meetings for who benefits and keep the ones where junior people get exposure to senior thinking, even if the agenda is imperfect. Juniors: meetings may be one of your better learning channels, so go in prepared.
  • Evidence it leans on:
    • Deming, Løken, Willén and Xu, NBER working paper (reported September 2026): meetings take about 12% of work hours and 14% of firm wage bills, based on 9,000+ Norwegian workers. Meeting intensity correlates with wage growth, and workers in meeting-heavy firms report more on-the-job learning, especially from senior colleagues.
    • SHRM's report of the paper: an average of 4.7 hours a week in meetings.
    • Counterweight: Asana (2024) figures on dreading meetings are secondary, so skip them.
  • What the author should admit not knowing: The paper is a working paper, not peer-reviewed, and its findings are correlational. It doesn't show that cutting meetings harms anyone, and the data are Norwegian. The author doesn't know whether it holds at their company.
  • Risk: It may sound like a defense of meetings the audience hates. It could also be read as excusing bad meetings. The post must separate "keep meetings that teach" from "keep meetings."

Angle 3: Count Before You Cut

  • Name: Audit, Then Decide
  • The thesis: "Meeting-free days are the popular fix, but I'd start by measuring what my own calendar actually costs."
  • Type: Practical framework
  • Why it's credible from this author: Project managers already track time, scope and dependencies. Treating meetings as a budget fits the role, and the post stays a method rather than a result.
  • What the reader takes away: A short method: list recurring meetings, note the purpose and who attends, and keep, shorten or replace each with a written update. Managers get a way to decide that isn't just a ban. Juniors get permission to ask what a meeting is for.
  • Evidence it leans on:
    • Deming et al.: 12% of work hours and 14% of wage bills, a useful benchmark to compare against one's own calendar. Cite as a working paper, September 2026 at the earliest.
    • Microsoft Work Trend Index 2025 (April 2025; 31,000 workers, 31 markets): people are interrupted every two minutes during core hours, and 60% of meetings are ad hoc.
    • Meeting-free days: the MIT Sloan Management Review study (2022, 76 companies) via HBR's March 2022 article. Use the 71% figure carefully, as it's tied to a 40% meeting reduction. Don't use the 35% single-day figure, which is unverified.
    • Atlassian's Loom No Meeting Day: 85% of 120 respondents wanted it permanent. This is a small internal survey, so use it only as an illustration.
  • What the author should admit not knowing: What share of their own meetings would survive an audit. There's also little verified evidence on how many meeting-free days is best; the claims that gains peak at three days are unverified.
  • Risk: It can sound like generic productivity advice. The post needs one firm stance, such as "Ban nothing until you've counted," or it blends into every other meetings post.

Editor

Done1.2s

You were asked

Which angle should your post take?

Your choice

Bad Meetings, Not Meetings

Editor

Done4.3s

You chose "Bad Meetings, Not Meetings", so I've briefed the Ghostwriter to draft the post in your voice.

🧭 Editor → ✍️ Ghostwriter

Write the LinkedIn post using the angle "Bad Meetings, Not Meetings": most of us don't hate meetings, we hate meetings with no question to answer; if you can't name the question, send an email or cancel it. Author: a project manager at a mid-sized company, posting as an individual under their own name, first-person "I", plain spoken, peer-over-coffee tone. Audience: early-career people and other managers; give each a concrete takeaway (managers: question-style agenda; juniors: how to politely ask "what decision are we making?"). Evidence to use sparingly, with dates: Rogelberg (UNC Charlotte) suggests framing agendas as questions to answer (CBS News); Deming et al. NBER working paper, September 2026 (not peer reviewed): meetings take ~12% of work hours, and meeting-heavy firms report more on-the-job learning from seniors, which is a reason not to just ban meetings. Do not use the unverified stats (35%, 72%, Pinterest, etc.). Don't invent personal anecdotes or clients; the only personal fact is that they've sat in far too many meetings that could have been an email. Admit honestly what they don't know (no data on project status meetings; their own calendar would be better evidence). No hype words, no engagement bait, no placeholders, no employer promotion.

Ghostwriter

Done6.0s

Most of us don't hate meetings. We hate meetings with no question to answer.

I've sat in far too many that could have been an email. Looking back, the common thread wasn't length or attendee count. Nobody could say what we were there to settle.

So my rule is simple: if I can't write the meeting's purpose as a question the group needs to answer, I send an email or cancel it.

Steven Rogelberg, a professor at UNC Charlotte, suggests framing agendas as questions to be answered, as he told CBS News. "Status update" becomes "Do we move the launch date, yes or no?" One of those gets people prepared. The other gets people reading their own notes aloud.

I wouldn't ban meetings outright, though. A September 2026 NBER working paper by David Deming and co-authors (not yet peer reviewed, Norwegian data) found meetings take about 12% of work hours. It also found that people in meeting-heavy firms report more on-the-job learning, especially from senior colleagues. That's a correlation, not proof. But it's enough to make me careful about deleting the rooms where juniors hear how experienced people think.

If you run meetings: put the question at the top of the invite. If you can't, ask whether it's a meeting at all.

If you're early in your career: you can ask, without sounding difficult, "Could you help me understand what decision we're making today?" It's a fair question, and a good organizer will be glad you asked.

What I don't know: whether this holds for project status and cross-team coordination meetings specifically. I haven't seen data on those. My own calendar would be better evidence than any study, and I haven't audited it properly.

If you could only add one line to your next invite, what question would it hold?


Fact sources, for your reference: Rogelberg via CBS News (undated in research, roughly early 2025); Deming, Løken, Willén and Xu, NBER working paper, via SHRM and a September 2026 blog post (exact release date unconfirmed).

Editor

Done2.6s

Draft is in. I've sent it to the Critic for a quick quality check before you see it.

🧭 Editor → 🧐 Critic

Review the Ghostwriter's draft against the standards: authentic first-person voice, specific, no invented experiences, every fact sourced and dated, no engagement bait (check the closing question), no placeholders or notes to the author left in the post body, audience fit. Return PASS or REVISE with up to 5 specific fixes.

Criticbehind the scenes

Done9.4s

Editor

Done2.7s

The Critic asked for a revise: mainly a hedged source date, an unsupported personal claim and the closing question. I'm sending those fixes to the Ghostwriter.

🧭 Editor → ✍️ Ghostwriter

Revise the draft applying all five of the Critic's fixes: remove the footer note; say "a 2026 NBER working paper"; give Rogelberg's CBS News piece as early 2025 and make clear the launch-date example is the author's own illustration; replace "I haven't audited it properly" with the real gap (no verified data on project status/cross-team meetings, own calendar would be better evidence) without claiming what the author has or hasn't done; end on the author's point, not a question, and tighten the "Looking back" passage. Return only the post.

Ghostwriter

Done3.6s

Most of us don't hate meetings. We hate meetings with no question to answer.

I've sat in far too many that could have been an email. The common thread usually isn't length or headcount. It's that nobody in the room can say what we're there to settle.

So my rule is simple: if I can't write the purpose of a meeting as a question the group needs to answer, I send an email or cancel it.

Steven Rogelberg, a professor at UNC Charlotte, has suggested structuring agendas as questions to be answered (CBS News, early 2025). The example below is mine, not his. "Status update" becomes "Do we move the launch date, yes or no?" One gets people prepared. The other gets people reading their own notes aloud.

I wouldn't ban meetings outright, though. A 2026 NBER working paper by David Deming and co-authors (not yet peer reviewed, Norwegian data) found meetings take about 12% of work hours. It also found that people in meeting-heavy firms report more on-the-job learning, especially from senior colleagues. That's a correlation, not proof. But it makes me careful about deleting the rooms where juniors hear how experienced people think.

If you run meetings, put the question at the top of the invite. If you can't write it, ask whether it's a meeting at all.

If you're early in your career, you can ask, without sounding difficult, "Could you help me understand what decision we're making today?" It's a fair question, and a good organizer will be glad you asked.

What I don't know is whether this holds for project status and cross-team coordination meetings specifically. I haven't seen verified data on those. Someone's own calendar would be better evidence than any study I've cited.

Until then, I'd rather fix a meeting than ban it, and the fix starts with one question at the top of the invite.

Editor

Done2.1s

The Critic flagged five fixes (an unconfirmed date, an unsupported personal claim, engagement-bait closing and more), and the revised draft above applies them.

You were asked

Happy with this draft, or do you want changes?

You

I don't have a rule like that yet, so don't say "my rule is" or that I cancel meetings. Frame the question-first idea as what I think works and what I'd suggest, not something I already do.

Editor

Done2.7s

You don't have that rule yet, so I'm asking the Ghostwriter to reframe it as what you think works and would suggest.

🧭 Editor → ✍️ Ghostwriter

Revise per the author's feedback: they don't have a rule like that yet. Remove "my rule is" and any claim that they send emails or cancel meetings. Reframe the question-first idea as what they think works and would suggest (e.g. "I think the test is...", "I'd suggest..."). Also fix the closing line and any "I'd rather fix than ban" phrasing so it's opinion, not a stated habit. Keep the sourcing fixes and the "what I don't know" section. Return only the post.

Ghostwriter

Done3.5s

Most of us don't hate meetings. We hate meetings with no question to answer.

I've sat in far too many that could have been an email. The common thread usually isn't length or headcount. It's that nobody in the room can say what we're there to settle.

I think the test is simple: can the purpose of the meeting be written as a question the group needs to answer? If it can't, I'd suggest an email or no meeting at all.

Steven Rogelberg, a professor at UNC Charlotte, has suggested structuring agendas as questions to be answered (CBS News, early 2025). The example below is mine, not his. "Status update" becomes "Do we move the launch date, yes or no?" One gets people prepared. The other gets people reading their own notes aloud.

I wouldn't ban meetings outright, though. A 2026 NBER working paper by David Deming and co-authors (not yet peer reviewed, Norwegian data) found meetings take about 12% of work hours. It also found that people in meeting-heavy firms report more on-the-job learning, especially from senior colleagues. That's a correlation, not proof. But it makes me careful about deleting the rooms where juniors hear how experienced people think.

If you run meetings, I'd suggest putting the question at the top of the invite. If you can't write it, ask whether it's a meeting at all.

If you're early in your career, you can ask, without sounding difficult, "Could you help me understand what decision we're making today?" It's a fair question, and a good organizer will be glad you asked.

What I don't know is whether this holds for project status and cross-team coordination meetings specifically. I haven't seen verified data on those. Someone's own calendar would be better evidence than any study I've cited.

Still, my view is that a bad meeting is better fixed than banned, and I think the fix starts with one question at the top of the invite.

Editor

Done1.9s

I've reworded the question-first idea as your opinion and suggestion, not a habit you already have.

You were asked

Is this version ready for the final package, or do you want more changes?

You

Approved

Editor

Done2.1s

You've approved the draft, so the Finisher will now build the final package.

🧭 Editor → ✨ Finisher

Turn the approved draft (latest Ghostwriter version, unchanged in substance) into the final package: the post, 2 alternative hooks, a first comment with sources and dates (Rogelberg via CBS News, early 2025; Deming, Løken, Willén and Xu NBER working paper 2026, via SHRM; flag the exact release date as unconfirmed), and a few hashtags. No engagement bait, no placeholders.

Finisher

Done6.0s

The post

Most of us don't hate meetings. We hate meetings with no question to answer.

I've sat in far too many that could have been an email. The common thread usually isn't length or headcount. It's that nobody in the room can say what we're there to settle.

I think the test is simple: can the purpose of the meeting be written as a question the group needs to answer? If it can't, I'd suggest an email or no meeting at all.

Steven Rogelberg, a professor at UNC Charlotte, has suggested structuring agendas as questions to be answered (CBS News, early 2025). The example below is mine, not his. "Status update" becomes "Do we move the launch date, yes or no?" One gets people prepared. The other gets people reading their own notes aloud.

I wouldn't ban meetings outright, though. A 2026 NBER working paper by David Deming and co-authors (not yet peer reviewed, Norwegian data) found meetings take about 12% of work hours. It also found that people in meeting-heavy firms report more on-the-job learning, especially from senior colleagues. That's a correlation, not proof. But it makes me careful about deleting the rooms where juniors hear how experienced people think.

If you run meetings, I'd suggest putting the question at the top of the invite. If you can't write it, ask whether it's a meeting at all.

If you're early in your career, you can ask, without sounding difficult, "Could you help me understand what decision we're making today?" It's a fair question, and a good organizer will be glad you asked.

What I don't know is whether this holds for project status and cross-team coordination meetings specifically. I haven't seen verified data on those. Someone's own calendar would be better evidence than any study I've cited.

Still, my view is that a bad meeting is better fixed than banned, and I think the fix starts with one question at the top of the invite.

Two alternative hooks

Each replaces the first two lines (the opening line and the "far too many" line).

Hook A I've sat in far too many meetings that could have been an email. The problem was rarely the meeting itself. It was that nobody could say what we were there to settle.

Hook B A meeting without a question to answer is just a group of people waiting for it to end. I'd rather fix those meetings than ban meetings altogether.

First comment

Sources for the post:

  • Steven Rogelberg (UNC Charlotte) on structuring agendas as questions to be answered: CBS News, early 2025 (exact date not confirmed)
  • David Deming, Katrine V. Løken, Alexander Willén and Yaling Xu, NBER working paper, 2026 (meetings average about 12% of work hours; meeting intensity linked to more on-the-job learning). Reported by SHRM, "Meetings May Be More Valuable Than Many Think," 2026. The exact NBER release date is unconfirmed, and the paper is not yet peer reviewed.

Hashtags

#Meetings #ProjectManagement #Leadership

Editor

Done2.1s

Your post, two alternative hooks, a first comment with sources and hashtags are ready above. Before you post, check two dates. The CBS News piece and the NBER paper's exact release are both unconfirmed, so look them up and add the dates to your first comment if you can. Hook B says "I'd rather fix those meetings than ban meetings altogether". That is your opinion, but it reads close to a habit, so reword it if you use that hook.

The team is done

Try it with your own brief