Skip to main content

Note-taking method

Best Atomic Notes for Designers

One idea per note, linked to others through context. For designers, the working week is scattered moodboards, design critiques, and research that never gets referenced again. 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 designers put it to work

  1. 1

    Critique with its context

    Feedback lands captured next to the frame it refers to — including the feedback that contradicted last week's. Design rationale lives in the record, not in the designer's memory of the meeting.

  2. 2

    A pattern shelf, not a moodboard pile

    Inspiration is stored by the problem it solved — empty states, pricing pages, onboarding — so the shelf answers a brief, not just a vibe. Sources stay attached for when the client asks where it came from.

  3. 3

    The dropped-direction log

    When a direction dies, the reason is captured next to the work. Six months later, when someone suggests the same direction, the link answers before the meeting does.

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 designers. Capture, link, and retrieve without the busywork.

Other methods worth trying

Atomic Notes for other roles