The Tools I Use to Organize Research Ideas

Most clinicians store research ideas the same way: a note in their phone, a half-filled Word document, an email they sent to themselves. The idea lives somewhere—but when it’s time to actually develop it, finding it is a separate problem, and connecting it to related ideas is nearly impossible.

This is where Notion for research and Obsidian have built real followings among academics. Not because they’re sophisticated, but because they solve a specific failure mode: the idea graveyard.

This post explains how I choose between them, how I use my setup as a clinician-researcher, and what actually matters when you’re picking a system.

Why Word and Google Drive Don’t Work for Ideas

The instinct to open a Word document when an idea strikes is understandable. But Word is a document tool—it’s designed to produce a finished, linear output. Research ideas are the opposite of linear: they branch, connect, stall, and revive.

Drive folders compound the problem. You end up with nested folders that made sense when you created them and make no sense six months later. Searching across documents is slow. There’s no way to link a literature note to a half-formed hypothesis to a methodological concern. Everything exists in isolation.

The result is not just disorganization. It’s that ideas stay shallow. You can’t build on something you can’t find and can’t connect.

Notion for Research: What It Actually Gives You

Notion works as a structured database. You can build a table of research ideas with properties: status (raw idea / developing / shelved), specialty, related papers, feasibility score. Each row opens into a full page where you can write freely.

What this means in practice: you can filter all your pediatric surgery ideas by status, open any one, and see everything you’ve ever noted about it in one place. You can create a linked database of papers that connects to the ideas they informed. The relationship between your thinking and the literature becomes visible.

Notion also handles collaboration well. If you’re working with a co-investigator or a research coordinator, sharing a workspace is straightforward. Permissions are granular. Comments work. This matters more than it sounds when a study has four people contributing to the protocol.

The trade-off is that Notion runs in the cloud. Your data is on their servers. For most academic work this is a non-issue—but it’s worth knowing if your institution has specific data handling policies for research materials. Also, Notion can get slow with large databases, and the interface rewards people who enjoy building systems. If you just want to capture and retrieve, it can feel like too much.

As a tool for organizing AI-assisted research workflows, Notion pairs well because you can store prompts, outputs, and notes together in structured tables rather than scattered files.

Obsidian for Academics: The Case for Local and Linked

Obsidian is built around plain markdown files stored locally on your machine. There’s no cloud dependency, no database structure—just files that link to each other using [[wikilinks]].

The core insight behind Obsidian is that thinking happens through connection. When you write a note about a paper, you link it to your note on the method it used, which links to your note on a clinical question you’re trying to answer. Over time, you build a network of connected ideas rather than a folder of isolated documents.

For researchers whose work spans years and multiple projects, this compounds in useful ways. A note you wrote two years ago about heterogeneity in meta-analysis surfaces naturally when you’re writing a new protocol because it’s linked to your notes on study design. Word documents don’t do this.

Obsidian also has a strong plugin ecosystem: Zotero integration so literature notes pull metadata automatically, spaced repetition for learning, templates for consistent note structure. The graph view—a visual map of how your notes connect—isn’t just aesthetic. It occasionally surfaces unexpected relationships between ideas.

The trade-off: Obsidian has a steeper setup curve. You make more decisions upfront about folder structure (or non-structure), naming conventions, and which plugins to use. It also doesn’t handle databases the way Notion does—if you want to filter ideas by status, you’ll be doing that with tags or folder conventions rather than proper properties.

How I Actually Use This as a Clinician

My setup is Notion for project-level organization and Obsidian for literature notes and developing ideas.

Notion holds the overview: active studies, their status, key dates, collaborators, protocol links. It’s the dashboard I share with co-investigators. When a new project moves from idea to actual data collection, it lives in Notion.

Obsidian is where I think. When I read a paper, I write a note in Obsidian: what the study did, what I found interesting or methodologically weak, what clinical question it connects to. When a research idea starts forming, I draft it here—linking it to the relevant literature notes, the relevant methodological concerns, the relevant clinical context.

Knowing what makes a research question worth developing helps you know what kind of notes to keep. You’re not archiving everything—you’re building a system that makes the right connections visible.

For literature review specifically, I use SciSpace to find and read papers efficiently before bringing the key insights into Obsidian notes. The combination—AI-assisted discovery, human-written notes—is faster than either alone.

The Decision Framework

If you’re trying to decide which to use:

Choose Notion if:
– You need to share your system with collaborators
– You have multiple projects running in parallel and need a project-level overview
– You prefer structured databases over free-form linking
– You want a visual, familiar interface with low setup overhead

Choose Obsidian if:
– Your primary use is developing and connecting ideas over time
– You process a lot of literature and want permanent, linked notes
– You want full control over your data (local files)
– You’re comfortable with some initial setup

Both options are meaningfully better than Word for this purpose. The choice matters less than the habit: consistently capturing ideas, consistently revisiting them, and consistently connecting them to what you’re reading.

What the Tool Can’t Do

No note-taking system turns a weak research question into a strong one. A well-organized idea graveyard is still a graveyard.

Academic writing is a system, not a skill—and the same is true of research development. The organizational tool is infrastructure. The thinking still happens when you sit with a question long enough to understand why it matters, whether it’s answerable with the resources you have, and what a publishable answer would actually look like.

The best use of Notion or Obsidian is not to capture everything. It’s to build a system that makes your better ideas easier to find and develop, and lets your weaker ideas quietly die instead of cluttering your thinking.

Starting Without Overcomplicating It

The mistake most people make is building the system before they know what they need it for. Start small: a Notion table with five fields, or an Obsidian vault with a single folder and no plugins. Use it for one month. The friction points will tell you what to add.

Your research output is the goal. The tool is in service of that—not the other way around.

---

Want a stage-by-stage system from idea to submission? Get the Checklist → — Stage-by-stage checklist from research idea to journal submission. ($5)