Meeting BS Detector

Is this meeting necessary or could it be an email?

Detects whether meetings are necessary or could be emails/async updates. Analyzes red flags like 'status update', 'touch base', no agenda. Provides alternative approaches (Loom, doc, Slack) with time saved estimates and permission to decline.

Overview

Most meetings are unnecessary and could be handled asynchronously. This tool analyzes meeting descriptions to detect BS meetings (status updates, FYI info sharing, vague 'syncs') vs legitimate ones (collaborative problem-solving, decisions, conflict resolution). Provides concrete alternatives and scripts to suggest them.

How to use it

  1. Describe the meeting (purpose, agenda if any)
  2. Add duration and number of attendees if known
  3. Get verdict: BS/borderline/legitimate with confidence score
  4. Receive alternative approach with exact template to send
  5. Use permission statement to decline or suggest alternative

Example

Scenario: Your manager scheduled a 60-minute 'weekly sync' with 8 people to share status updates. No agenda, just 'touching base on projects.'

What you do: Input: 'Weekly team sync, 60 minutes, 8 people, status updates on projects'.

Result: Verdict: BS (95% confidence). Red flags: 'Status update' (should be written), 'Touch base' (vague purpose), 60 min for info sharing (excessive), 8 people (too many for no decision). Alternative: 'Send this as a Slack thread instead. Each person posts 2-3 bullet update by Tuesday 5pm. Saves 8 hours of collective time.' Template provided: 'Hi [Manager], I think we could make our weekly sync more efficient. What if each person posted a brief status update in #team-updates by Tuesday 5pm? We could reserve meetings for collaborative problem-solving. This would save everyone an hour/week. Thoughts?' Permission: This meeting is wasting 8 collective hours/week. You're not being difficult by suggesting a better way.

Tips

Common pitfalls