How to Run (and Survive) Meetings That Produce Outcomes

"I'm stuck in back-to-back meetings all day and nothing gets done. Half of them don't even have an agenda."

I hear some version of that constantly. Here's the uncomfortable truth: meetings aren't the problem. Nobody owning the outcome is the problem.

Early in my career at TELUS, I was pulled into a cross-functional "war room" to manage a major system migration. The first few meetings were a disaster. Fifteen people. No agenda. The most senior person would talk for 40 minutes, everyone else nodded and checked their phones, and we left without a single decision.

Then the project lead quit, and suddenly I was running the room.

My first move was wrong. I tried to run it democratically: go around the table, ask everyone for "thoughts," let the conversation wander. Sixty minutes later we'd generated a lot of discussion and zero commitments.

What I learned, painfully, is that silence in a meeting is a decision. If someone sits through a 30-minute discussion about a deadline, says nothing, then misses that deadline, they made a choice. The room was assembled to hear the risk and they didn't flag it.

The shift came when I stopped treating meetings as discussions and started treating them as decision factories.

You don't need to be running war rooms for this to matter. Meetings are one of the few places where people at every level see how you think in real time. If you're early in your career, how you show up in them is one of your most visible signals, and how you run your first ones is your first real test as a leader.

The short version

• Every meeting needs a named decision or outcome. If nobody can name it, it probably should be an email.
• Show up with a position, not a question. Three minutes of prep puts you ahead of most of the room.
• Silence is agreement. If you disagree, say it in the room. No hallway vetoes later.
• Run it in three boxes: context, tension, commit. End on time.
• Nothing counts until it's written down as an owner, an action and a date.

Be the person everyone wants in the room

Most people are poor meeting participants and don't know it. When I managed a team at WestJet, the pattern was clear: the people who got promoted weren't the ones who talked the most. They were the ones who delivered the most signal per minute.

There are a few familiar archetypes:

• The Narrator restates what everyone already knows, to show they're in the loop.
• The Tangent Machine pulls the conversation toward a loosely related problem they care about.
• The Silent Passenger says nothing, agrees to everything, then sends a contradictory email 45 minutes later.
• The Politician speaks in vague generalities to avoid committing. "We should probably think about maybe exploring that."
• The Operator reads the material, arrives with a position, speaks when they have new information, a risk or a disagreement, and names their commitment out loud before leaving.

Be the Operator. Before any meeting, spend three minutes on four questions:

1. What decision is being made? If you don't know, ask the organiser before the meeting.
2. What's my position? Not "I need to hear more." You always know enough for a preliminary stance.
3. What's the one thing the room might miss? A risk, a dependency, a person who'll be upset if they're not consulted.
4. What am I willing to commit to?

A note if you're junior: you may not feel you have the standing to push back on a meeting with no agenda. You don't need to refuse it. Just ask, politely and early: "Happy to join. What decision are we hoping to land, so I can come prepared?" That one question improves the meeting for everyone, and the organiser will notice who asked.

Key idea: You don't earn influence in meetings by talking more. You earn it by moving the room closer to a decision.

Running the room: the 3-Box Framework

When it's your meeting, this is the structure I use for operational meetings. It works for a team of four and for a room of fifteen.

Pre-read. A one-page note sent a day ahead with the decision to be made, the two or three options, and the relevant data. If you can't write the decision down, you're not ready to call the room together.

Box 1, Context (5 minutes max). Fill in only what the pre-read didn't cover: new data, a concern that just surfaced. Don't read the pre-read out loud.

Box 2, Tension (10 minutes). This is where the meeting earns its existence. Put the options up and ask directly: "Who disagrees with Option A, and why?" Make it safe and expected to disagree. Silence here counts as agreement.

Box 3, Commit (10 minutes). The decision maker, named before the meeting starts, makes the call. Write it down in real time with an owner and a deadline. If it can't be decided in the room, the only acceptable output is a specific escalation: who will decide, by when.

25-minute hard stop. Not 30, not 60. The extra five minutes give people time to breathe and switch to their next thing. Respecting people's time is a discipline, not a courtesy.

A few more rules from the basics that still matter:

• Invite only who's needed. Everyone else gets the recap.
• Kill the pure update meeting. If the whole purpose is sharing information, send it in writing or a short recorded video. Save live time for decisions and disagreements.
• Send the recap the same day. Decisions, owners, dates. That's the meeting's real output.

Nothing counts until it's in the register

