What the Empty Field Asks You

In 1882, Friedrich Nietzsche — his eyesight failing badly enough that handwriting had become painful — purchased a Rasmus Malling-Hansen Writing Ball, a typewriter shaped like a brass hedgehog, with fifty-two keys arrayed across a hemisphere. He used it for six weeks before setting it aside. In those weeks, something happened to his prose. His friend Heinrich Köselitz noticed: the sentences were shorter, more telegraphic. The German media scholar Friedrich Kittler later described the change precisely — Nietzsche's writing had moved "from arguments to aphorisms, from thoughts to puns, from rhetoric to telegram style."

Nietzsche understood what had happened. He wrote, in a note: "Our writing utensils also help shape our thoughts."

Most people encounter this anecdote and take from it something vague about technology and cognition. I think the more specific lesson is about fields — about what the blank space in front of you asks you to fill in.

The blank page asks for anything

That's its virtue and its failure. When you open a new note in Bear or Obsidian or Apple Notes, the cursor blinks in a rectangle that will accept a grocery list, a half-formed thought, a decision you made last Tuesday, or the name of someone you need to call. All of it, with equal neutrality, organized by nothing, distinguishing nothing. The note format is so generic it's essentially asking: "got something?"

That is not the same as asking: "when did you last speak with this person?" Or: "what alternatives did you consider?" Or: "what do you prefer when this situation comes up?"

A blank field with a label is a different object. It's a question that was written before you arrived.

The form creates the noticing

When you have a person record with fields for how you know someone, what you've worked on together, and a last-contact date, something happens before you fill it in. You start noticing those things about the people you meet. Not because you've become more attentive. Because the form told you those things were worth noticing.

Michael Nygard figured this out for software architecture in 2011 with Architecture Decision Records. An ADR is a short document with fixed fields: context, alternatives considered, decision, consequences. Engineers who adopt ADRs consistently report not that their documentation improved, but that their decisions improved. The form created a pause — a moment of structured attention that the blank page never demanded. Knowing you'll need to fill in "alternatives considered" changes whether you consider alternatives at all.

The same thing happens with typed entities in a knowledge base.

Harbor stores people as first-class records, not as notes that mention someone's name. A person record has fields for context: how you know them, what you've worked on, what they care about. There's a field for last contact. These fields start mostly empty. But empty fields are not neutral — they're questions. "When did you last talk to this person?" is a different prompt than "write something about this person." The second is open. The first is specific, slightly uncomfortable, and harder to avoid.

I've found that a person record with an empty last-contact field motivates follow-up better than any reminder system I've tried. Not because the software nags me. Because the empty field is a visible gap. The schema makes incompleteness observable. A blob of text can't be incomplete — it just has more or less text. A typed record with a blank labeled field is asking something specific.

This is also why the generic note eventually fails as a knowledge system. Not because it stores things badly, but because it asks nothing of you at capture time. It accepts everything without comment, which means it makes no claim about what's worth noticing. Over time, a collection of undifferentiated notes becomes an archive organized by when things arrived, not by what they are.

The schema is a bet

Here's the uncomfortable implication: a useful knowledge system requires a theory of what kinds of things are worth knowing. You have to decide, before you encounter information, that people are a category worth tracking differently from tasks, which are worth tracking differently from decisions. Most tools avoid this. They give you the generic note and let you build the taxonomy yourself. The result is that most people construct a personal taxonomy from scratch, abandon it after six months, and start again.

Typed records are a commitment. They say: these kinds of things are different enough from each other that they deserve different shapes. The shape is the claim. And the claim turns out to matter, because the field is what creates the noticing.

Nietzsche's writing ball was a poor capture tool — six weeks and then abandoned. But his observation about it was right. The instrument shapes the thought. Not by constraining it, but by asking it something specific.

Every interface is a question. The blank page just asks the laziest one.

---

Asgeir Albretsen is the founder of Harbor.