A room for Meeting facilitators

Meeting Notes People Read

Capture the decision, reason, owner, and next step without writing a transcript.

Why this might help

Most meeting notes end up as long, rambling documents nobody opens twice. This room shows you a better way. Instead of writing down everything that was said, you capture four things: the decision made, the reason behind it, the person who owns it, and the next step. That's it. When your notes are this focused, people actually read them — and your team knows exactly what to do when the meeting ends.

Does this feel familiar?

  • Someone asks 'Wait, what did we decide?' two days after the meeting.
  • Your notes are three pages long but nobody can find the action item.
  • A task falls through the cracks because it wasn't clear who owned it.
  • You spend the first ten minutes of the next meeting recapping the last one.

Try this together

  1. Open a blank doc before the meeting starts and write the four headings: Decision, Reason, Owner, Next Step.
  2. During the meeting, jot only what fits under those four headings — skip the back-and-forth conversation.
  3. If a decision isn't made, write 'No decision yet' so everyone knows it's still open.
  4. Name one real person as the owner, not 'the team' — vague ownership means nobody moves.
  5. Send the note within an hour of the meeting ending, while the context is still fresh.

Four-Part Meeting Note

  1. Create a new work item in Tindlo and give it the meeting name and date.
  2. Add the four-part note — Decision, Reason, Owner, Next Step — in the Brief field.
  3. Tag the item with the relevant project or team so it's easy to find later.
  4. Attach any files or links that support the decision, so the context lives in one place.
  5. Schedule the next step as its own work item and assign it to the owner you named.

Questions worth talking about

Did we actually make a decision today, or did we just talk about the problem?

Who's the one person we'd call if this next step didn't happen?

Is our reason clear enough that someone who missed the meeting would understand why we chose this?

A few common questions

What if we made more than one decision in the meeting?

That's fine — just repeat the four parts for each decision. Keep each one short. Think of it like a small table: one row per decision. If you've got five decisions, you've got five rows. It's still much easier to read than a wall of notes.

What if someone pushes back and wants a full transcript?

Explain that the four-part note captures what matters most: what was decided, why, who owns it, and what happens next. A transcript records the conversation; this records the outcome. You can always keep a rough draft for yourself, but share the focused version with the team.

Can Tindlo help keep these notes connected to the actual work?

Yes, in a practical way. Tindlo lets you store your four-part note in a work item's Brief field alongside files, links, and a schedule. That means the decision and the task that came from it live in the same place, so your team doesn't have to hunt across different tools to find the context.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?

Engineering Leadership ExchangeEngineering leadersProduct Operations CircleProduct operations teamsProject Managers' WorkshopProject managers