ManageTime

Article

The meeting ended with no decision: what to do next

Write the decision down before you leave: one sentence naming what was not settled, who can settle it, and by when. Then send that sentence to that person today. A 2012 study of 92 videotaped team meetings found action planning was among the behaviors separating meetings teams rated well from meetings they did not. This page is about the meeting that ended open, with the question you brought still unanswered and nobody named to answer it. Tasks the room agreed to and then dropped are a different problem. Why the meeting went that way in the first place belongs to the meetings pillar.

What do you do when a meeting ends without a decision?

Twelve minutes over, everyone thanking each other, and the thing you came to settle is still open.

Write it down before you stand up. Not the topic, the decision: the sentence that would have been true if the meeting had done its job. Ship in March, or ship in April. Sara owns the migration, or Tom does. A topic keeps its shape for weeks and commits nobody, which is exactly why an agenda can carry one for weeks without anybody noticing. A decision written as a sentence has a shape that shows when it is missing.

Then answer the question the meeting skipped: who gets to say. Most stalled decisions are not hard. They are unassigned. Somebody in your organization can settle the thing in four minutes, and the meeting spent fifty without establishing who that is. If the answer is you, you have a task rather than a decision, and it goes wherever your tasks go. If it is somebody who sat in the room, you need one sentence from them. If it is somebody who was never in the room, that meeting could not have decided this at any length, and booking a second one with the same people repeats the mistake at the same price.

Do it while you are still in the doorway. Ten minutes out you can still reconstruct who leaned which way, what the objection actually was, and whose silence you are guessing at. By tomorrow you have the topic and a feeling, and you cannot write the sentence from those.

The meeting is over. The decision is not.

Why do meetings end without deciding anything?

Not because the room was lazy. Because of how your hour got spent, and that part has been counted.

Allen and Lehmann-Willenbrock reported two studies in Small Group Research in 2024, covering 101 problem-solving meetings between them. They coded what was said using act4teams, a scheme that sorts each contribution into a behavior type instead of summarizing the meeting, then analyzed the coded streams in INTERACT. Four distinct clusters came out. The authors named them story-telling, well-organized networking, solution-focused and problem-focused. Those profiles were linked to how the group performed on its meeting task, and linked differently from one another, which is the useful finding: how a meeting talks is not a matter of mood, and it tracks what the meeting produces.

What the paper does not hand you is a ranking. It reports that the four profiles differed in performance, not that problem-focused meetings finish last, so anybody telling you the research proves circling the problem is the killer has gone further than this study does. The setting was a laboratory, and those groups worked a meeting task rather than a decision your Thursday depends on. Take the shape of the finding. Leave the sizes.

The behavior worth naming in your own meetings has a study of its own. Kauffeld and Lehmann-Willenbrock videotaped 92 regular team meetings for Small Group Research in 2012, real teams rather than a lab, coded them the same way, and gathered team and organizational outcomes by questionnaire and telephone interview. Teams whose meetings carried more functional interaction, and the authors name problem-solving interaction and action planning among those behaviors, were significantly more satisfied with their meetings. Better meetings went with higher team productivity. Constructive interaction still related to organizational success two and a half years later.

The same paper found something sharper about the other direction. Dysfunctional communication, and criticizing other people and complaining are the examples given, related negatively to those outcomes, and those negative relationships were more pronounced than the positive ones from functional interaction. The worst of what a room does weighed heavier than the best of it. Remember that when you are tempted to start the thread about it afterwards.

One caution before you carry any of this anywhere. Both studies are correlational on this point: teams that planned actions also rated their meetings higher and were more productive, which is a pattern across 92 meetings rather than proof that adding a decision to your Thursday call makes your team productive. The field study is also from 2012, before a normal meeting was a grid of faces. And neither paper tested what one attendee should do the next morning, so the moves on this page are this site's read of the work, not a result from it.

The evidence tells you how the hour tends to go, and stops there.

Should you book another meeting or settle it over email?

The reflex is another meeting. It is usually the wrong purchase.

