Join the LadVen OS testing programRequest a demo
Skip to main content

Meeting to Tasks

A meeting is expensive: one hour with six people is six working hours. It pays off only through decisions that someone executes afterwards. If decisions stay in memory, in a notebook, or in a chat protocol, the same topic is discussed all over again a week later.

There is one rule: a meeting decision exists only if it became a task — with an assignee, a deadline, and a clear result.

Before the Meeting: an Agenda Built on Slices​

A good meeting starts not from a blank page but from the state of the work:

  • open the saved slice for the department or project — overdue work, acceptance, tasks without an assignee;
  • participants see the same slice in advance and come with answers instead of hearing the questions at the meeting;
  • new topics are added to the agenda, not used to replace the review of the state.

Which slices to keep ready is described in Task List, Filters, and Views.

During the Meeting: Record at the Moment of Decision​

Tasks are created right at the meeting, not "afterwards, from memory":

  1. A decision is voiced — immediately ask: who does it, what the result will be, when it is due.
  2. One assignee. "Everyone will handle it" means nobody will.
  3. The task is created at the moment of agreement — it takes 30 seconds: title, assignee, deadline. Details can be added after the meeting, but the card and the owner appear right away.
  4. If the decision concerns an existing task, the comment and the new deadline go into its card, not into a separate protocol.
  5. Decisions without an executor (take note, change a rule) are recorded as a comment on the relevant object: a process, a template, a client.

By the end of the meeting the protocol already exists — as tasks, not as text that still has to be "distributed."

After the Meeting: Five Minutes, Not an Hour of Minutes​

  • Walk through the created tasks: each one has a result description and a deadline.
  • Add the details: files, checklists, observers — where needed.
  • No separate protocol is required: the list of meeting tasks is the protocol. If your company expects a written summary, make it a short list of links to the tasks.

At the next meeting, the review starts from the tasks of the previous one in the same slice — done, overdue, waiting for acceptance. The checklist for the review itself is in Task List, Filters, and Views.

Signs the Discipline Broke​

  • Meeting outcomes live in chats and notes, and "distributing them into tasks" is a separate job nobody does.
  • The same topic is discussed at the third meeting in a row — decisions do not turn into tasks.
  • After the meeting, participants remember the agreement differently.
  • Meeting assignments get lost — see the scenarios Work gets lost between people and Manager Assignment Control.

Each of these symptoms has the same cure: record the decision as a task at the moment of agreement.

For a small team and for a large department

Small team: one meeting per week over a shared slice, and the meeting facilitator creates tasks as the discussion goes. Do not introduce a separate "minutes owner" — that role belongs to the reporter of each task.

Large department or enterprise: cascade the meetings — teams review their slices before the joint meeting, and only exceptions and cross-team decisions go up. Create cross-team tasks with observers from both sides right away, so the agreement is visible to all participants.

Common Mistakes​

  • A protocol instead of tasks. A nice summary text nobody opens. Only what became a task gets done.
  • Tasks "after the meeting." Half of them are created from memory, wording blurs, deadlines are set at random.
  • A decision without an owner. "We should do it" without a name is not a decision but a wish.
  • A meeting instead of acceptance. Results are accepted "verbally" at the meeting, tasks stay open or get closed without a check. Acceptance lives in the task: see Review and Close a Task.
  • Discussing statuses that are visible in the slice. Do not spend the meeting retelling what the list already shows — discuss decisions on deviations.

Meeting Checklist​

  • The agenda is built on a saved slice, and participants saw it in advance.
  • Every decision became a task: assignee, deadline, result — at the moment of agreement.
  • Decisions on existing tasks are written in their cards.
  • After the meeting, tasks got their details within 5 minutes.
  • The next meeting starts from the tasks of the previous one.
Last updated on