Capture agreements, decisions, and actions without writing a transcript nobody will use.
Created by the First Role Skills Editorial Team. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
A realistic scenario
A 25-minute project meeting covers a launch date, two blockers, and four tasks. Your notes must help someone who could not attend.
DeliverableA one-page record with decisions, named actions, due dates, and unanswered questions.
Three beginner mistakes
- Writing every sentence instead of outcomes
- Listing tasks without owners or dates
- Mixing decisions with ideas that were only discussed
Complete it in six controlled steps
Prepare the frame
Before the meeting, add title, date, purpose, attendees, and three sections: Agreements, Decisions, and Actions. This is the ADA frame.
Capture evidence, not dialogue
Record the reason behind a decision only when it will matter later. Paraphrase accurately and mark uncertainty instead of guessing.
Write decisions as complete statements
Use ‘The team decided to…’ and include scope or conditions. A topic heading is not a decision.
Turn verbs into owned actions
Every action needs a deliverable, one accountable owner, and a due date or review point. Separate collaborators from the accountable owner.
Read back critical items
Before the meeting ends, confirm high-impact decisions, owners, and deadlines aloud. Correct misunderstandings while everyone is present.
Publish a short follow-up
Send the notes to the agreed location, link supporting documents, highlight unresolved questions, and update the record when an action changes.
Before and after
Before:
Launch discussion. Sam mentioned copy. We talked about Friday. Need to check legal and analytics.
After:
Decision: move launch review to Friday 10:00 UTC.
Action: Sam delivers final copy by Thursday 15:00 UTC.
Open question: Legal approval owner to be confirmed today.
Complete the exercise
Convert the rough notes in the template into ADA format. Do not invent owners. Mark missing ownership as an open question, then compare with the completed example.
Download the meeting-minutes template — An editable ADA template plus a completed fictional example. — Download file
Use only fictional or fully anonymized data. Never upload an employer’s confidential information to a portfolio.
Turn the exercise into credible evidence
Show the rough notes and final ADA record side by side. Highlight one agreement, one decision, one owned action, and one unresolved question. Explain why an unassigned item stayed visible instead of receiving a guessed owner. A reviewer should be able to understand the meeting outcome without attending it and trace every action to a person and an unambiguous review date.
Check your own work
- Purpose recorded
- Decisions are explicit
- Actions have owners
- Dates are unambiguous
- Open questions visible
Primary reference: Atlassian Team Playbook: Page-Led Meetings
Why this matters in your first job
New employees are often asked to take notes in meetings. It can feel like a minor task, but good notes make you visible and valuable: they become the record of what was decided and who is doing what. Managers notice when notes are clear, sent quickly and lead to action, and the habit trains you to focus on decisions rather than discussion.
Common questions
Should I write down everything people say? No. Capture decisions, action items with owners and deadlines, and open questions. Detailed transcripts are rarely read.
When should notes be shared? Ideally within a few hours, while the meeting is fresh. Send them to everyone who attended and anyone who owns an action.
What if I am also participating in the discussion? Ask someone else to share note-taking, or keep a simple template open and fill in actions as they are agreed. Our guides to running a short, useful meeting and writing a status update use the same principles.