What Leaders/Managers Can Learn from How to Take Smart Notes
Derek managed a twenty-person operations team and took thorough notes in every one-on-one, every skip-level, every leadership offsite. His notebook was full: dates, names, action items underlined twice. When his VP asked him to build the case for restructuring his team ahead of next year's budget, Derek pulled out eight months of notebooks and started reading. What he found was a diary of individual meetings, each self-contained, none pointing to the others. He could see that three different people had mentioned burnout in three different months, but nothing in his notes connected those three mentions into a pattern he could name. He spent a weekend re-reading everything by hand to reconstruct an argument his own notes should have already made for him. The restructuring proposal went in a week late, thinner than it should have been, and his VP asked why he hadn't flagged the burnout trend sooner.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Turn meeting notes into your own read of the situation
Instead of transcribing what was said in a one-on-one, pause afterward and write one or two sentences capturing what you now believe about that person or that project, in your own words. A transcript records the conversation; your own sentence records your judgment, which is what you'll actually need later.
Derek recorded action items verbatim in every meeting but never once wrote down what he personally concluded from them, so his notebook had a record of tasks and no record of his own evolving read on the team.
After each one-on-one, write a single sentence starting with "What I now think is..." before moving to the next task on your list.
Link what one person says to what another one meant
A comment from one report about workload becomes meaningful once you connect it to a similar comment from someone else, or to your own earlier note about a project timeline. Patterns across people are invisible until the individual notes are deliberately tied together.
Derek's notebook had a separate section for each direct report, so three burnout mentions sat in three different sections for months without ever being read side by side.
Once a week, scan your recent notes across all your reports and ask which two, if any, are describing the same underlying issue.
Let team themes emerge instead of pre-sorting by meeting type
Don't file every note under a rigid template of "performance," "morale," "projects" decided before you knew what themes would actually recur on your team. Let recurring notes cluster naturally, and name the category once the pattern is undeniable.
Derek's meeting template forced every note into one of four fixed boxes, so a cross-cutting issue like the burnout pattern never had a box of its own and stayed invisible in all four.
Leave new notes untagged for a week, then look for which ones keep coming up together before you name a category for them.
Let your notes make the case before you're asked to
A leader who keeps linked notes over time has, without extra effort, the beginnings of every argument they'll eventually need to make: for a promotion, a reorg, a budget request. The pattern that would take a weekend to reconstruct from scratch is instead something you noticed as it was forming, months before anyone asked you to defend it.
Writing your own read of a conversation takes a private moment right after a meeting, while linking that note to others takes a step back you're tempted to postpone when your calendar is full. Favor the immediate one-sentence capture every time, since an unwritten judgment disappears entirely, but block fifteen protected minutes weekly for linking, since patterns across people only appear when notes are actually placed next to each other.
Name one thing, honestly
What pattern among your team's conversations have you already half-noticed but never actually written down and connected?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Leave new notes untagged for a week, then look for which ones keep coming up together before you name a category for them.