The Card Is the Constraint

I've tried every note system there is. Folders, tags, the PARA method, the Bullet Journal, Obsidian graphs that look like a nervous system. Some lasted a month. Some lasted a year. None of them changed how I thought.

Then I heard about a system called Object Pages — Joan Westenberg's idea that every note deserves its own page. One idea. One page. A header with the note type and date. A footer with status, two tags, and any connections. Nothing else.

I didn't switch to paper. But I finally understood what I'd been doing wrong with the digital tools I'd been bouncing between. The problem was never the app. The problem was that I'd been cramming five thoughts onto a single page and hoping the structure would sort itself out.

The constraint is the feature

There's a reason a single idea per page works. It's the same reason a haiku is easier to write than a novel. The constraint forces you to pick the one thought that matters, and the white space around it makes that thought load-bearing.

Most note systems let you keep going. Add another bullet. Add another tag. Add another folder. You end up with a wall of text that looks productive but doesn't tell you anything you didn't already know. A page with one idea and a footer that says 'status: active' and 'tags: project, planning' tells you the moment you open it what this note is, when you wrote it, and what to do with it. That's it. You don't have to decode it.

What I copied (and what I changed)

Object Pages is built for paper. Six note types — task, idea, reflection, list, connection, decision. A simple header and footer. The system has a charm to it, and if you love fountain pens and notebooks it probably fits you the way it fits its creator.

I'm a digital person. I don't want to scan pages or manage stacks of notebooks. So I took the principle — one idea per note, header and footer for metadata — and applied it inside NoteDex. Every card in NoteDex is one object. Title at the top, the thought in the middle, tags and status at the bottom. That's the whole shape.

The thing I didn't expect: I started writing fewer notes. When each note is its own card, you stop writing notes you don't mean. The friction of creating a new card is just enough to make you ask 'is this a thought, or is this a passing feeling?' Most of the time it's the second one. You close the app and move on.

Why most digital note systems fail at this

Most apps are designed around documents. A document can be anything. A document can be two sentences. A document can be a 4,000-word essay. The app doesn't care. So you write 4,000 words of notes that you'll never read again, because the page was already open and you were already typing.

Object Pages — and any system that gives each idea its own space — flips that around. The page is the constraint. The card is the constraint. You can't fit a project plan and a passing observation on the same card, so you don't try. You make two cards. Each one does one thing. Each one is findable later, because the metadata told you what it was when you wrote it.

The other thing most apps get wrong is connections. They either give you no way to link notes, or they give you a graph view that looks impressive but doesn't help you find anything. Object Pages limits you to a small 'connections' field in the footer. Two or three links, max. That's enough. More than that and you're back to managing the map instead of walking the territory.

What changes when you give an idea its own space

Three things, in my experience.

First, you start finishing thoughts. A card with one idea is small enough to complete in one sitting. You don't open a page intending to write a paragraph and end up with a half-formed thought you'll never come back to.

Second, you read your old notes. A wall of text is intimidating. A card with a clear title and a status tag is approachable. You scroll through your archive and actually pick up the thread instead of skipping it.

Third, you make connections you didn't expect. When every note is its own thing, you stop thinking of them as chapters in a book. You start thinking of them as objects you can pick up and put next to other objects. The note you wrote three months ago about a meeting becomes the seed for a new project plan. The decision you captured last week is the answer to a question you had today. The system surfaces these because the notes are small enough to move around.

The minimalist trap

There's a version of this advice that goes too far. 'Write one sentence per note.' 'Don't use tags.' 'The best system is no system.' I've tried that. It doesn't work for me. Some ideas need a paragraph. Some projects need five cards to capture. The point isn't minimalism, it's clarity.

The point is: every note earns its own space because the alternative — a single document full of unrelated thoughts — is the same as having no system at all.

Object Pages got this right. One idea per page. Enough structure to find the note later. Not so much structure that managing the system becomes a job.

The system that does the work for you

Here's what I like about the one-card-per-idea approach. It pushes the work onto the system, not onto me. When I open a card, I see the date, the type, the status, the tags. I don't have to remember what this note was about. I don't have to re-read three paragraphs to figure out where I left off. The card tells me.

That's the real point. A good note system is one where the structure does half the work. You write the thought. The system handles the rest. Object Pages does this on paper. NoteDex does it on a screen. The medium doesn't matter. The shape does.

If your current system feels like it's fighting you, the fix might not be a new app. It might be a smaller container. One idea. One card. The constraint does the rest.