How to Teach CLN to Your Team

The Documentation Graveyard

Every team has one. A Confluence space nobody reads. A Notion workspace where information goes to die. Google Docs with 47 comments and no resolution. The problem isn't the tool — it's the lack of a shared notation for what kind of information each line represents.

CLN doesn't replace your tools. It gives your team a shared language for structuring thought — regardless of where that thought lives.

The 3-Week Rollout

PLAN: CLN Team Adoption
    = goal: team of 8 using CLN for meetings and decisions by Week 3

    . Week 1: Introduction
        . 15-min demo at standup (show meeting notes example)
        . share cheat card (PDF or physical)
        . ask team to try CLN for ONE meeting this week
        ! don't mandate — invite. Mandates kill adoption
        * start with just 4 operators: = . ! ?

    . Week 2: Practice
        . review Week 1 notes together (10 min in retro)
        . celebrate good examples (share in Slack)
        . introduce | @ for resource tracking and metadata
        ? who on the team naturally adopted it? make them CLN champion

    . Week 3: Standard
        . agree on team conventions (which headers, which operators)
        . create team template library (meeting, decision, postmortem)
        . add CLN section to onboarding doc

The Key Insight

You don't teach CLN as a "system." You teach it as a "shortcut." Show the team that writing ! deployment blocked by missing config is faster and clearer than writing "There's an issue with the deployment — it seems like the configuration file might be missing, which is preventing us from proceeding." The notation sells itself through speed.

Team Templates

Decision Record

DECISION: [Title]
    = context: [why this decision is needed]
    @date: YYYY-MM-DD
    @participants: [names]

    + option A advantages
    - option A disadvantages
    + option B advantages
    - option B disadvantages

    = chosen: [option]
    * rationale: [why]
    . action items
    ? review date: [when to revisit]

Postmortem

POSTMORTEM: [Incident Name]
    @date: YYYY-MM-DD
    @severity: P1/P2/P3
    @duration: X hours

    = what happened (1-2 lines)
    ! root cause
    . timeline of events
    . what we did to fix it
    + what went well in response
    - what went poorly
    . action items to prevent recurrence
        @owner: [name]
        @deadline: [date]

Adoption Metrics

Track these signals: Are meeting notes getting shorter? Are action items clearer? Are fewer decisions revisited because context was lost? If yes — CLN is working. You don't need a survey.