One on one meeting: making thirty minutes worth having

A one on one meeting is a recurring conversation between a person and their manager that exists for the things which never fit anywhere else: the concern that is not yet a complaint, the ambition nobody has been told about, the project detail that is quietly going wrong. It is not a status report — status can be read — and treating it as one is the fastest way to make people stop preparing for it.

Two failures account for most bad one on ones. The manager talks for twenty-five of the thirty minutes, and the meeting gets moved whenever something urgent appears. The second is worse: a one on one cancelled twice in a row teaches the person that their time is the flexible kind.

What a good one on one contains

• Their agenda first. The person brings what they want to discuss, and it goes at the top rather than in "any other business".
• Space for how things are actually going — workload, blockers, anything they are carrying that you cannot see.
• Feedback in both directions, specific and recent. Saved-up feedback delivered quarterly is not feedback, it is a verdict.
• Progress on what they are working towards: skills, scope, the next role, whatever they said mattered.
• Follow-up on what was agreed last time. Nothing kills the meeting faster than actions that never happen.
• Decisions and actions written down, with owners — including the ones that belong to you.
• Nothing that could have been a message. If the whole agenda is status, the meeting is misconfigured.

Talk less than half the time. Managers consistently estimate they talked less than they did, and the meeting is the only one on the calendar that belongs to the other person. Silence after a question is not an invitation to fill it — waiting is how the second, more honest answer arrives.

Running the series

1. Set a cadence and hold it: weekly for new starters or fast-changing work, fortnightly for most people, monthly at the outside. Rarer than monthly is not a one on one, it is a check-in.
2. Thirty minutes is usually right. Long enough to get past the surface, short enough to protect.
3. Share a running document both of you can add to between meetings, so nobody arrives trying to remember.
4. Open with their items, not yours. Yours will still fit; theirs are the ones that get dropped.
5. Write the actions at the end of the meeting, in the same document, while both of you are present.
6. Start the next one by reading last time's actions aloud. This single habit is what makes the series credible.
7. Reschedule rather than cancel, and do it yourself. Moving it is fine; dropping it is a message.
8. Every few months, step back: are they growing, is the work still the right work, has anything changed about what they want.

Writing it down without turning it into surveillance

Notes from a one on one should be a shared record of what was agreed, not a private file about a person. The practical rule is that everything you write should be something you would be comfortable with them reading — because in a shared document, they will. That constraint is a feature: it keeps the notes to decisions, actions and context, which is all anyone needs six weeks later when someone asks what was agreed about the promotion conversation.

Ettex Notes suits this: one note per person, with checklists inside the note so actions become items with visible progress rather than sentences that get skimmed, tags to keep a series together, backlinks and linked references so a one on one can point at the project or document being discussed, reminders for the follow-up you promised, and version history showing what changed and when. The recurring slot lives in Ettex Calendar, and anything that becomes a formal document — a development plan, a role change — moves to Ettex Docs where comments and version history apply.

To be clear about what Ettex does not do here: there is no one-on-one or performance module, no goal or OKR tracking, no review cycles, no prompts suggesting what to ask, and no per-person permission model that hides a note from the person it is about. It is a shared note with checklists and history. For a small team that is genuinely enough; formal performance management at scale is a different category of software.

Running a team is more than holding conversations. Team management covers workload, capability, priorities and the decisions a manager owns, which is what those conversations are supposed to serve.

Signals a one on one is not working

• It gets moved or cancelled more than it happens.
• The person arrives with nothing, which usually means previous meetings taught them not to bother.
• It is entirely status, and both of you leave knowing nothing you did not know before.
• Actions are agreed and never revisited, so the meeting becomes theatre.
• Feedback only appears in the formal review, making the review a series of surprises.
• You do most of the talking — the easiest thing to measure and the most common thing to get wrong.
• Difficult subjects are always raised elsewhere, which means the meeting is not safe enough for them.

Keep it away from the annual performance review. The one on one is where problems are raised early precisely because nothing is being scored; the moment it feeds a rating, people start saving their concerns for a safer moment. If the conversation tends to sprawl, a simple meeting agenda with three standing questions is usually enough structure.

A one on one meeting works when it is protected, when the other person sets the agenda, and when last time's actions get read out at the start of this one. Everything else is detail.