What 1:1s are actually for

A 1:1 is not a status meeting. The EM already has access to most status through standups, Jira, and other channels. Running 1:1s as status meetings wastes the format — it treats the most direct communication channel between a manager and a report as a third team standup.

The 1:1 is for the things that don't surface anywhere else: what's frustrating the person right now, where they want their career to go, what blockers they haven't raised in standup because they seem too small or too political, what the manager needs from them specifically. The agenda below protects space for all of those.

The agenda (copy-paste this)

Duration: 30 minutes weekly, or 45 minutes biweekly
Format: Both parties add items to a shared doc before the meeting

Section 1 — Top of mind (5 min)

The employee goes first, no prompt — what's on your mind this week?
The manager listens; no fixing or problem-solving yet
This section surfaces things that don't fit any other format

Section 2 — Projects and blockers (10 min)

What's moving and what's stuck
Blockers: can the manager unblock this directly, or does it require escalation?
Skip work that's clearly on track; this isn't a status review

Section 3 — Growth and development (5-10 min)

What skills are you working on? What opportunities do you want?
Are there specific things the manager could do to help?
This section gets cut when time is short — put it in the agenda explicitly so it doesn't disappear

Section 4 — Manager topics (5 min)

Feedback the manager has for the report
Context the report needs: org changes, team direction, process updates
The manager's asks: anything needed from the report this week

Action items (close of meeting)

Who does what, by when; both people write them down before the call ends

What generic 1:1 templates miss

Most 1:1 templates err in one of two directions. The overly structured version has 15 prompts and feels like a performance review every week. It turns the meeting into a form-filling exercise and kills the kind of honest conversation that makes 1:1s valuable in the first place.

The underfitted version is "how are you doing?" with no structure, which works when things are going well and collapses when there's something real to discuss. The person who needs to say something hard doesn't have a hook to hang it on.

The section most templates skip entirely is growth and development. It's the thing engineers most want to talk about and the first section to get cut when the meeting runs long. An explicit time box is the only reliable way to make sure it happens more than twice a year.

The other gap is what happens to commitments made in 1:1s. The EM commits to getting the report into a specific project. The report commits to resolving a long-standing blocker. These commitments are made in a private conversation, not tracked in Jira or a team Slack channel. They live in two people's working memory and disappear if neither person writes them down. They're often the most consequential outputs of the meeting and the ones most likely to be lost.

For how missing context from 1:1s (and other meetings) compounds into hidden overhead: The meeting tax.

How Pavleur handles 1:1 notes

The standard approach is a shared doc — both parties add to it before the meeting, one person updates it after. This works until it doesn't. A week gets skipped. The doc falls behind. After a few months, the history is patchy and not useful for performance review prep or career growth conversations.

Pavleur runs during the 1:1 and generates the meeting report automatically after the call ends. The report captures action items with owners, feedback exchanged, topics covered in each section, and any visuals referenced — an org chart, a career ladder screenshot, a PR or ticket someone pulled up mid-conversation. Audio-only tools give you the transcript but miss the visual context that often carries the most meaning.

The full meeting history is searchable. An EM with six direct reports can pull up three months of 1:1 records for a specific person without reconstructing them from a patchy shared doc. That makes performance reviews and growth conversations much easier to prepare for. For how Pavleur compares to other meeting tools on this: Pavleur vs. alternatives.

A note on cadence

Weekly 30-minute 1:1s are generally better than biweekly 45-minute ones because the feedback loop is tighter. Monthly 1:1s are almost never enough for a direct report, especially someone newer to the team or role. The format stops working when the cadence is long enough that both parties have forgotten half the action items from the previous session — at that point you spend the first 10 minutes reconstructing context instead of making progress.

If you're biweekly, the meeting history becomes especially important. The shared doc or the Pavleur report from the previous session should open the meeting, not rebuild from scratch.