My Notion Setup for Medical School (Screenshots Included)

Medical school organization advice usually falls into two camps: the color-coded spreadsheet crowd and the "just use your phone calendar" crowd. I tried both. Neither worked for me the way Notion did, once I built the right system.

What I want to share isn't a generic Notion tutorial. It's the specific architecture I ran through pre-clinical years — what each component does, why it's structured that way, and how it connects to the broader study pipeline that helped me get through M1 and M2 without falling apart.

The Core: Three-Column Kanban Per Block

Pre-clinical medical school is organized into course blocks — typically weeks-long units covering a body system or integrated content area. My Notion setup mirrored this structure exactly: one Kanban board per block.

Each board had three columns: To-Do, In Progress, and Done. That's it. No "Someday/Maybe," no "Waiting On," no elaborate status taxonomy. Three columns is enough to see where everything stands without creating overhead.

Cards in the board represented discrete study tasks, not vague goals. "Review cardiology lecture 3 and make Anki cards" is a card. "Study cardiovascular" is not. The specificity matters because vague tasks live in perpetual To-Do — you never know when they're actually done.

Moving a card to Done is a small hit of satisfaction that compounds across a semester. It sounds like gamification because it is gamification, and gamification works.

Aesthetics Are Infrastructure

This sounds like a soft claim, so let me be precise: I think the visual design of your study environment affects your willingness to open it.

Every block board in my Notion setup had an emoji — matched to the content — and a cover photo. Cardiovascular block got a dark, clean cardiac-themed cover. Neuroscience got something minimal and cool. Musculoskeletal got gear/machinery imagery.

Why does this matter? Because medical school produces a lot of aversion. Aversion to the content, aversion to the grind, aversion to sitting down and opening your tools for the seventh consecutive evening. If your tracker looks like a spreadsheet, it generates a spreadsheet-opening feeling. If it looks like something you'd actually want to engage with, the friction to open it is lower.

Lower friction means more consistent use. More consistent use means your system actually functions. This is not fluff — it's a real lever on behavior.

PDF Organization by Block

Each Kanban board linked to a corresponding Notion page that held all the PDFs and resources for that block. Lecture slides were dropped directly into Notion as embeds or stored in a linked folder — organized by lecture number and date.

The advantage of block-level organization: when you're reviewing for an exam that covers ten lectures from weeks three through five, you don't have to hunt through a semester-level dump of files. Everything for that block is in one place, and the Kanban tells you what you've actually processed versus what's still waiting.

I used Notion as the hub, not the terminal. The PDFs might live in Notion, but the active review happened elsewhere.

The Full Study Pipeline

Notion was one node in a larger pipeline, not a standalone system. Here's how the flow actually worked:

1. Lecture PDF lands in Notion under the current block — organized, tagged, ready.
2. Notability for annotation — I'd pull the PDF into Notability on the iPad for handwritten notes and markup during lecture or first pass review. The Notion task for that lecture moved from To-Do to In Progress.
3. Anki card creation — After Notability review, high-yield points and anything I had to think about became Anki cards. This was the conversion step: passive exposure becoming active recall material.
4. Notion card moves to Done — Once a lecture had been annotated and carded, it was done. Not "done enough" — done. This distinction matters.

The pipeline means nothing accumulates invisibly. Either a lecture is in the pipeline or it isn't. Either a card has been made or it hasn't. The Kanban makes the status of every piece of content visible at a glance.

Why Aesthetic Design Reduces Burnout

I've thought about why the visual design of the system seemed to matter for my experience of burnout. My hypothesis: when your environment reflects effort and intentionality, it signals to you that you're taking your own work seriously.

Pre-clinical medical school is relentless enough that students often stop caring about the quality of their systems. They go survival mode — messy folders, disorganized notes, a to-do list that's really just a wall of anxiety. The system looks like how they feel.

A system that looks good is a small daily signal that you're still in control. That signal compounds. It's not a cure for medical school stress — nothing is — but it's a real friction reducer, and friction reducers matter when you're doing this for years.

What I'd Change

Looking back, the one thing I'd add: a weekly review. Not a long one — ten minutes every Sunday to look at what moved in the past week, what didn't move, and what needs to get on the board for next week. The Kanban is only useful if you look at it consistently. A weekly review keeps it alive.

The Notion setup I ran through pre-clinical years wasn't perfect. But it was intentional, maintained, and connected to the real workflow. In medical school, a real system beats a perfect system every time.