How to Run Better One-on-One Meetings: A Manager’s Weekly System

A good one-on-one meeting should make the next week clearer for both the manager and the employee. Too often, it becomes a hurried status update: the manager works through a list of projects, the employee reports what happened, and the conversation ends without useful support or a clear next step.

Running better one-on-one meetings does not require a complicated template or a long list of clever questions. It requires a dependable rhythm: collect topics while they are fresh, prepare briefly, protect the employee’s agenda, listen for the real issue, and turn agreements into visible follow-up.

This guide gives managers a practical weekly system for doing that while keeping performance records, confidential notes, and team commitments in the approved workplace systems where they belong.

Be clear about what the one-on-one is for

A one-on-one is a recurring, private conversation between a manager and one direct report. It is useful for matters that do not fit well in a project update or team meeting: support, feedback, workload, relationships, development, decisions, and concerns the employee may not raise in a group.

The current Asana one-on-one guide distinguishes these meetings from status updates and frames them around feedback, career development, trust, and individual concerns. That boundary matters. If routine project reporting takes the entire meeting, the conversation loses the space that makes it valuable.

Before changing your agenda, write one sentence that describes the purpose of your one-on-ones. For example: “This is protected time for you to raise what matters, get support, exchange feedback, and leave with clear next steps.” Share it with each report so both of you know what the meeting is meant to do.

Choose a cadence the relationship can sustain

There is no universal frequency. A new hire, a newly promoted manager, or someone navigating rapid change may need a weekly conversation. An experienced employee in a stable role may prefer every two weeks. Less frequent meetings make consistency and prompt rescheduling more important.

Set the cadence together, make the invitation recurring, and revisit it when the employee’s work changes. Consistency matters more than copying another company’s schedule. If you must cancel, reschedule promptly rather than letting the conversation silently disappear.

Give the meeting enough room for a real conversation. Thirty minutes is often workable; forty-five may suit complex roles or less frequent meetings. The right length is the shortest block that still allows the employee to bring an important topic without watching the clock from the first minute.

Use one shared agenda that stays open all week

The easiest way to improve preparation is to stop starting from a blank page before every meeting. Keep one private, shared agenda for each manager–employee pair. Link it from the recurring invitation and let both people add items as they arise.

The GitLab 1-1 handbook recommends a consistent agenda, encourages both people to add topics, and suggests keeping the document available during the week rather than scrambling shortly before the call. Its detailed format is specific to GitLab, but the durable principle is useful anywhere: continuity beats a fresh list every time.

A simple shared agenda can have five sections:

• Employee topics: questions, concerns, decisions, feedback, and help needed.

• Open actions: promises from the previous meeting, with an owner and date.

• Workload and priorities: what feels unclear, overloaded, blocked, or likely to slip.

• Growth and feedback: strengths to build, skills to practice, and feedback in both directions.

• Later: valuable topics that do not need this week’s limited time.

Let the employee’s items come first. Your role is not to arrive with a hidden interrogation. If you need to address a formal performance or conduct issue, follow your organization’s process instead of disguising it as an ordinary one-on-one.

Prepare in ten focused minutes

Preparation should make you present, not scripted. Reserve a short block before the meeting and review:

1. the employee’s new agenda items;

2. actions you personally promised last time;

3. recent wins or useful recognition you have not yet shared;

4. a blocker, workload signal, or priority conflict that may need a decision;

5. one open-ended question that would help you understand rather than assume.

Do not turn preparation into a full project review. Read the team tracker when context is necessary, but move routine status elsewhere. Prepare to listen and decide, not to recite information the employee already entered.

Run a 30-minute agenda that leaves room for the employee

Use time ranges as guardrails, not a rigid script:

• 0–5 minutes: check in and confirm what matters most today.

• 5–18 minutes: work through the employee’s topics, starting with the one they most need help with.

• 18–24 minutes: discuss priorities, workload, feedback, or development that needs shared attention.

• 24–28 minutes: make decisions and name actions.

• 28–30 minutes: recap what each person heard and confirm what happens next.

If a sensitive or important subject needs more time, use the meeting for it and move lower-value items. A useful one-on-one is not the one that clears the agenda. It is the one that addresses the right issue responsibly.

Ask questions that reveal the decision or support needed

Generic questions often produce generic answers. “Everything okay?” makes “yes” easy. Ask questions that help the employee describe what changed, what is difficult, and what they need from you.

• What is taking more effort than it should right now?

• Which priority is least clear?

• What decision are you waiting for?

• Where are dependencies slowing you down?

• What should I start, stop, or continue doing as your manager?

