The one-to-one is scheduled for thirty minutes every fortnight. It reliably becomes a status update, because a status update is what two people default to when neither has thought about what else to discuss.
Both parties feel this is a waste, both are too polite to say so, and it continues for a year.
The fix is not a better agenda template. It is that a one-to-one is the only recurring meeting whose entire value comes from continuity, and continuity is a note.
Why it decays
Neither person prepared. Preparation for a 1:1 means five minutes with a note. Nobody does five minutes, so the meeting begins with "so, how's it going", which has exactly one natural answer: a list of what you are working on. Which your manager can already see.
Nothing carries over. The thing raised three weeks ago that neither of you has thought about since. The commitment made in June. Without a record, each meeting starts from nothing, and a meeting that starts from nothing can only cover the present — which is what makes it a status update.
The important things are not urgent. Career, growth, whether you are in the right role, the thing that has been quietly bothering you for two months. None of it presents itself, so it never comes up, so the meeting is permanently about this fortnight.
Nobody says the awkward thing. Which is often the whole reason the meeting exists, and it is much easier to raise something you wrote down calmly on Tuesday than something you have to summon on Thursday.
One note per person, forever
Not a note per meeting. One note per person, growing downward, exactly like a client note — and if you manage people, this is the single most useful document you have.
At the top: what they are working on, what they said they want next, how they like feedback, their working pattern, anything about their life you should remember to ask about. Below: dated entries, newest first.
The reason this shape wins is the moment it is used. You have five minutes before the meeting. One note, read the top and the last two entries, and you arrive knowing what was raised last time and what you owe. Any arrangement spread across a calendar of separate meeting notes means reconstructing that from three places, which is why nobody does it and why the meeting starts from nothing.
The four lines, before each meeting
Written by both people, ideally, and by at least one.
What has changed since last time. Not everything you did — what is different. One or two things.
What I am stuck on, or need a decision about. The most useful line in the meeting. It converts a status update into a conversation with a purpose, and it is the one your manager can actually act on.
Anything from last time that is still open. Requires reading the previous entry, which is the point.
One thing that is not about this fortnight. Career, a frustration, an idea, something about how the team is working. This is the line that stops the meeting collapsing into the near term, and it is worth having a standing slot for even when the answer is "nothing this time".
Four lines, five minutes. That is it.
What to write during and after
Ten minutes afterwards, while it is fresh.
What was decided, plainly, and by whom.
What each of you owes, with a date. These become actual dated tasks immediately — one sentence with the date in it — because a commitment made in a 1:1 and recorded only as prose is a commitment that will be quietly dropped, and dropped commitments are what destroy trust in this meeting specifically.
What they said about what they want. Career direction, interests, frustrations, the thing they mentioned twice. Six months of these is the material for a promotion case or a difficult conversation, and it is completely unreconstructable from memory.
What you noticed and did not say. For managers: the observation you were not sure about yet. Two or three of these across a couple of months either becomes a pattern worth raising or dissolves, and both outcomes are better than acting on a single impression.
Both sides should keep one
If you are the report, keep your own. It is not duplication.
Your note contains what you asked for and when — which is what you need when a promise made in March has not materialised by October, and which nobody else is recording from your side. It contains what you were told about your progress, in their words, dated, which is the raw material for your own review case. And it contains the things you raised, so a pattern of raising something four times is visible rather than a vague sense of not being heard.
It should be in your notes, on your machine, not in a company document. The reason is the same as for a work log: the day you most need the record of what you were promised is often the day you lose access to the company's systems.
What not to write
For managers, some care, because a note about a person is a record about a person.
Not conclusions about character. "Seems unmotivated" is an interpretation from partial information that will outlive both the impression and the situation that produced it. Write the observation — "missed two commitments this month, mentioned being stretched" — which is factual, actionable and fair.
Not anything you could not defend if read aloud. These notes can be subject to disclosure in a dispute, and more to the point: a note you would not want them to see is usually a note you should have turned into a conversation.
Not personal information they shared in confidence, beyond what you need to be a decent manager about it. "Back on the 14th" rather than the medical detail.
The test is whether the note would embarrass you if the person read it. If it would, the problem is generally not the note.
The honest version
None of this makes a bad one-to-one good. If the relationship is broken, or the meeting exists to perform management rather than to do it, better notes will produce a better-documented waste of thirty minutes.
What it fixes is the common case: two people who both want the meeting to be useful and neither of whom has spent five minutes preparing it. That is a genuinely large share of all 1:1s, and five minutes with one note is the whole intervention.
Cyanote has a 1:1 template in the / menu, and notes that nest into sub-pages so each person can be a page with entries under it. [[ links connect a person to the projects and meetings they appear in, so their page assembles context you never filed there. Tasks take an owner and a date out of a typed sentence, and everything is searchable a year later with ⇧⌘F. It is one local database on your own Mac — which for your own side of these conversations is the point, since it leaves with you when the laptop does not.