The Three Meeting Types That Determine Whether You Need a Follow-Up Task (With a Triage Worksheet)
Published
Not every meeting needs a task afterward. But some absolutely do—and the tricky part is knowing which is which while you're still in the room.
Get it wrong in one direction and you leave a meeting with a list of tasks nobody actually needed, cluttering up your workflow. Get it wrong in the other direction and a real decision or commitment quietly disappears, with nobody quite sure who was supposed to do what.
This article gives you a simple way to tell the difference. It sorts meetings into three types, explains what each one actually produces, and ends with a short triage worksheet you can use before you close your laptop.
Why the Meeting-to-Task Question Is Easy to Get Wrong
When a meeting ends, there's a natural pull toward action. People feel like they should do something with the time they just spent. So tasks get created—sometimes useful ones, sometimes not.
Some practitioner discussions describe a related frustration: decisions made in meetings lose their context by the time someone tries to act on them later. The decision exists, but the reasoning behind it doesn't. This theme appears in a practitioner discussion about lost project context.
The root problem isn't that people forget to create tasks. It's that they haven't stopped to ask what kind of meeting just happened—and what that kind of meeting actually produces.
The Three Meeting Types
Type 1: The Decision Meeting
A decision meeting exists to reach a conclusion. Someone had a question that needed a group answer. By the end, a choice has been made.
What it produces: a decision, and often a small number of concrete next steps that flow directly from that decision.
Does it need a follow-up task? Yes, if the decision requires someone to act. No, if the decision was the endpoint itself.
The test: ask yourself, "Did someone commit to doing something as a result of this decision?" If yes, that commitment needs a task. If the decision was purely informational—a policy clarified, a direction confirmed—a task may not be necessary. A note in the right place is often enough.
A common mistake here is creating a task called "implement decision" without any specifics. That kind of task tends to sit untouched because it's too vague to act on. If you're going to create a task, make it concrete: who does what, by when, and why.
Type 2: The Alignment Meeting
An alignment meeting is about shared understanding. Everyone needs to know the same thing—a project update, a change in direction, a new constraint. No decision is being made. No one is being assigned work.
What it produces: shared context.
Does it need a follow-up task? Rarely. The output of an alignment meeting is knowledge, not action.
The mistake here is treating shared context like a deliverable. You don't need a task that says "be aware of the new timeline." What you might need is a place where that context lives so people can find it later—especially people who weren't in the room.
If your alignment meeting regularly produces tasks, that's worth examining. It may mean the meeting is actually a decision meeting in disguise, or that the information being shared isn't reaching the right people through other channels.
Type 3: The Working Meeting
A working meeting is where actual work happens together. A design review, a code walkthrough, a writing session, a planning exercise. The meeting is the work.
What it produces: a work artifact—a draft, a plan, a reviewed document, a set of open questions.
Does it need a follow-up task? Sometimes. It depends on whether the artifact is finished or whether it needs more work outside the meeting.
The test: is the thing you made in the meeting done, or does it need a next step? If it's done, no task needed. If it's a draft that needs revision, or a plan that needs approval, or a list of open questions that someone needs to answer—yes, create a task. But create it for the specific next step, not for the whole artifact.
The Triage Worksheet
Use this at the end of any meeting, before you close your laptop. It takes about two minutes.
Step 1: Name the meeting type.
- Was this a decision meeting? (We chose something.)
- Was this an alignment meeting? (We shared something.)
- Was this a working meeting? (We made something.)
If it was a mix of two types, treat each part separately.
Step 2: Ask the output question for that type.
- Decision meeting: Did someone commit to an action as a result of this decision?
- Alignment meeting: Does this context need to live somewhere accessible, or is it already captured?
- Working meeting: Is the artifact done, or does it need a specific next step?
Step 3: Apply the task rule.
- If yes to the decision question → create a task with a clear owner, action, and deadline.
- If yes to the alignment question → add the context to the right place; only create a task if someone needs to do that capturing.
- If yes to the working meeting question → create a task for the specific next step only, not for the whole artifact.
- If no to all three → no task needed. Close the meeting cleanly.
Step 4: Check the task before you save it.
A good follow-up task answers three questions in one sentence: who does what, and by when? If your task can't answer all three, it's not ready to be a task yet.
A Note on Context
One thing the worksheet doesn't fully solve is context loss. A task created right after a meeting makes sense to the person who created it. Two weeks later, the same task can look cryptic—especially to someone picking it up for the first time.
This is a problem that appears in practitioner conversations about handoffs and project continuity. A small number of practitioner discussions describe situations where work stalls not because the task was missing, but because the reasoning behind it had disappeared. One example appears in a practitioner discussion about maintaining work context across a team.
The fix isn't complicated. When you create a follow-up task, add a brief note—one or two sentences—explaining why it exists. What decision created it? What's the goal? That note is what lets someone else pick it up without needing to reconstruct the whole meeting.
How Tindlo Fits In
If you're using Tindlo, the follow-up task you create after a meeting can carry that context with it. Each work item in Tindlo has a Brief field where you can capture the reasoning, plus space for Links and Files if there's supporting material from the meeting. You can also tag the item and connect it to the right people so it doesn't float in isolation.
Because Tindlo shows work across time in Day and Week views—alongside your Google Calendar—you can see a follow-up task sitting next to the meeting that created it, and next to the other work it has to fit around. That makes it easier to judge whether the task is realistically scheduled, not just theoretically assigned.
If you'd like to try it, Tindlo is free to get started. You can bring in your Google Calendar and start building a clearer picture of where your follow-up work actually lives.
The Short Version
- Decision meetings produce commitments. Create a task only if someone committed to an action.
- Alignment meetings produce shared context. Capture it somewhere; don't reflexively create tasks.
- Working meetings produce artifacts. Create a task only for the specific next step, if one exists.
- A good task answers: who does what, by when?
- Add a brief note explaining why the task exists. Future you—and your teammates—will thank you.
The goal isn't to create fewer tasks or more tasks. It's to create the right ones, with enough context that they actually get done.