A one-on-one gives an employee and manager time to discuss blockers, feedback and growth without the whole team in the room. A shared agenda helps them use the time for the issues that need a conversation rather than only reporting status.
Use a shared agenda, a few questions and running notes that carry from one meeting to the next. The template below gives you a starting structure for a 30-minute conversation, with room to follow up on unfinished actions.
Quick answer
- Make it the employee's meeting. They bring most of the agenda.
- Use a running note that both people add to between meetings.
- Keep a simple structure: wins and blockers, the employee's topics, the manager's topics, growth, action items.
- Never cancel twice in a row. Reschedule instead.
A one-on-one agenda that works
For a 30-minute weekly or fortnightly meeting:
- Check-in (2 minutes). How are you, really?
- Wins and blockers (5 minutes). What went well? What's in the way?
- Employee's topics (12 minutes). Whatever they added to the note.
- Manager's topics (5 minutes). Feedback, context, upcoming changes.
- Growth (4 minutes, at least monthly). Skills, goals, what's next.
- Action items (2 minutes). Who does what by when.
Send routine status updates ahead of time so the conversation can focus on decisions, support and feedback. This agenda is a starting point, not a requirement to switch topics every few minutes. GitLab's one-on-one guidance similarly recommends a consistent agenda with most topics added by the team member.
Questions for managers to ask
Pick one or two. Don't run through all of them.
- What's taking more of your time than it should?
- Is there anything you're waiting on from me?
- What's one thing we could change about how the team works?
- What part of your work do you want more of? Less of?
- Is there feedback you've been holding back?
- On a scale of 1 to 10, how sustainable does your workload feel?
- What would you like to be doing a year from now?
Questions for employees to bring
- Here's what I'm working on next. Is that still the priority?
- I'm stuck on X. Can you help me with Y?
- How do you think I handled Z?
- What should I be learning in the next three months?
- Is there anything coming that I should know about?
The running note
A running note can make follow-up easier. Keep one document per employee-manager pair, with the newest meeting at the top and unfinished actions still visible. Limit access to the people who need it, and follow your workplace's rules for confidential feedback and retention.
Why it works:
- Topics get added when they happen, not remembered 30 seconds before the call.
- Action items stay visible. Next week starts by checking last week's.
- Patterns show up. Three weeks of "blocked on access" is a problem worth escalating.
- Reviews have concrete examples. You can refer to agreed goals and past actions rather than relying only on memory.
One-on-one template (copy and paste)
# 1:1: [Name] and [Manager]
## [Date]
Check-in:
Wins:
-
Blockers:
-
[Employee] topics:
-
[Manager] topics:
-
Growth (monthly):
Action items:
- [ ] [Who], [what], [by when]
Carry over to next time:
-
Scheduling one-on-ones so they actually happen
- Same time, recurring. Put it on the calendar as a repeating event and treat it as fixed.
- Choose a time both people can protect. Avoid a slot that repeatedly clashes with deadlines or other commitments; there is no universally best weekday.
- Move, don't cancel. If something comes up, edit that one occurrence. Most calendars let you change a single occurrence without touching the series.
- Protect the first five minutes. If you're the manager, finish the previous call on time.
Running one-on-ones in Dainvo
Dainvo is a personal planner, so this is about the manager's or employee's own setup:
- Recurring event. Create the one-on-one on Google, Outlook or iCloud. Dainvo supports single-occurrence changes on Google and Outlook; its iCloud edits use series scope. If you need to move just one iCloud occurrence, use Apple Calendar and check the result in Dainvo.
- Notes as files you own. Event and meeting notes are on by default and saved as local Markdown in a folder you choose. Keep the running note as one Markdown file per person in that folder, and open it from your prep block each week.
- Join in one click. For a recurring Google event, Dainvo can create a Google Meet link. Teams, Zoom and Webex meeting creation in Dainvo requires a single event. For a recurring series using one of those services, create the recurring meeting in that service and use its join link in the calendar event.
- Action items become tasks. Create a Dainvo Task from the note, or link an existing one, then drag it onto the calendar to give it time.
- Prep block. Add a 10-minute Bucket before the meeting with the note and any files linked. See the meeting preparation checklist.
Notes and local file links stay on desktop and are not shared with the other person automatically. If you want a shared agenda, keep it in a suitably restricted shared document and link it from the event. Do not put private feedback in an event visible to a wider audience.
FAQ
How often should one-on-ones happen? Weekly can work well for new team members or fast-moving work; every two weeks may suit a more independent working relationship. Agree on the cadence together and shorten the interval when blockers or feedback need attention. Do not save urgent feedback for the next scheduled meeting.
How long should a one-on-one be? 30 minutes works for weekly meetings. Make it 45 to 60 minutes if you meet monthly.
Who should own the one-on-one agenda? The employee, mostly. The manager adds topics too.
What shouldn't be in a one-on-one? Long status updates and anything that should go to the whole team.
Try Dainvo to keep recurring meetings and their notes in one place.



