Friction MapPractical systems for ADHD work & life日本語

Work Systems

Meeting notes that survive the meeting: owners, actions, and dates

Turn discussion into a short record of decisions, owners, next actions, due dates, and the next check—without transcribing every sentence.

A stream of conversation bubbles is filtered into three clear cards for a decision, an owner, and a next action
Filter the meeting into what changed, who owns it, and when it becomes visible again.
Quick take

See the decision before the details

Capture change

Separate confirmed decisions from proposals, interpretation, and unresolved questions.

Make movement visible

Record owner, observable next action, due date, and the next check.

Verify the recap

Invite correction and treat transcripts or AI summaries as drafts, not authority.

Transcription is not the same as usable notes

Attention and working-memory demands can rise quickly when several people speak, topics change, and decisions are implied rather than stated. Trying to capture every sentence may leave the important handoff hidden inside pages of text.

Adults with ADHD may experience difficulty with organization, planning, time management, or remembering daily tasks. Similar meeting problems can also come from an unclear agenda, poor facilitation, excessive workload, ambiguous authority, or a conversation that never reached a decision. Incomplete notes are not evidence of ADHD by themselves.

The practical goal is not a perfect record of everything said. It is a reliable bridge from the discussion to the systems where decisions and commitments will be carried out.

Know which record you are making

Personal working notes, a shared recap, and formal minutes have different jobs. Formal governance, legal, clinical, regulatory, safety, and employee-relations meetings may require specific attendees, wording, approvals, retention, or records controls. Follow that process instead of substituting a personal template.

For an ordinary project meeting, agree who owns the shared record and where it will live. If no shared record is expected, your personal notes should still separate confirmed decisions from your interpretation or open questions.

Capture five fields, not every sentence

  • Decision: What is now true, approved, rejected, deferred, or changed?
  • Owner: Which named person or role accepted responsibility for the next movement?
  • Next action: What observable change will that owner make?
  • Due date: When must the action be delivered, received, or reviewed?
  • Next check: When and where will the group see the result or surface a blocker?
A staged documentary overhead photograph shows colleagues around a wooden meeting table with a blank notebook and five blank action cards
Illustrative staged photograph: five empty fields make missing decisions and ownership visible before the meeting closes.

Write unknown when a field was not agreed. A blank owner or guessed date is useful evidence that the meeting has not finished assigning the work; do not silently convert a group intention into your own commitment.

Use a light capture code during the meeting

  • D — confirmed decision.
  • A — action that still needs an owner or a clear verb.
  • ? — unresolved question or assumption.
  • B — blocker, dependency, access need, or approval.

The symbols are only a fast personal capture method. After the meeting, convert them into ordinary language that other people can understand. Keep a link to the agenda, source document, or project location rather than copying sensitive material into an extra system.

Ask for the sentence the notes are missing

When a decision is unclear, use a neutral confirmation: “Before we move on, can I check what was decided and who owns the next step?” For timing, ask: “What needs to be visible by the next check, and when is that check?” These questions improve the handoff for the group and do not require disclosing a diagnosis.

Before the meeting ends, read back only the commitments and unresolved decisions. A short correction while the participants are present is usually safer than reconstructing intent from private notes later.

Run a five-minute post-meeting conversion

  1. Mark every confirmed decision and separate it from proposals, questions, and background discussion.
  2. Rewrite each action as owner + observable verb + output. Replace “budget” with “Mina compares the two approved cost tables.”
  3. Add the agreed due date, timezone, delivery location, and reviewer only when they were actually confirmed.
  4. Move your own actions into the trusted task list with a link to the shared record or source material.
  5. Put appointments and date-specific checks on the calendar; do not use the inbox or meeting document as the only reminder.
  6. Place the shared recap in the agreed project location and send or publish it only if that is part of your role.

Use a recap that invites correction

A compact recap can use four blocks: Decisions; Actions with owner and due date; Open questions or blockers; Next check. Link to the supporting document rather than retelling the whole discussion.

If you are authorized to circulate the recap, state how corrections should be made and by when. Silence is not always agreement, so do not invent a rule that an uncorrected recap automatically becomes approved. Use the team's actual decision and records process.

Research and professional guidance on meetings commonly emphasize summarizing decisions, assigning action items, expected completion dates, and explicit follow-up. The exact format is less important than whether the group can detect a wrong owner, missing action, or ambiguous date before work drifts.

When an owner or date is missing

  • No owner: record “owner not assigned” and return it to the person with authority to assign work.
  • Several owners: identify one coordinating owner or state each person's distinct output; do not assume shared ownership will coordinate itself.
  • No due date: record the next decision or check date rather than guessing a deadline.
  • Blocked action: name the decision, access, information, or capacity required and who can provide it.
  • Conflicting commitments: ask which consequence takes priority instead of compressing both plans silently.

Treat transcripts and AI recaps as drafts

A transcript can preserve more language while still mishearing names, numbers, technical terms, or speakers. Research on AI meeting recaps also reports that systems can miss personally relevant details and that misattributed action items can damage group dynamics.

Verify decisions, owners, dates, and high-consequence details against authorized sources and the people involved. Never upload confidential meeting content to an unapproved AI service. Recording, transcription, monitoring, consent, and retention rules differ by workplace and jurisdiction, so obtain the required permission before recording or processing a meeting.

Possible workplace supports

Depending on the role and local rules, advance agendas, written instructions, shared notes, reduced distractions, a designated note-taker, permission to record, or structured follow-up may be considered. Supports should match the person's actual difficulty and the work requirements. Accommodation rights and processes differ, so use local official guidance or qualified advice.

For the next ordinary meeting, prepare five empty lines before it begins: decision, owner, next action, due date, and next check. Afterward, spend five minutes moving each real commitment to its proper task, calendar, or project system.

Sources and further reading

Sources support the health and diagnostic context. Practical workflow suggestions are low-risk editorial adaptations, not clinical treatment.