A room for Meeting-heavy teams

Fewer Meetings Studio

Keep the conversations that help and remove the ones nobody needs.

Why this might help

Some meetings are genuinely useful. Others just eat up your day and leave everyone a little tired. This room helps your team tell the difference. You'll find simple ways to check whether a meeting is worth everyone's time before you send the invite. Think of it like a quick gut-check you do together. No complicated systems here — just honest questions and small habits that help you protect the time that actually matters.

Does this feel familiar?

  • Your team leaves a recurring meeting and nobody's quite sure why it happened.
  • Someone sends a meeting invite when a short written message would have done the job.
  • You're in back-to-back calls all morning and still feel behind on real work by lunch.
  • A decision that needed three people somehow turned into a calendar block for eight.

Try this together

  1. Before you book a meeting, write one sentence explaining what needs to happen by the end of it — if you can't write it, skip the meeting.
  2. Try a standing 'async first' rule: give a message or shared doc 24 hours to do the job before you schedule a call.
  3. Trim your invite list to only the people who genuinely need to decide or contribute — everyone else can read a quick summary after.
  4. Set a default meeting length of 25 minutes instead of 30 or 60, and see how often that's actually enough.
  5. At the end of each week, pick one recurring meeting as a team and ask honestly: did this help us last week? If not, pause it for a month.

Meeting Usefulness Check

  1. List every meeting your team has in a typical week — recurring ones and one-offs both.
  2. For each meeting, write down one honest answer to this question: what would not happen if this meeting didn't exist?
  3. Score each meeting on two things only — did it lead to a clear decision or action, and did the right people attend?
  4. Flag any meeting that scores low on both as a candidate to cancel, shorten, or replace with a written update.
  5. Share your results with your team and agree on one change to try for the next two weeks, then check in on how it felt.

Questions worth talking about

Which meeting on our calendar this week could have been a message instead?

Is there a recurring meeting we keep showing up to out of habit rather than need?

When a meeting does go well, what made it actually useful — can we do more of that?

A few common questions

What if my manager keeps adding meetings and I can't say no?

Start small. You don't have to cancel anything — just bring your usefulness check results to your manager as a conversation starter. Showing the pattern with real examples from your own calendar is usually more persuasive than a general complaint about too many meetings.

How do we make sure decisions from fewer meetings don't get lost?

Write them down somewhere your whole team can see. Even a short summary in a shared doc or a comment on the relevant task helps. The goal is that nobody has to call another meeting just to remember what was decided last Tuesday.

Can Tindlo help with this?

It can support the habit. Tindlo lets your team attach context — files, links, notes, and a brief — directly to work items on a shared weekly view. When that context lives alongside the actual work, you often find you need fewer check-in calls just to stay on the same page.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?

Engineering Leadership ExchangeEngineering leadersProduct Operations CircleProduct operations teamsProject Managers' WorkshopProject managers