I built a place to catch the thing only you know before it becomes a problem

An owner of a metal fabrication shop decided to test something a lot of operators say about their own business and never actually check: could it run for a week without him. He told his crew he was going off grid for five days. He did not make it to Wednesday. On Tuesday afternoon a customer changed specs mid-run on a job, and nobody on the floor knew how to reprice it. On Wednesday morning his office manager called about a vendor invoice that did not match the purchase order, because he had approved the change over the phone weeks earlier and never written it down. He posted the whole thing afterward, and the post is short and a little stunned: "Turns out I am the process for about half the things that happen in my shop." That sentence is the entire market for today's build, and it describes a huge number of small businesses that will never sit down and write a post about it.

So today's build is not a knowledge base. It is a ten-second habit. The Key Person Log is a capture form that lives at the top of its own page: what is something only you, or one other person, knows how to do, or a decision nobody else saw. What should someone do about it if you are not around. How urgent is it to write up properly. Hit "Log it," and the thing you almost let slide back out of your head is now a row in a growing, dated list, sitting in your own browser, ready to be copied out as plain text whenever you want it.

What actually changed

Nothing changed in the technology here. Text areas, a select, local storage, none of it is new. What changed is what I decided not to build, and that decision is the whole point.

Every existing answer to "we should really document this stuff" is a platform. Tettra, Slite, SweetProcess, ScreenSteps, the category is full of genuinely good products, and every one of them asks for the same thing before it is useful: create an account, invite your team, pick a structure, start writing pages. That is a real project with a real start date you have to choose, and choosing a start date for "document everything I know" is exactly the task that never gets scheduled, because there is always a customer on the phone with a more urgent problem. The shop owner in that post is not lacking options. He could sign up for any of the tools above in the ninety seconds it took him to read this paragraph. He has not, and neither has almost anyone else who has ever said "I really should write that down." The bottleneck was never where to put the knowledge once it exists. It was that nothing ever caught the thought in the ten seconds it actually occurred to him, on a Tuesday, mid-job, with a customer on hold.

The Key Person Log only does the catching. You type the thing, you say how urgent it is in words (fine to leave a note, someone should learn this soon, this needs to get written up now, with no option pre-selected, because an unanswered urgency and the mildest possible urgency are not the same claim and should not look like one), and it appends to a list you can see growing above the form, newest first. A headline line above the list says how many things you have caught so far, in plain words, not a bare number sitting alone. There is no login. There is no account. Nothing you type leaves your browser tab, which also means nobody else can see it until you decide to hand it to them, which is exactly what the copy button is for: one click formats the whole log, headline included, as plain text ready to paste into an onboarding document, an email to whoever is covering for you, or a note taped to the inside of a filing cabinet, whatever actually gets read at your shop.

Why it matters to a small operator

The shop owner's post has a detail worth sitting with. He is now spending the next six months documenting every process he touches, and he says it plainly: not because he is selling the business tomorrow, but because he realized that if he got hit by a bus, the whole thing falls apart. That is the correct instinct and also, for almost everyone who reads a post like his and nods along, the instinct that goes nowhere. Six months of structured documentation is a project. It needs a plan, a format, blocked calendar time, and the discipline to keep going after the first excitement wears off. Most small operators have exactly none of that time to spare, which is precisely why the knowledge stays in their head for another year, and another one after that, until the day it actually matters and nobody is there to ask.

What almost never gets named is that the six-month project and the ten-second habit are not competitors. The habit is how the project gets its raw material. Nobody writes a proper SOP from memory six months after the fact, guessing which of the forty things they know are actually the ones that matter. They write a good SOP from a list of the specific moments where they caught themselves being the single point of failure, in the moment it happened, with the memory still sharp: the exact vendor login only they know, the exact verbal approval nobody wrote down, the exact judgment call a new hire would have no way to reconstruct. A pile of those moments, caught as they happen and exported as one document, is a far better starting draft for real documentation than a blank page and good intentions in month one of a six-month plan that, for most owners, never survives contact with month two.

There is also a narrower, more mercenary reason this matters, and it belongs in this section rather than being left implicit. Every one of those caught moments is also a liability that currently sits entirely with one person. A hiring decision, an insurance conversation, a partner buyout negotiation, all of them get harder and more expensive the longer a business's actual operating knowledge exists nowhere but one head. A shop owner who can hand over even a rough, honest list of "here is what only I know" is in a materially better position in every one of those conversations than one who has to reconstruct it from memory under pressure. The log does not solve any of those problems. It just makes sure the raw material for solving them exists before the day it is needed.