• What work are you proud of that I may not have seen?

• Which skill or responsibility would you like to practice next?

Then listen long enough to understand the request. Is the employee asking for a decision, context, coaching, escalation, protection from conflicting work, or simply space to think aloud? Do not solve the wrong problem because you started answering too quickly.

Turn concerns into options, not vague reassurance

When an employee says the workload is too high, “do your best” is not a plan. Identify the competing commitments, deadlines, and consequences. Then agree on an option: stop something, reduce scope, move a date, get help, clarify the standard, or escalate the trade-off to the person who can decide.

The guide to prioritizing tasks when everything feels important offers a useful decision sequence for urgency, consequences, dependencies, and available capacity. Use it for the employee’s own work only after the manager has made the organizational trade-off clear.

Record the decision in the approved team or HR system when it belongs there. A personal task list can remind you to follow up, but it should not become the only record of a changed deadline, accommodation, performance expectation, or staffing decision.

Close with actions that can survive the week

Reserve the final minutes for a spoken recap. For every action, name the outcome, owner, date or review point, and authoritative tracking location. “Manager to check with Finance about the training budget by Thursday” is usable. “Look into training” is not.

Keep the action list short. If the meeting creates eight new commitments, decide which ones matter before leaving. Then schedule your own follow-up while the context is fresh. The employee should not have to use the next one-on-one to remind you what you promised in the last one.

GitLab’s suggested agenda format uses explicit states for discussion, help, review, and completion. You do not need its exact tags, but visible state is helpful: waiting, due, done, or moved to another system.

Plan the follow-through before your calendar fills

Managers often leave several one-on-ones with a pile of small promises and no time reserved to fulfill them. Treat follow-through as work, not as invisible overhead.

1. Capture your actions immediately after each meeting.

2. Place time-sensitive actions beside the week’s existing meetings and deadlines.

3. Batch quick approvals or messages when that reduces context switching.

4. Schedule deeper work—such as reviewing a growth proposal—in a real calendar block.

5. Send an update before the next meeting if an action is delayed.

If your task list and calendar are disconnected, use the guide to organizing tasks and calendar together to test whether your promised follow-up actually fits.

Adapt the system without losing its purpose

New hires may need more context and shorter feedback loops. Senior employees may need more space for strategy and development. Remote employees may benefit from a shared written agenda and explicit follow-up, but the conversation should still feel human.

During a crisis or high-change period, use more frequent check-ins if they reduce uncertainty. Do not simply add meetings on top of the work. Shorten the agenda, cancel low-value status calls, and protect the conversation that helps the employee make decisions.

For a first conversation with a new report, explain the purpose, ask what has made previous one-on-ones useful or frustrating, agree on confidentiality and documentation boundaries, and choose a trial cadence. Review the format after four meetings.

Common one-on-one mistakes to avoid

• Status takeover: project reporting uses all the time.

• Manager monopoly: the manager supplies the agenda, questions, and most of the talking.

• Cancellation habit: the meeting is the first calendar block sacrificed every busy week.

• Advice before understanding: the manager offers solutions without clarifying what help is wanted.

• Invisible actions: promises have no owner, date, or tracking home.

• One-format-fits-all: every employee gets the same cadence and questions regardless of context.

• Private-system risk: sensitive employee information is copied into a personal planner or unapproved tool.

Fix one failure mode at a time. A lighter agenda with reliable follow-through is better than an elaborate template nobody maintains.

How Flick helps managers prepare and follow through

Flick can support the personal execution around one-on-one meetings while your organization’s HR, performance, project, and documentation systems remain authoritative. Keep a project for your own manager actions, use sections such as Prepare, Follow up, and Waiting, then add dates, deadlines, priorities, reminders, notes, or permitted attachments.

Because tasks and calendar events are visible together, you can place preparation before the meeting and follow-up after it instead of hoping both fit later. Drag a task into open time, resize the block when the work needs longer, and move it when the week changes. Flick does not assign work to employees or replace the shared agenda.

If your one-on-one promises keep disappearing into a long task list, review Flick Planner’s task-and-calendar workflow and test it with your own preparation and follow-up for one week.

Conclusion

Better one-on-one meetings come from a repeatable loop: define the purpose, choose a sustainable cadence, keep a shared agenda, prepare briefly, let the employee lead the important topics, make real decisions, and schedule the follow-through.

Start with one improvement at your next meeting. Open the agenda early, ask which topic matters most, and leave two minutes to confirm actions. That small discipline will do more than adding twenty new questions to a conversation that still has no clear ending.