🚀 Executive Summary
TL;DR: Endless follow-up meetings occur because initial discussions often mistake ‘discussion’ for ‘decision,’ leading to vague agreements without concrete, assigned tasks. To solve this, enforce clear agendas with defined ‘Desired Outcomes,’ appoint a Directly Responsible Individual (DRI) for action items before meetings conclude, and empower senior staff to decline invites lacking a clear purpose.
🎯 Key Takeaways
- Appoint a Directly Responsible Individual (DRI) at the end of every meeting to document and share concrete action items, assignments, and due dates, preventing nebulous ‘sync-ups.’
- Enforce a structured meeting agenda, including a ‘Desired Outcome’ section, to ensure meetings are scheduled only when a clear goal or decision is required, treating the agenda as a contract.
- Senior engineers should adopt a ‘No Agenda, No Me’ policy, politely declining meeting invites without a clear agenda and desired outcome to foster a culture of focused, purposeful discussions and protect team focus time.
Tired of endless follow-up meetings that could have been an email? Learn how to enforce clear agendas, assign concrete action items, and reclaim your calendar from the clutches of meeting purgatory.
So, We’re Having a Follow-Up About the Follow-Up? Let’s End This.
I remember it like it was yesterday. 3 AM, PagerDuty screaming bloody murder. The new checkout service on `prod-ecom-api-02` was failing its health checks and getting boot-looped by Kubernetes. We all jumped on a call, bleary-eyed and frantic. The junior on call, bless his heart, found that a critical secret wasn’t mounting. Someone with admin access manually injected it, the pod went green, and we all went back to bed. The next day, at 10 AM sharp, an invite pops up: “Post-Mortem Follow-Up.” In that meeting, it became clear: we fixed the *symptom*, but nobody was assigned the task of fixing the actual *problem*—the broken reference in our Helm chart. We needed a second meeting because the first one produced zero actionable, assigned work. It was a band-aid, not a cure.
The Real Problem: We Mistake “Discussion” for “Decision”
Look, I get it. We’re engineers. We like to talk about problems, poke them with a stick, and whiteboard them into oblivion. But a meeting’s purpose isn’t just to talk; it’s to *decide* and *delegate*. The endless follow-up loop happens because the first meeting ends with a vague sense of agreement but no concrete, assigned tasks. We walk away thinking, “Great, we all know the database connection string is wrong,” but no one walks away with the JIRA ticket assigned to them, with a due date, to actually go and fix it in the Vault and update the deployment configs. We leave with shared awareness, not shared responsibility.
The Fixes: From Duct Tape to a New Foundation
You can’t just tell people to “have better meetings.” That’s useless advice. You need to change the mechanics. Here are three levels of intervention I’ve used, from a quick fix to a permanent cultural shift.
1. The Quick Fix: Appoint a “DRI” Before You Hang Up
This is the duct tape, and sometimes, duct tape is exactly what you need. At the end of every single meeting, before anyone is allowed to click “Leave,” you ask one simple question: “Who is the DRI for the action items?”
DRI stands for “Directly Responsible Individual.” This person’s job isn’t to do all the work. Their job is to write down the one or two sentences that summarize the action items, who is assigned each one, and when it’s due. They then post it in the main Slack channel for the project. That’s it.
Pro Tip: Don’t let the meeting end with “Okay, we’ll all sync up on Slack.” That’s a trap. Force the summary and assignments *before* the Zoom window closes. The social pressure to not be the person holding everyone up works wonders.
It sounds simple, but it forces a moment of accountability. It turns a nebulous “we should fix the pipeline” into “Steve will update the Jenkinsfile for PR-1138 by EOD Tuesday.”
2. The Permanent Fix: The Agenda is a Contract
If you want to stop this from happening long-term, you need to be disciplined *before* the meeting ever starts. My rule is simple: if the meeting invite doesn’t have a clear agenda with a “Desired Outcome” section, I decline it. An agenda is a contract for everyone’s time.
Here’s the template I force my teams to use. It lives in a shared Confluence page.
**Meeting Topic:** Investigate `prod-auth-svc-03` Latency Spike
**1. Context (1-2 sentences):**
Since the last deployment, p99 latency for the /login endpoint has increased by 300ms. Monitoring shows high CPU on the pod.
**2. Attendees & Roles:**
- Darian (Lead Architect): Final decision-maker on infra changes.
- Sarah (SRE): Has access to observability data (Datadog).
- Mike (Developer): Wrote the new authentication logic.
**3. Desired Outcome (The most important part!):**
- A decision on whether to roll back the deployment OR
- A list of 2-3 concrete investigation tasks, assigned to specific people, with deadlines.
**4. Agenda Points:**
- (5 min) Sarah presents the latency/CPU graphs.
- (10 min) Mike explains the code changes in the last PR.
- (15 min) Discussion and decision on rollback vs. further investigation.
This structure forces the meeting organizer to think about the *end goal* before scheduling. If they can’t fill out the “Desired Outcome,” they don’t need a meeting; they need to do more research first.
3. The ‘Nuclear’ Option: The “No Agenda, No Me” Policy
This is for my fellow senior engineers and architects. You have to be the change. You have more political capital than you think. When you get a vague meeting invite with a title like “Sync on Q3 Roadmap” and nothing in the body, you must decline it. Politely, but firmly.
I have a canned response I use:
“Hey [Organizer], thanks for the invite! To make sure I can contribute effectively, could you please add a brief agenda with the key topics and the desired outcome for this meeting? If it’s just a general sync, a quick Slack update might be more efficient for everyone. Let me know!”
Nine times out of ten, one of two things happens: the meeting gets canceled and replaced with a Slack message, or a proper agenda appears within minutes. You are not being difficult; you are protecting your team’s most valuable resource: focus time. We are paid to solve complex problems, and we can’t do that if our day is fragmented into a dozen pointless sync-ups.
Summary: Choose Your Weapon
You don’t have to live in a world of endless follow-ups. Start small or go big, but start somewhere. Here’s the breakdown:
| Method | Description | When to Use It |
| Appoint a DRI | Designate one person to document and share action items before the meeting ends. | Quick, tactical fix for an undisciplined team. Good for incident response. |
| Agenda as Contract | Require all meetings to have a structured agenda with a clear “Desired Outcome.” | The best all-around, long-term fix for improving meeting culture. |
| No Agenda, No Me | Politely decline meetings that lack a clear purpose and agenda. | For senior staff who need to lead by example and protect their team’s time. |
Stop letting your calendar be a symptom of someone else’s disorganization. Fix the root cause, and you won’t need a follow-up about the follow-up ever again.
🤖 Frequently Asked Questions
âť“ Why do organizations frequently require follow-up meetings?
Follow-up meetings are often needed because initial discussions mistake ‘discussion’ for ‘decision,’ resulting in shared awareness but a lack of concrete, assigned action items and responsibilities, as seen in the example of fixing a symptom without addressing the root cause.
âť“ How do the proposed fixes compare in terms of impact and implementation effort?
The ‘Appoint a DRI’ method is a quick, tactical fix for immediate accountability in undisciplined teams. The ‘Agenda as a Contract’ is a more permanent, long-term solution for improving meeting culture by enforcing discipline before meetings. The ‘No Agenda, No Me’ policy is a ‘nuclear’ option for senior staff to lead by example, protecting focus time and driving cultural shift.
âť“ What is a common implementation pitfall when trying to assign action items in a meeting?
A common pitfall is allowing a meeting to end with a vague ‘Okay, we’ll all sync up on Slack,’ which avoids immediate accountability. The solution is to force the summary and assignment of action items with a Directly Responsible Individual (DRI) *before* the meeting concludes, leveraging social pressure.
Leave a Reply