Most meeting failures happen after the meeting. People leave with different memories of who agreed to what. A week later, nothing has moved and everyone thinks someone else had it.

The fix is an action register: a running list, shared with everyone, with three columns that matter. Owner, action, due date. One person, never "the team." One action, starting with a verb. One real date, never "ASAP."

Start the next meeting by reviewing it. Done, not done, new date. It takes two minutes and it's the most powerful accountability tool you'll ever use, because it makes commitments visible without anyone having to nag.

Even if you're not running the meeting, you can own this. Offer to take notes and send the recap. It's visibility that also creates value, the rare kind nobody resents.

What it looks like in practice

A hypothetical example.

Jess is a shift supervisor at a busy retail location. Every Monday there's a 45-minute "team sync" with the store manager and three other supervisors. It drifts every week: scheduling complaints, a stock issue, someone's story about a difficult customer. People leave annoyed and nothing changes.

Jess offers to take notes and try a new format for a month. Her manager agrees.

On Sunday night she sends a short note: "Tomorrow's decision: how we cover the two open weekend shifts. Options: A) overtime for current staff, B) borrow from the other location, C) post a temporary role." Monday's meeting runs 25 minutes. Two minutes reviewing last week's actions. Five on context. Ten debating A versus B. The manager picks B for a month. Jess writes it in the register: "Store manager, call the other location's manager, by Wednesday."

Within a few weeks, the Monday meeting is the shortest one on everyone's calendar and the only one where things actually move. Her manager starts asking Jess to run other meetings too.

Common traps

• Meeting to avoid deciding. Recurring "syncs" can become a place where problems get discussed forever. Fix: name the decision on every invite.
• Confusing airtime with impact. Talking a lot feels like contributing. Fix: before you speak, check that you're adding something new.
• The hallway veto. Agreeing in the room, then undermining it after. Fix: disagree in the room, then commit fully.
• "The team will look into it." A team owns nothing. Fix: one name per action.
• No recap. Without a written record, memories diverge by Thursday. Fix: send decisions, owners and dates the same day.

Do this this week

Upgrade one meeting you attend or run.

1. Pick one recurring meeting on your calendar.
2. Before it, spend three minutes on the Operator's four questions and write your answers down.
3. During it, track every commitment in the action register format below.
4. Send the recap within two hours, and open the next meeting by reviewing the register.

Your tool

CopyMEETING AGENDA TEMPLATE  (send 24 hours before)

Meeting:        _______________________   Date/time: ____________
Owner:          _______________________   Length: 25 min
Decision maker: _______________________
Attendees:      _______________________   (only who's needed)

THE DECISION WE NEED TODAY:
  ______________________________________________________________

OPTIONS ON THE TABLE:
  A) ___________________________________________________________
  B) ___________________________________________________________
  C) ___________________________________________________________

PRE-READ / DATA:  [link or 3-5 bullet points]

RUN OF SHOW
  0-2   min  Review last action register (done / not done / new date)
  2-7   min  Box 1: Context - only what's new since the pre-read
  7-17  min  Box 2: Tension - "Who disagrees with Option A, and why?"
  17-25 min  Box 3: Commit  - decision, owners, dates, who to inform

-----------------------------------------------------------------
OPERATOR'S PREP (3 minutes, for any meeting you attend)
  Decision being made:      ____________________________________
  My position:              ____________________________________
  What the room might miss: ____________________________________
  What I'll commit to:      ____________________________________

-----------------------------------------------------------------
ACTION REGISTER  (shared doc, reviewed at the start of every meeting)

| # | Owner (one name) | Action (starts with a verb) | Due (real date) | Status        |
|---|------------------|-----------------------------|-----------------|---------------|
| 1 |                  |                             |                 | Open/Done/New |
| 2 |                  |                             |                 |               |
| 3 |                  |                             |                 |               |

DECISIONS MADE:  ______________________________________________
WHO NEEDS TO BE TOLD:  ________________________________________

-----------------------------------------------------------------
RECAP EMAIL (send same day)
  Subject: [Meeting] - decisions and actions, [date]
  Decided: ...
  Actions: [Owner] will [action] by [date]. (repeat)
  Open questions / escalations: [who decides] by [when]

Talk about it

1. What's the worst recurring meeting you've been part of, and what one change would fix it?
2. Which meeting archetype do you fall into when you're tired or unsure? What triggers it?
3. Where in your work does "silence is agreement" feel risky to apply, and how could you make disagreement safer?

— Evan