# What Makes a Good Meeting (and What Makes One Waste Your Time) Canonical URL: https://headwayskills.com/knowledge/communication/good-meeting/ Markdown URL: https://headwayskills.com/knowledge/communication/good-meeting.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A good meeting has one purpose, an agenda sent in advance, the right people, and a close that names who does what by when. Here's how to get there. ## Key facts - Title: What Makes a Good Meeting (and What Makes One Waste Your Time) - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Time Management - Primary keyword: good meeting - Source page: https://headwayskills.com/knowledge/communication/good-meeting/ ## What this page covers - A good meeting has one purpose, an agenda sent in advance, the right people, and a close that names who does what by when. Here's how to get there. - Practical guidance for good meeting - How this topic connects to Communication ## Detailed explanation You have sat through the meeting that ended exactly where it started: forty minutes, nine people, no decision, and a vague sense that someone will follow up. A good meeting is the opposite of that, and it is not hard to describe. It has one stated purpose, an agenda sent in advance, only the people who can actually contribute, a length matched to the work rather than to the calendar, real discussion instead of a monologue, and a close that names what happens next and who owns it. Almost anyone can list those six things. Meetings still drift anyway, which suggests the problem is not knowledge. It is a small set of decisions that get made, or skipped, before anyone joins the call. ## What actually makes a good meeting? Purpose comes first, and it is not the same thing as an agenda. The purpose is why the meeting exists at all; the agenda is how the time inside it gets spent. A meeting can have a detailed agenda and still be pointless if nobody can say what it is supposed to produce. In survey data compiled by Flowtrace, 72% of professionals named clear objectives as the key to an effective meeting and 67% named a clear agenda, and the two get treated as one thing far more often than they should be. McKinsey sorts meetings by what they are for rather than by what they look like: making a decision, solving a problem or generating options, coordinating and updating, or sharing information one way. That sorting matters more than it sounds, because the same behavior is good in one type and a failure in another. Open-ended discussion is the entire point of a problem-solving session and a waste of everyone's afternoon in a status update. ## How long should a meeting be? Shorter than your calendar suggests. Widely cited survey figures put attention at around 91% in meetings under 15 minutes, with a steep drop as length grows, which is the evidence behind the standard advice to stay under an hour and to default to smaller blocks. The sixty-minute default is an artifact of calendar software, not of the work. One rough convention that circulates among practitioners ties duration to purpose instead: about ten minutes for a check-in, thirty for a status update or a one-on-one, fifty when several topics need airing, and ninety for genuine problem-solving. Treat it as an illustration rather than a rule. The useful move is deciding the length after you know the purpose, instead of booking an hour and then finding something to fill it. ## Do I really need to be in this meeting? Often, no. The University of Nebraska's guidance on efficient meetings gives an unusually concrete test: invite only people who can contribute to at least half the agenda items, and for anything running longer than thirty minutes, bring specialists in only for the part that needs them. That rule explains a common experience, which is sitting through forty minutes in order to speak for three. This matters because volume, not incompetence, is the dominant complaint. In the same survey roundups, 78% of professionals said too many meetings was the leading reason meetings are unproductive, and 47% said meetings waste more of their time than anything else at work. If you are an attendee rather than the organizer, the practical version is a question you can ask before accepting: which agenda items am I needed for? A reasonable organizer will either answer it or realize they invited you out of habit. ## Does a short meeting still need an agenda? Yes, though "agenda" can mean two lines in the invitation. The most consistent piece of advice across the research on meetings is to circulate it at least 24 hours ahead, which Atlassian frames as the thing that makes preparation possible at all. Harvard Business Review pushed the same point further in 2023, arguing that preparation rather than facilitation skill is what separates good meetings from bad ones. A day's notice does something else that is easy to miss: it lets people push back on the contents before the meeting happens. Half the items that turn a thirty-minute meeting into an hour are items that should never have been on the list, and the only person who can catch that is someone who saw it in advance. ## How much should I be talking during meetings? It is a real and mostly unanswered worry. There is a discussion thread on TeamBlind with the title asked flatly: how much should I be talking during meetings. The honest answer is that it depends on which of the four purposes you are in. A problem-solving meeting wants your half-formed thought; a status update wants your update and nothing else. Beyond that, the useful habits are specific rather than temperamental. [State your main point first](/knowledge/communication/concise-communication/) instead of narrating your way toward it. Be brief. Moderate how long you hold the floor, and notice when you are talking past the moment your point landed. Listen with an actual intention to understand rather than to wait for a gap. The bigger reframe is for the person who says nothing. Advice on [speaking up in meetings](/knowledge/professional-behaviors/how-to-speak-up/) converges on something procedural, not psychological: ask for the agenda in advance and write down two or three points you intend to make. That turns a confidence problem into a preparation problem, which is a far more solvable kind of problem. Facilitators also have their own version of this, gently calling on quieter attendees so that everyone gets an opening, so being asked directly is normal rather than a sign you have been caught out. If holding your ground in a room is difficult in ways that go beyond meetings, it is worth a look at **[where your work habits stand](https://assessment.headwayskills.com/)** before you assume meetings are the problem. ## What do I do when a meeting goes off topic? You do not need to be [chairing](/knowledge/communication/running-meetings/) to fix this, and the move is smaller than it feels. Name the agenda item rather than the behavior: say which item the group was on and ask whether the current thread belongs to it or somewhere else. That reads as helpful rather than as a rebuke, because it is about the list, not about the person talking. The second half is parking it properly. Meeting guidance is consistent that the right home for a genuinely important tangent is a follow-up session with the smaller group of people it actually concerns. Say that out loud and it stops being an interruption you shut down and becomes an item you routed. ## How do I end a meeting so something actually happens afterwards? By protecting the last five minutes, which are the first thing to get cut when a meeting runs long. A substantial share of workers report leaving meetings unclear on what happens next or who owns it, and every serious guide on meetings closes on the same instruction: finish with the actions, each attached to a named person and a date. The failure here is structural rather than lazy. The closing summary sits exactly where the time pressure is worst, so it needs to be defended deliberately, either by ending the discussion early on purpose or by someone simply asking, before people start leaving, what the agreed actions are. If nobody in the room can answer that, the meeting has not finished, it has only stopped. ## Is it okay to decline a meeting invitation? Sometimes, with care. [Declining is a skill](/knowledge/time-management/how-to-say-no-at-work/) that runs on credibility, which means it works better once you have built up a track record than it does in your first month. When you do decline, do it clearly and give the reason rather than letting the invitation sit unanswered. There is usually a middle option worth taking first. Ask what you are needed for, offer to contribute the piece that concerns you in writing beforehand, or ask to attend only the relevant item and read the notes for the rest. That protects your afternoon without signaling that you are unavailable to your colleagues, and it quietly nudges the organizer toward a shorter invitation list next time. ## The skills a good meeting runs on Read those answers next to each other and a pattern surfaces. Almost none of them are about the meeting itself. They are about preparing before you walk in, knowing how much to say and when, respecting other people's time as a matter of course, and being honest about what deserves an hour. Those are ordinary work habits that meetings simply make visible. **Communication** carries most of the load, and its meeting component is more concrete than the word suggests: knowing which of the four kinds of meeting you are in, preparing for it properly, holding the conversation to its purpose, and leaving a usable record behind. The participation habits sit here too, including stating your main point first, keeping it brief, and managing interruptions without either steamrolling or disappearing. Note what this is not. It is not presentation skill, and a meeting is not an audience. **Professional Behaviors** covers the part of a meeting that is conduct rather than content. Arriving on time, keeping distractions to a minimum, and handling video calls decently are norms with reasons behind them rather than etiquette for its own sake, since each one costs someone else attention when it slips. The behaviors that damage meetings most are equally specific: contributing nothing, complaining without offering anything, and treating other people's items as less important than your own. **Time Management** decides which meetings you are in at all, which turns out to be the largest lever available to you. Saying no clearly and with a reason is part of it, as is knowing that this is a skill you use once you have earned some standing rather than in your first week. So is being honest about which activities genuinely deserve your hours, and removing the distractions that make you a worse participant when you are in the room. Those three habits show up far outside a meeting room, which is the point of measuring them rather than guessing. A free seven-minute assessment gives you **[your full skills picture](https://assessment.headwayskills.com/)** across the twelve work skills this one belongs to, and the gaps it surfaces are learnable ones. ## If meetings are part of your week Some of this will already describe how you work. People who are good in meetings are rarely the most talkative ones in the room; they are usually the ones who read the agenda beforehand and thought about what they were actually there to do, which is close to what you have just spent a few minutes doing here. Whatever is missing is missing in practice, not in personality, and nothing above asks you to become a different person at work. It does compound. The meetings you are asked into get longer, larger, and more consequential as your responsibilities grow, and the habits you carry into them now are the ones you will still be using then. Knowing which of those habits to work on first is what turns a general intention into something you can start on before your next invitation lands. ## See where your work skills stand The only thing left is finding out which of these habits are already working for you and which ones are costing you time you have not noticed. The Job Skills Test is a **free** seven-minute self-assessment of your work skills. It shows you where you stand across all twelve of them, so you can pick the one or two that will change the most about how your next meeting goes instead of trying to improve everything at once. **Take the skills test** *Free, about seven minutes, and nothing to prepare beforehand.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A good meeting has one purpose, an agenda sent in advance, the right people, and a close that names who does what by when. Here's how to get there. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Professional Behaviors, Time Management. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/time-management.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/good-meeting/ Preferred summary: "A good meeting has one purpose, an agenda sent in advance, the right people, and a close that names who does what by when. Here's how to get there." ## Change log - 2026-07-07: Content collection version published.