If your meeting notes don't separate "Decisions" from "Discussion," you are creating work, not resolving it.
We've all been there. You attend a 45-minute meeting. You take two pages of diligent notes. You email them to the team. A week later, the deadline passes, and someone asks, "Wait, who was doing that?"
The problem isn't your team's memory. The problem is that standard meeting notes are linear transcripts. They mix conversation with conclusions, burying the critical "next steps" inside paragraphs of chatter.
Cognitive Ladder Notation (CLN) forces a separation of concerns. In a CLN meeting note, the Operator Column tells you instantly: Is this a Fact? A Task? A Blocker?
The "Protocol" Mindset
Think of meeting notes not as a diary, but as a log file. A log file is useless if it's messy. It needs a schema. CLN provides that schema.
Decision (=)
The most important output. A binary state: we decided X. This goes under the
= operator.
Action (.)
A commitment to do work. Must always have an Owner (@). If it has no
owner, it's not an action.
Blocker (!)
Something stopping progress. Use ! to highlight risks so they aren't
lost in the "parking lot".
The CLN Meeting Template
Copy this structure into your next meeting document. It works in Notion, Obsidian, Google Docs, or a plain text file.
TEMPLATE MEETING: [Topic/Project Name] date: YYYY-MM-DD attendees: [List] AGENDA . Review [Topic A] . Decide on [Topic B] DECISIONS = DECISION: [What was agreed] * context: Why we chose this path ACTION ITEMS . ACTION: [Specific task description] owner: [Name] due: [Date] BLOCKERS & RISKS ! RISK: [Potential issue] mitigation: [Plan to handle] OPEN QUESTIONS ? QUESTION: [Unresolved item]
Real World Example: Sprint Planning
Here is how a messy discussion about a "Release Date" transforms into a clear CLN artifact.
EXAMPLE MEETING: Q1 Sprint Planning date: 2026-02-17 team: Backend, Product DECISIONS = DECISION: Release date moved to March 15th * reason: QA needs more time for regression testing = DECISION: Feature X is cut from scope ACTION ITEMS . Update Jira roadmap with new dates owner: Sarah due: 2026-02-18 . Send update email to stakeholders owner: Mike . Hire contract QA tester owner: HR Dept BLOCKERS ! BLOCKER: API keys for staging environment are expired owner: DevOps . Action: Rotate keys by EOD ? OPEN: Do we need to re-sign the contract with the cloud provider?
The Scannability Test
Look at the example above. Can you find every owner in 5 seconds? Yes (scan for
@). Can you find every risk in 5 seconds? Yes (scan for
!).
This is impossible with standard paragraphs.
Conclusion
Meeting notes are not a record of what was said. They are a map of what happens next. By using CLN, you turn a chaotic conversation into a structured database of tasks and decisions.