Ask what the decision is short of. If it is short of information, a meeting cannot supply it and will only book the same people to notice the same gap again. Somebody goes and gets the number, then sends it. If it is short of authority, you need the one person who has it, and a message reaches them faster than a calendar slot does. If it is short of agreement, and people in the room want different outcomes rather than the same outcome by different routes, that is the case where the room earns a second hour. Only the third one is a meeting.

Who owns a decision nobody was assigned? Whoever writes it down first, at least until somebody with the authority to make it takes it over. That sounds like a burden you did not ask for, and mostly it is not one, because owning it here means naming the decision and asking one person to make it rather than making it yourself. In practice the person who sends that sentence gets treated as the owner of the thing from then on. Worth knowing before you send it, and not a reason to skip sending it.

Put the sentence somewhere that carries a date. A decision you are waiting on somebody else for behaves like any other blocked item, and it goes missing the same way blocked items do. That is why Getting Things Done keeps a separate waiting-for list rather than trusting anybody to remember who owes them what. This site has a page on keeping work you are waiting on visible, and the mechanics carry over with one difference: an ordinary blocked task already has a person on the other end and this one does not. Give it one. Then you are only chasing, which is a solved problem.

What you do not do is start the thread about how that was a wasted hour. Everyone will agree with you, it will be the most honest fifteen minutes of the afternoon, and it moves nothing. The 2012 paper measured complaining inside the meeting rather than in a channel afterwards, so treat that as a caution rather than a result. The caution still stands: no decision has ever been made by a thread agreeing that one should have been.

How does your working style change the answer?

Which part of this you get wrong is fairly predictable from how you already work. The four names below are this site's own, from the working-style self-check on the home page.

Architect-leaning readers write the sentence well and send it late. The pull is to get the framing right first, to lay out the options and the trade-offs so the decision can be made properly, and a document that takes two days costs more than a wrong-shaped question would have. Send the rough sentence today. Somebody correcting your framing is information, and it arrives sooner than your own second draft.

Sprinters go the other way and simply decide it. Often that is right, and it is why stalled things move around them. The failure mode is the decision that was not theirs to take, discovered three weeks later by the person whose call it was. So spend one extra line. Say what you intend to do unless somebody objects by Thursday, and you keep the speed without the ambush.

Visionary-leaning readers leave the meeting with the problem reframed rather than settled, which is useful and is not a decision. If that is you, the discipline is narrowing it before you leave: which of two things happens next week. Save the reframe for the second meeting. Book that only once the narrow question exists.

Improvisers catch it in the corridor, which works more often than the process people would like. It also leaves no record, so the thing you settled in ninety seconds on the way to the kitchen stays settled for exactly as long as you both remember it. Send the one-line confirmation afterwards. That is the entire fix, and it takes less time than the corridor did.

So give the next meeting that ends open ten minutes in the doorway. Write the sentence nobody said. Name the person who can say it, send it to them today with a date on it, and if it turns out nobody in that room could ever have decided this, you have learned something more useful than a decision.

Frequently asked questions

What do you do when a meeting ends without a decision?

Write down the decision that did not get made, as one sentence, before you leave the room. A topic commits nobody and can sit on an agenda for weeks. The sentence that would have been true if the meeting had worked shows plainly that it is missing. Then name who can settle it, and send them that sentence today.

Should you schedule another meeting or resolve it over email?

Book the room again only when people want different outcomes; everything else moves faster in writing. A decision short of information needs somebody to go and get the number. A decision short of authority needs the one person who holds it, and a message reaches them sooner than a calendar slot does. Real disagreement is what earns a second hour.

Who should own a decision nobody was assigned in the meeting?

Whoever writes it down first, until somebody with the authority to make it takes it over. Owning it here means naming the decision and asking one person to make it, not making it yourself. Be aware that the person who sends that sentence usually gets treated as the owner from then on.

How long should you wait before chasing a decision that was never made?

Do not wait at all, because there is nobody to chase until you have named an owner and a date. An ordinary blocked task already has somebody on the other end of it. A decision that died in a meeting has neither an owner nor a date, so your first move creates them instead of waiting on them. After that the normal waiting-for rules take over.

Sources