# Meeting best practices that make time worth it

**Meeting best practices** are not about prettier slides.
          Productive meetings have a purpose, the right people, a path to a decision or artifact, and a clear follow up.
          Everything else is theater that steals maker time.
        

        
## Start with purpose, not calendar habit

        

          Before you hit send on an invite, finish this sentence: we are meeting so that ___.
          Good endings look like “we choose option A or B,” “we unblock the release,” or “we align on the hiring bar.”
          Bad endings look like “sync” or “catch up” with no outcome.
        

        

          If the purpose is information only, write it instead.
          Engineering teams especially pay a tax when status that could live in a doc becomes a recurring call.
        

        
## Invite fewer people on purpose

        

          Every extra attendee raises cost and lowers honesty.
          Distinguish required decision makers from optional listeners.
          Make optional real: people should feel safe to decline without political risk.
        

        

          - Required: people who decide or own the work.

          - Optional: people who need awareness, can read notes later.

          - Not invited: people added “just in case.”

        

        
## Agenda rules that actually get used

        

          A useful agenda is short and decision oriented:
        

        

          - Outcome in one line.

          - Topics with time boxes.

          - Links to pre reads, due before the meeting.

          - Open questions that need input live.

        

        

          Send it with the invite, not two minutes before start.
          If nobody did the pre read, reschedule the decision portion instead of improvising from cold.
        

        
## Run the room for decisions, not monologues

        

          The chair’s job is progress, not airtime.
          Park tangents on a visible list. Time box debate. Restate the decision when you have it.
          If conflict stalls, name the disagreement and pick a path or a spike with an owner.
        

        

          Facilitation humility matters here.
          See
          [how to facilitate a meeting](https://isilta.com/blog/how-to-facilitate-a-meeting/)
          for habits that keep managers from answering every question themselves.
        

        
## Close with owners, dates, and a feedback loop

        

          End five minutes early for two things: action capture and a quick pulse on value.
          Write owners and due dates where the team already works.
          Then ask a lightweight ROTI or one
          [meeting feedback question](https://isilta.com/blog/meeting-feedback-questions/)
          so the next session improves.
        

        
## Practices that raise productivity without more meetings

        
| Practice | Why it helps | Failure mode |
| --- | --- | --- |
| Async updates first | Live time goes to decisions | Updates still get read aloud |
| 25 or 50 minute defaults | Creates buffer and focus | People still stack meetings back to back |
| Decision log | Stops reopening settled topics | Log exists but nobody searches it |
| Standing agenda review monthly | Kills zombie meetings | Calendar inertia wins |

        
## A weekly checklist for managers

        

          - Scan your calendar for meetings without a written outcome.

          - Convert at least one to async this week.

          - Cut one optional attendee from a crowded invite.

          - Require pre reads for any design or planning decision.

          - Publish actions within an hour of ending.

        

        

          Do this for a month and “how to make meetings more productive” stops being a slogan.
          It becomes a measurable drop in low value hours.

## Frequently asked questions

### What is the most important meeting best practice?

A written purpose and outcome before anyone joins. If you cannot name the decision or artifact, the meeting should probably be async.

### How long should a team meeting be?

Default to 25 or 50 minutes, not 30 or 60. Shorter slots force prioritization and give people a buffer to think.

### How do you make meetings more productive without more process?

Cut attendees, require pre reads for decision meetings, and end with owners and dates. Process is light when purpose is sharp.

### Should every meeting have an agenda?

Yes for recurring and decision meetings. A three line agenda beats a blank invite. Skip heavy templates that nobody reads.

Related: [meeting feedback questions](https://isilta.com/blog/meeting-feedback-questions/), [how to facilitate a meeting](https://isilta.com/blog/how-to-facilitate-a-meeting/), [why 1 on 1s feel like a waste of time](https://isilta.com/blog/why-1on1s-feel-like-waste-of-time/).