Why Your Health Notes System Keeps Failing (and What Actually Works)

The Setup Trap

There's a moment, right after you've watched a YouTube video about note-taking, when you believe this time will be different. You'll have a vault for every blood pressure reading, a tag for every symptom, a folder for every medication. I've been there. I once spent a whole weekend wiring up a database, installing plugins, color-coding folders. It felt like I was building a command center for my own body.

Then Monday came. I had a headache, a doctor's appointment, and no energy to log anything. The system sat there, pretty and useless.

A recent online discussion showed I'm not alone. Hundreds of people described their own abandoned workflows—elaborate setups that crumbled within weeks. The pattern is always the same: we put more effort into building the system than using it, and eventually the system becomes a second job.

Complexity Has a Cost

One person's story stuck with me. They went from OneNote to a handwriting tablet to Obsidian, hoping each step would fix the last one. The handwriting tablet felt slippery and slow. Obsidian needed constant syncing workarounds—OneDrive, then TeraCloud, then Alibaba Cloud OSS—just to keep notes accessible on their phone. The final straw? Markdown wouldn't convert to the Word and Excel formats their clinic required. So they stripped Obsidian down to a plain searchable database with one plugin for quick capture.

The point isn't that these tools are bad. It's that complexity eats time and motivation. When the overhead outweighs the benefit, you stop.

In health tracking, that's dangerous. If you're logging daily blood sugar or meds, you need something that's always there and needs zero fuss. Otherwise, you skip entries, and then you skip the whole thing.

Start Dumb, Not Smart

Another person in that thread said they now use a single text file for everything. No folders, no tags, no plugins. Just a running log they can open with any editor. Someone else swears by Apple Notes—it's native, syncs effortlessly, and handles voice memos. That's it.

This matches what health informatics folks have been saying for years: the simpler the system, the more likely you'll stick with it. Your phone's built-in notes app is already installed, already syncing, and can handle text, photos, even voice recordings. For most people, that's enough.

I'm not saying you should never upgrade. I'm saying start with the dumbest tool that works. Add structure only when you actually need it—when you find yourself wanting to see trends or connect symptoms to triggers.

Add Structure Gradually, Not All at Once

One user described starting with plain Markdown files in VSCode, then slowly adding organization as their notes grew. It was easier to maintain that way, and they could migrate to Obsidian later if they wanted. Another built a complex shortcut-based time tracker, used it religiously for six months, then retired it once the habit was formed.

For health, that might mean logging your steps in a simple file first. Then, after a few weeks, you notice patterns and think, "I want to tag which days I had headaches"—so you add a tag. Then maybe you want to correlate headaches with sleep, so you add a column. It's incremental, and each step is justified by real need.

Tools That Actually Survive

The discussion highlighted a few tools that people genuinely stick with. Apple Notes, plain text files, and simple capture apps like flomo came up repeatedly. One person mentioned a basic note app with color support and mind maps, but they bemoaned the lack of an iOS version—a reminder that platform lock-in is a real issue.

If you need more than a note, consider dedicated health trackers. They often have built-in reminders, charts, and export options. But beware of feature bloat. If logging an entry takes more than five minutes, you'll quit. I've seen people abandon apps because they required entering 15 fields for one meal. That's not tracking; that's data entry.

Don't Mistake Preparation for Progress

A recurring theme in the comments was the confusion between building a system and actually doing something. One writer put it well: "We may think mastering methodology means having ability and action, but it's the other way around. Ability and action create good methods."

This hits hard in health. You can spend weeks crafting the perfect dashboard, but if you're not exercising, eating decently, or taking your meds, that dashboard is just a pretty picture.

Start with the action. Log your daily steps. Record your blood pressure. Track your mood. Then, if you find yourself wanting to see trends, add a tool that helps with that—not before.

Design for Your Real Life

Your tracking system should fit into your life, not the other way around. If you're a parent checking things at night, like the user who set up their phone to launch a flashlight with one tap, think about convenience. If you're always on the go, a mobile-first solution might be best.

One user told a funny, honest story about a food-rating app they built. Great idea, but they stopped using it. Now they just take photos of their meals and add notes in the photo app. It's simpler, and it works.

Same for health data. If you're tracking meals, a photo might be more useful than a detailed text entry. If you're tracking workouts, a simple log of distance and time might be enough. Don't force structure where it isn't needed.

The Only Metric That Matters

There's no one-size-fits-all solution for personal health informatics. But the community wisdom is clear: simplicity wins. Start with a tool you already use. Add structure only when necessary. And remember, the goal is to support your health, not to create a beautiful system you'll abandon in a month.

So, take a hard look at your current setup. Is it helping you stay on top of your health, or is it just another thing to manage? If it's the latter, consider stripping it down. Your future self will thank you—and maybe actually use it.