Skip to main content

Note-taking method

Best Atomic Notes for Project Managers

One idea per note, linked to others through context. For project managers, the working week is decisions buried in Slack threads, email chains, and meeting notes. The rest of this page is the method, cut for that week.

By tentus team · Updated 2026-09-20

What Atomic Notes actually asks of you

A note holds exactly one idea, written so that someone who never saw it could understand it alone.

Titles are claims, not topics — "Retrieval beats re-reading", not "Learning". If a note needs its neighbors to make sense, it is two notes, not one.

How project managers put it to work

  1. 1

    Decisions captured in the flow

    Decisions made in meetings and Slack threads get captured where they happened, with the date and who made them. The status report stops being detective work.

  2. 2

    Dependencies you can actually see

    A decision that blocks another team is linked to the thing it blocks. When the date slips, the blast radius is known before the standup, not discovered during it.

  3. 3

    Status assembled from evidence

    The weekly status is written from what the record shows — what was decided, what shipped, what stalled — not from your recollection of a loud week. Evidence makes the bad news deliverable early.

The capture habit, the linking, and the retrieval are the parts tentus automates — atomic notes without the daily upkeep.

Try it with tentus

tentus makes Atomic Notes practical for project managers. Capture, link, and retrieve without the busywork.

Other methods worth trying

Atomic Notes for other roles