Notes and wiki

What this category covers

Somewhere to put what you know: personal notes, team wikis, meeting records, research and the increasingly blurry space between a document and a database.

Products here split by audience. Personal tools optimise for speed of capture. Team tools optimise for finding something a colleague wrote last year. A few try both, and the compromise usually shows.

Customer-facing documentation belongs in docs and knowledge base. Task lists sit in task management.

Capture speed decides whether it gets used

A notes tool competes with a scrap of paper, and it loses whenever it is slower.

Measure the time from thought to written word: opening the application, finding the right place, and starting to type. Products that require choosing a location before writing lose material that would otherwise have been kept.

Mobile capture matters for the same reason. Most notes are made away from a desk, and a tool that takes eight seconds to open on a phone quietly stops being used for anything urgent.

Finding it again

Everything in this category is easy at fifty notes and difficult at five thousand.

Search quality is the whole game. Try a query with words from the middle of a document rather than its title. Check whether it searches attachments, whether results are ranked usefully, and how quickly it responds on a large archive.

Linking beats filing. Folders force one decision that is often wrong later, while links between notes let structure emerge from use. Backlinks, mentions and the ability to see what refers to a page are worth more than any hierarchy.

Tags help when they stay few. A vocabulary of two hundred tags is a second filing system with the same problem.

Structure, databases and the tempting part

Modern products blend documents with structured tables, which is powerful and easy to overdo.

• Plain pages, for anything written once and read occasionally.
• Tables and properties, when items share fields worth filtering on.
• Templates, for recurring formats such as meeting notes.
• Views, so one set of records serves several purposes.
• Embeds, which look elegant and complicate export.

The failure mode is building a system before there is anything to keep in it. Elaborate structures created in the first week are usually abandoned by the fourth. Write first, organise when the pile makes the shape obvious.

Sync, offline and where the files live

Ask three practical questions before adopting anything for real work.

Does it work without a connection, and what happens when two devices edit the same page while apart? Where is the data stored, and can you keep a local copy? What does export produce, in a format something else can read?

That last question is the important one. Plain text and markdown travel well. Proprietary blocks, linked databases and embedded views usually flatten into something unusable, which is how a decade of notes becomes a folder of confusing files.

Teams, permissions and cost

For shared use, look at permissions per space and per page, guest access for outsiders, and version history depth. Then look at what happens when somebody leaves, since notes in a personal account can walk out of the building.

Pricing is per user per month, with free personal tiers that are genuinely usable. The boundaries that push teams upward are usually version history, permissions, guests and single sign-on rather than storage. Similar patterns across other categories are set out in what pricing pages hide.

Personal tools, team tools and the awkward middle

A personal notes application is judged on capture speed and search, and almost any of them works if you write in it consistently.

A team wiki is judged on whether somebody else can find what you wrote a year ago without asking you. That needs structure, permissions, naming conventions and a habit of writing for a reader rather than for yourself.

The awkward middle is a personal tool adopted informally by a team. It works for a while, and it fails the day the person who built the structure leaves, because nothing about it was documented and half of it lived in a private space.

If notes matter to more than one person, put them somewhere the organisation owns from the beginning. Moving later is possible and rarely happens before something is lost.