> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to run meetings that produce decisions
- URL: https://blog.jestor.com/run-meetings-that-produce-decisions/
- Published: 2026-09-16T18:56:07.000Z
- Updated: 2026-09-16T18:56:07.000Z
- Author: Bruno Bannach

**Meetings that produce decisions** differ from status meetings in one respect: the information was available before the meeting, so the hour is spent deciding. In **Jestor**, dashboards read live data, so preparation is reading rather than assembling.

## Why operational meetings become status rounds

Each area reports what happened. The reporting fills the time, everyone half listens to the parts that do not concern them, and the meeting ends without anything being decided.

It happens because assembling the information is the hardest part, so it becomes the content.

What changes when preparation disappears:

- The hour is spent on decisions rather than on reporting
- Everyone reads the same numbers beforehand
- Exceptions drive the agenda
- Actions are recorded during, not after
- Absent people can still follow what happened

## Meeting types worth separating

| Type            | Purpose                       | Failure mode                          |
| --------------- | ----------------------------- | ------------------------------------- |
| Decision        | Choose between options        | Becomes discussion without a decision |
| Review          | Assess against a plan         | Becomes reporting                     |
| Problem solving | Work through a specific issue | Too many attendees                    |
| Information     | Share something broadly       | Should have been written              |

## Step by step to run one

1. **State the type** in the invitation, so expectations match.
2. **Publish the material beforehand**, live rather than as a deck.
3. **Open with exceptions**, not with area reports.
4. **Name the decisions** the meeting must produce.
5. **Record actions during the meeting**, with owners and dates.
6. **Start the next one** by reviewing those actions.
7. **Cancel the meeting** when there are no decisions to make.

## Why cancelling is the practice that proves the rest

A recurring meeting that runs regardless of whether there is anything to decide will drift back into a status round. Cancelling it occasionally, when the dashboard shows nothing requiring a decision, is what keeps the format honest and demonstrates that the meeting exists for a purpose.

## Why choose Jestor

In **Jestor**, dashboards read live from the records the team works in, so material is current without preparation. Exceptions can be filtered views, actions recorded during the meeting become tasks on the boards where work already happens, and drill down settles any question about a number.

## Frequently Asked Questions

### Why do operational meetings become status rounds?

Because assembling information is the hard part, so it becomes the content. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### What should the agenda open with?

Exceptions, since they are what the meeting can act on.

### When should a recurring meeting be cancelled?

When there is nothing requiring a decision, which keeps the format honest.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.