Jot is not a note app, and the refusal is the product

There is a well-worn path for a tool like this.

It starts as a box you can summon with a keystroke. Someone asks for formatting, so it gets bold. Someone asks to keep related notes together, so it gets folders. Then tags, then backlinks, then a graph view, then templates, then a database view of the templates. Four years later it is a knowledge management platform with a quick-capture feature, and the quick-capture feature is a modal inside a window that takes 900 milliseconds to open.

Nobody made a bad decision. Every individual request was reasonable and came from a real user. The tool simply drifted, one sensible feature at a time, into being something else — and the people who came for the keystroke left without filing a complaint, because they had nothing specific to complain about.

The only defence against this is to write down, in advance, who the product is not for, and then treat that document as binding.

The three problems, and the two Jot ignores

Personal information management is three separate problems:

1. Capture. Getting a thought out of your head before it decays.
2. Organisation. Putting it somewhere it will be found again.
3. Retrieval. Finding it at the moment it is useful.

Almost every tool in this space is built around the second one, because organisation is where the interesting product surface lives. It is where you can put folders and views and filters and a sidebar. It is what demos well.

Capture, by contrast, has almost no surface. Done properly it is a text field that appears and disappears. There is nothing to show in a screenshot, no feature grid to build, and no obvious way to make it look like more work than it is.

Which is precisely why it stays broken. The bottleneck in most people’s system is not that their notes are badly organised. It is that the thought never got written down at all, because writing it down cost twelve seconds and a context switch at a moment when they had neither.

Jot solves the first problem and deliberately hands the other two to somebody else — Microsoft To Do, mostly, which is already installed, already on your phone, already in Outlook, and already the place your reminders come from.

The anti-persona

The person Jot is not for is easy to describe, and describing them is more useful than describing the target user, because the target user is just “someone who has thoughts while busy”.

The person who wants an editor. Someone who intends to write a paragraph, or a page, or a structured document. Jot’s input is a single growing text field with no formatting. If you want to write, write somewhere with a scrollbar.

The person who wants a knowledge base. Someone building a system: a vault, a second brain, a linked graph of everything they have ever read. That is a real and worthwhile thing, and there are good tools for it. Jot has no links, no backlinks, no graph, and no plans for any.

The person who wants transcription. Meeting recorders, voice notes, “just capture everything and sort it out later”. Capturing everything is not the same problem as capturing the one thing you decided mattered. The second one requires a decision, and the decision is the valuable part.

The person who wants their notes in the cloud, accessible everywhere, searchable from a browser. Jot’s captures are a file on one machine. That is a feature for some people and a dealbreaker for others, and the second group should find out on the website rather than after installing.

What the refusal buys

Saying no to those four is not modesty. It is the only reason the rest of the design is possible.

The overlay can be a single text field, which is why it can be summoned and dismissed without a layout pass, and why it never asks a follow-up question. If it had formatting, it would need a toolbar. If it had folders, it would need a picker. Every one of those is a decision presented to somebody who is mid-call and has four seconds.

Storage can be one SQLite file, which is why the whole app has no account system, no sync server and no privacy policy longer than a page. A knowledge base wants to be everywhere, and everywhere means a server, and a server means an account, and an account means an email address, a password reset flow, a breach surface, and a subscription that pays for the machine.

The product can end. There is a version of Jot that is finished — hotkey, parsing, reminders, a bridge into To Do, search over everything you ever typed — after which the correct number of new features is close to zero. That is only possible because the boundary was drawn first.

The one place this gets tested

Jot has AI features. They are the exact point where the boundary is most likely to erode, so the rule around them is narrow and written down: the AI suggests, and the user confirms. Nothing is ever filed automatically.

Not “usually”. Not “unless confidence is high”. Nothing.

The moment a capture tool starts deciding where your thoughts go, it has become a system you have to audit, and auditing it costs more attention than filing them yourself would have. The suggestion is offered, it is visible, and it does nothing until you accept it.

The other half of that rule is that Jot has no AI service and no API key of its own. You bring a key, the text goes from your machine to that provider, and the feature is free — because there is nothing for Jot to charge for. It exists because it is occasionally useful to split a hurried run-on line into three todos, not because a product is expected to have AI in it.

Say the boundary out loud

The front page of this site has a section headed Not a note app, with two columns: what it is, and what it will never be. That is not a modesty pose. It is there for two reasons.

The first is that it saves the wrong person an install. Someone looking for a vault should read that column, decide Jot is not it, and go and be happy with something else. A user who leaves in week two costs more than one who never arrives.

The second is that it is load-bearing. Once “never a knowledge base” is printed on the front page, adding a graph view means editing the front page, and that is a conversation someone has to have out loud. The scope creep that kills tools like this is never a decision. It is a series of small yeses, none of which felt like a change of direction.

This one has to be argued for in public.

Jot is a quick-capture app for Windows: one hotkey, one line, back to what you were doing. What it is, or what is still unproven.