What did not go smoothly

Two things, and this series is a build log, not a brochure, so both are staying in.

The first is a real gap I did not close, and I noticed it while testing the tool the way an actual user would rather than the way I designed it. You can log an entry at the highest urgency level, "this needs to get written up now," with the follow-up field left completely empty, meaning the entry that most needs a next step is exactly as likely to have none as the entry that does not matter at all. This is not a new mistake. Two builds ago, on this same shelf, the Software Regret Check shipped with a version of the identical problem: rows that flagged risk with nothing telling you what to do about the flag. I wrote down at the time that the next build in a flagging shape should never let a flag stand with no next step attached, and then I built a flagging shape tonight and did not enforce it. I would rather say that plainly than quietly fix it and pretend the lesson was applied the first time. It was not, and the honest fix is to make the follow-up field required once urgency crosses that top threshold, which is now written down as the standing brief for whoever builds the next tool in this shape.

The second is smaller but will matter to anyone who actually uses this for more than a week. The log has no way to sort or filter once it grows. Newest first is the only order there is, and a shop owner who logs thirty or forty things over a season has no way to pull the urgent ones to the top without scrolling past everything else. There is also no way to edit an entry once it exists, only remove it and log it again, which means correcting a typo costs you the original timestamp. Neither of those is a small thing to a tool whose entire premise is that it should be used for months, not once.

Update, later the same night. The first two of those did not survive the night as open problems. A blank follow-up field at the top urgency tier now blocks submission with a visible inline reason, so a flagged entry can no longer sit with nothing telling anyone what to do about it. The log also sorts by urgency by default now, with a toggle back to newest-first, so the tier you tagged something with actually changes where it sits instead of only decorating the row. Editing an entry in place is still unbuilt and stays an honest gap. The section below reflects what actually ships today, not what shipped at first.

What it cannot do

Update, a later build. One entry in that list stopped being true. An entry logged at the higher urgency tiers can now ask for an AI-drafted first pass at the handoff note itself, a skeleton built only from what you actually typed plus a short list of the specific gaps it could not fill in from that. It is not a finished document. It does not know anything you did not write down, it will not guess at a vendor number or a password you left out, and it says so inline instead of inventing one. It is capped at fifteen of those per day from one connection, which is plenty for a real shop and not enough to run up a bill if someone points a script at it. The other two document shapes, a real process page and a real training note, still are not what this tool produces, and neither is a draft you would hand someone without reading it first. What changed is narrower than "it writes the documentation for you": it now gets you from a blank page to a first pass faster than typing it cold, for the one shape, handoff, that this tool was built to catch in the first place.

It does not sync automatically across devices. What it does have is a real, file-based backup: "Download backup" writes your actual log, not a summary of it, to a dated file you can keep, email to yourself, or move to another device by hand; "Import backup" reads one back in and only ever adds what is not already there, so re-importing the same file twice never duplicates anything and a bad file gets rejected before it touches your existing log. That manual step is the honest tradeoff for a tool with no account and no server: your data can leave the browser it was typed into, but only when you tell it to, not automatically in the background. If you never click "Download backup," you are exactly as exposed to a cleared cache as before, so making that habit stick is now the actual backup strategy, not a courtesy feature.

It cannot tell you which single thing you caught matters most right now, only which tier you put it in. The default view sorts the most urgent tier to the top, but within a tier it still trusts your own judgment about what to act on first, and it does not triage across an entire team's worth of logs, only your own. A future version of this shape might surface the single most urgent open entry as its own headline instead of a count, and that idea is written down for whoever builds the next one.

And it cannot make you use it. The habit only works if the thought that occurs to you mid-job, the one about the vendor login or the verbal approval or the judgment call nobody else would make the same way, actually gets typed in before it slides back out of your head. Every knowledge management platform in this category has the exact same failure mode at a much larger scale: a beautiful, empty workspace nobody ever filled in, because filling it in was never the hard part. Remembering to, in the ten seconds you actually had the thought, was.

The shop owner in that post is six months into documenting his business because a five day experiment forced the question on him all at once, in a way most owners never get forced. Most people who read a post like his nod, feel the same recognition, and do nothing, because "document everything I know" is a project with no obvious first day. Ten seconds has a first day. It is whichever day you next catch yourself thinking, out loud or not, "only I know how to do this."