The Bullet Journal Method
Leaders & Managers
DropRegion · Lessons from The Bullet Journal Method · Ryder Carroll

What Leaders/Managers Can Learn from The Bullet Journal Method

Marcus managed nine people across two time zones using a shared project tool for team work, a private notebook for his own thoughts, and a running string of direct messages for anything urgent. He believed the project tool showed him everything, so he rarely looked anywhere else, until a direct report mentioned in a one-on-one that she had flagged a staffing risk three weeks earlier in a message Marcus had since scrolled past. He had reviewed the project board every morning and felt fully on top of his team's work, yet the one thing that actually needed his judgment had never made it into any list he trusted enough to revisit. The risk became a missed deadline, and Marcus realized his morning ritual had been reviewing tasks, not reviewing what mattered.

01 · The Book in One Minute

The whole book, compressed

01Writing Down What Your Team
02The Weekly Pass That Separates
03Giving Each Project And Each
04What A Manager's Recurring List

This edition works through 4 core lessons — take them one at a time, not all at once.

02 · Where Are You Now?

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.

Your task list is really two lists tangled together, your own deliverables and everything your team surfaces to you, and treating them identically buries the decisions only you can make.
Reviews for you are not private reflection alone; what you decide to carry forward often becomes someone else's assignment, so vague entries cost other people time.
You are interrupted constantly by direct reports, which makes quick capture more valuable to you than to someone with an uninterrupted schedule.
Your team's work is naturally organized by project or person, so a single undifferentiated feed hides which initiatives are actually stalling.
Patterns in what keeps recurring on your list often point to a structural problem on the team, not just a personal productivity gap.

0 of 5 selected

03 · Core Lessons

The core lessons, applied to you

Writing Down What Your Team

Writing down what your team tells you before it disappears

The idea

A one-on-one, a hallway comment, a message flagged as urgent: each can carry a real signal, but only if you capture it in the moment rather than trusting yourself to remember it later. A brief line written down immediately turns a passing remark into something you can act on.

What it looks like

Marcus's habit was to nod during one-on-ones and mentally file concerns for later, so anything not written down competed with everything else in his head and usually lost.

Try this

Keep a running log open during every one-on-one and write one line for anything a report raises that needs your judgment, even if it seems minor.

The Weekly Pass That Separates

The weekly pass that separates real risk from routine noise

The idea

A regular review lets you look back over everything captured, from your own deliverables to what your team surfaced, and decide deliberately what deserves to move forward into next week. What you do not carry forward should be a conscious call, not an accident of forgetting.

What it looks like

Marcus's review consisted of scrolling the project board, which showed assigned tasks but never the offhand concern his report had raised, so it was never re-examined until it had already become a crisis.

Try this

Once a week, read your full running log start to finish and only rewrite forward the entries you can explain the importance of out loud.

Giving Each Project And Each

Giving each project and each report their own list

The idea

Mixing every team member's updates and every project's status into one daily feed makes it nearly impossible to see which threads are healthy and which are quietly drifting. A dedicated list per project, and one per direct report, keeps related entries visible together.

What it looks like

Marcus's staffing risk was buried three days deep in a general log by the time he reread it, mixed in among lunch plans and a scheduling note.

Try this

Start a dedicated list for each direct report and log every concern, commitment, and follow-up there instead of in your general daily entries.

What A Manager's Recurring List

What a manager's recurring list reveals about the team

The idea

The task you keep carrying forward without ever finishing is rarely about your own discipline; more often it flags a dependency, an unclear owner, or a decision waiting on someone above you. Reading your list over several weeks with that lens turns a personal record into a management diagnostic, showing you where the team's real friction sits well before it shows up in a status report or a missed deadline.

When the clusters compete

Quick capture during a busy day and dedicated lists per project can pull in opposite directions: sorting an entry correctly in the moment slows down the conversation you are trying to stay present for. Capture fast into one general log during the day, then move entries into their proper project or report list during your weekly review rather than trying to file everything as it happens.

04 · Choose Your Priority

Name one thing, honestly

Which task on your list right now would you actually delegate if you paused to write down exactly what it requires?


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.

05 · Put It Into Practice

The practices from this edition

Keep a running log open during every one-on-one and write one line for anything a report raises that needs your judgment, even if it seems minor.
Once a week, read your full running log start to finish and only rewrite forward the entries you can explain the importance of out loud.
Start a dedicated list for each direct report and log every concern, commitment, and follow-up there instead of in your general daily entries.

0 of 3 selected

06 · Small Experiment

Run this for seven days

Start a dedicated list for each direct report and log every concern, commitment, and follow-up there instead of in your general daily entries.

07 · Remember This
If you remember only 4 things
01Writing Down What Your Team. A one-on-one, a hallway comment, a message flagged as urgent: each can carry a real signal, but only if you capture it in the moment rather than trusting yourself to remember it later.
02The Weekly Pass That Separates. A regular review lets you look back over everything captured, from your own deliverables to what your team surfaced, and decide deliberately what deserves to move forward into next week.
03Giving Each Project And Each. Mixing every team member's updates and every project's status into one daily feed makes it nearly impossible to see which threads are healthy and which are quietly drifting.
04What A Manager's Recurring List. The task you keep carrying forward without ever finishing is rarely about your own discipline; more often it flags a dependency, an unclear owner, or a decision waiting on someone above you.
08 · Your Next Step

What will you do differently because you read this?

Managers looking for the fuller method behind this habit of capture and deliberate review can turn to Ryder Carroll's The Bullet Journal Method.