What separates a good meeting from a bad one
No meeting is ever going to be perfect, because a meeting is by definition a group of people — with different tastes, opinions, priorities and values. It is unlikely everyone will agree on what a great meeting looks like, so a good part of the work is aligning on that definition itself. A useful starting point is the bad meeting, which is much easier to agree on:
- No clear purpose or direction
- A chaotic feel
- The wrong people in attendance
- General disrespect between participants
- A shared sense that everyone's time is being wasted
Inverting those traits gives us the good meeting: a clear purpose, an agenda, the right people in the room — not so many that communication gets complicated, not so few that the people needed to move forward are missing — some order, with nobody drifting in and out or talking over others, and a clear decision, outcome and set of next steps at the end.
Bookending the meeting: purpose and outcome
The first and last of those traits are connected. You have all come for a specific purpose, and the end of the meeting should capture what you learned about that purpose and what happens next. That is why the opening and closing of a meeting can sound similar.
An opening might state why everyone is there, present new data that frames the direction, hand off to the people who will cover implementation details, and call on a stakeholder whose team will be affected by the rollout. The close might confirm the chosen direction, verify that the affected team is comfortable with its part, state the agreed timeline, and list the next steps — exploring specific impacts and reconvening in a week on findings and process.
The example matters less than the pattern: align at the beginning and the end so that nothing major is missing and everyone is on the same page. If no decision was reached, your next steps are either to identify who will make the decision and inform everyone, or to roll the matter over to a new meeting. Ideally these bookend statements carry the information everyone needs:
- The shared purpose
- What you are doing to reach that outcome
- Who owns what
- How it will happen
- When, including the timelines
Anyone in the room who does not need that information probably should not have been invited.
Agendas: useful tool, common trap
An agenda should always state the purpose of the meeting. Beyond that, a practical format is a few talking-point bullets plus space to take notes in the document during the meeting. Be careful, though: an agenda that is locked down top to bottom with pre-written material can shut down the collaborative aspect of the meeting. In that case it should not be a meeting at all but a shared document to be consumed asynchronously — part of the purpose of a meeting is the discussion itself.
Agendas are genuinely useful, but strict rules built around them can breed a strange culture. The point of the agenda and the meeting is to collaborate on something, and that point is nullified when process is put ahead of it. The healthiest cultures treat meetings and agendas as tools for working together effectively — tools everyone equally feels responsible for making useful.
Matching the agenda to the meeting type
Brainstorming. A full agenda may be counterproductive. The purpose plus a notes section can be enough, or a whiteboarding tool with small stubbed-out areas for capturing people's thoughts.
Weekly discussion or daily standup. People can add whatever they like, prefacing each item with their name and a small category such as RD for rapid decision, D for discussion, or P for process:
- [Sarah, RD] should we block off 4 hours to triage our iceboxed issues?
During the standup the team uses a kanban board and takes turns talking through current work. This solidifies tasks and priorities for the week and allows accidental misalignment to be corrected before the work is done. The team also covers what was finished or shipped the previous week and celebrates a little, especially on tasks that took someone a long time or a lot of effort. Through trial and error, twice-weekly check-ins worked best: Monday to kick off the week and Wednesday to keep alignment and momentum going.
Cross-functional meetings. These benefit from a more formal agenda and some preparation, so every party has enough information about the purpose and the discussion. When there is a lot of material, a one-sheeter shared ahead of time is better than stuffing everything into the agenda. If everyone is too busy to read it asynchronously, give the group the first 5 minutes of the call to read it together so you start from a shared footing.
The spectrum of awkward
You led the meeting, set direction and timelines — and yet it was awkward. Some awkwardness is natural and some is more harmful. It helps to sort it by how innocuous it is.
Unfamiliarity
With a team that knows each other well and has actively cultivated trust and vulnerability, meetings flow easily; banter at the top turns into business without friction. When a meeting with a group you don't know well has awkward moments, that is natural. Conversation starters can help, but forcing them can feel stilted. Ease up on the guilt for this one.
Too many people
Conversation at some scale starts to feel performative, because so many eyes are on the person speaking. Try not to invite too many people. If someone might feel excluded, mark them optional or tell them you will report the outcome afterward. If you invite everyone because the culture says everyone must be involved in every decision, that may signal a wider problem: companies at a certain scale struggle to function without a clear understanding of ownership. Inviting everyone out of a frequent fear of hurt feelings is probably not a meetings problem but a clarity problem — see the DRI discussion below.
The thing nobody is saying
This is the most harmful kind. The meeting is awkward because people don't feel comfortable telling the truth, or there is an elephant in the room. Watch for it and act. One approach is to walk toward the fire: acknowledge that it is awkward because transparency is missing, state what you know from your perspective, and ask whether others feel the same. Then wait. People will likely be a little shocked that you said it and will need a moment to weigh telling the truth themselves — it is crucial that you not fill the silence, uncomfortable as it is. Once someone speaks up, the rest usually follow and you can dig into the problem.
Handling conflict directly
Conflict should not be avoided. Passion about the work is good, and not all conflict is negative; a meeting may exist precisely to surface where people are not aligned. There is usually a base premise or problem everyone is trying to solve, even when they see the solution differently. Find the alignment there so ideas can be fleshed out without being attached to a person's identity. That attachment is a pitfall: when two people defend their idea rather than an idea, rejection of a concept feels like rejection of a person.
Guide the discussion so nobody feels attacked, and actively prevent disrespect. It is the manager's job to disambiguate healthy conflict from attack so that respectful discourse is encouraged; ad hominem remarks need to be reeled in and the conversation steered back toward the work, or it cannot stay productive.
A useful move is to hear people out, reflect back what you think you are hearing, and tie it to a shared purpose — for example, noting that one person worries a system migration will collide with her team's big feature release while another sees the migration as urgent for stability, then observing that both share the goal of shipping features with stability and proposing to sort out which timelines are immovable so everyone stays coordinated.
Stating what you heard lets the person feel heard or correct a misunderstanding. Stating the shared goal, along with the risks and constraints behind the conflict, anchors the conversation. The final point ties both parties' understandable needs into one vision. The specifics of the wording don't matter; what matters is that people feel heard, that everyone agrees on what the conflict is, and that you stay open to the discussion while locating the base premise for having it.
It is easier said than done. If a conversation goes off the rails, take some time after the call to write down what you think happened, in two parts: the facts and your feelings about what went poorly and what could have gone better. Checking in with the facts separately matters because our brains sometimes protect us by seeing a particular version of events. If a strong conflict leaves the group at an impasse, follow up a week later and hear people out individually in the meantime — sometimes people need distance from a matter or are simply having a hard day.
Designating a DRI
A good meeting must have a DRI — a Directly Responsible Individual — who is not necessarily the person who called the meeting, and not necessarily you. You must designate who owns the project and ultimately makes the decisions. Eventually, however much input everyone offers, a decision has to be made, and plenty of things in software development have no single true answer.
The phrasing is deliberately not "person who makes decisions" but Directly Responsible Individual, because that also tells you who the person is: the one who owns the outcome. That is part of why not everyone can have an equal say — if the project's outcome rests on you, you need to own the decision-making, and people with no stake in the outcome may not grasp all the moving parts or treat the decision with due gravity. Appointing a DRI unblocks the group to make final decisions and places responsibility on the party that will carry the weight.
Several ownership systems exist, including DACI, which separates Driver, Approver, Contributors and Informed so roles are clear, along with RACI and RAPID. Use whichever fits your organization. The DRI is best identified early in a project and restated at the start of each meeting (it can go on the agenda), because when you hit a crossroads that person can unblock the group and move it forward.
Why it is worth the effort
Meetings can feel like a drag on the software engineering process, but they don't have to. There is something special about collaborating with a group of people who are respectful and working toward a common purpose. Good meetings provide clarity and save people hours or days of work when they are headed in the wrong direction, and clear ownership, documentation and only the right people in the room can keep teams in lockstep even when the problems are complex.



