M360 Compass

M360 Compass · Management insights

One-on-one meeting: a 30-minute agenda for managers

· 7 min

A manager listens to a technician in a glass-partitioned space beside a workshop, with two open notebooks and a sand timer on the table.

A one-on-one meeting is a recurring conversation between a manager and an employee to clarify priorities, understand obstacles and agree on what happens next. A thirty-minute agenda can protect time for listening, one practical issue, development and a clear review of commitments.

In a growing business, a check-in can become a list of completed tasks read aloud to the manager. The manager gets an update, but the employee leaves with the same obstacles. A friendly conversation can also end without anyone knowing what was decided. The model below keeps space for both the person and the work without turning every meeting into a formal appraisal. Treat its timings as a planning aid, rather than a test of how closely people follow the clock.

What should a one-on-one meeting make possible?

A useful check-in examines what quick exchanges leave unresolved. A priority may look clear in a work plan but remain difficult to apply. An employee may be waiting for a decision the manager believes has already been communicated. The meeting gives both people an opportunity to make that gap visible and discuss it.

In its July 17, 2026 article about one-on-one meetings and delegation, BDC recommends a recurring appointment, a shared agenda and documented decisions. Job Bank also emphasizes two-way discussion and agreed follow-up. The thirty-minute allocation in this article is an original proposal, rather than an agenda validated by either organization.

Keep the purpose distinct from a performance review, which considers a defined period and known expectations. A stay interview focuses more specifically on reasons to remain with the organization and concerns that could lead someone to leave. A regular check-in may surface those subjects, but it does not need to cover every management topic at every meeting.

What belongs in a thirty-minute agenda?

Share the headings before the meeting. Both the employee and the manager can add an issue, then agree on what needs a conversation. A tracking system can provide routine status information; the meeting should create room to understand, decide or offer support.

Suggested time Focus Opening question
3 minutes Open the conversation What needs my attention today?
5 minutes Review the last commitment What did we do and learn since we last spoke?
10 minutes Explore an obstacle or decision What is preventing the next step?
7 minutes Discuss support and development Which resource or learning opportunity would help now?
5 minutes Confirm the next steps Who will do what, by when, and how will we review it?

The proposed blocks add up to thirty minutes. They provide a starting structure rather than a rigid operating rule. If an important concern emerges, explicitly move another topic or book a separate discussion. Do not squeeze a sensitive conversation into the last few seconds simply to finish the agenda.

The opening does not require an employee to disclose personal information. It gives them room to identify a work event, concern or priority. The manager should also explain which decisions they need to prepare so both people understand what can realistically be settled during the appointment.

How can managers listen without taking every task back?

When someone describes a problem, ask about a specific situation before proposing a fix. What have they tried? Which information is missing? At what point does the decision fall outside their authority? These questions help separate a missing resource, competing priorities and an expectation that has not been made clear.

Summarize your understanding before moving ahead. Two requests may arrive at the same time with no agreed order of priority. That description is easier to examine than a broad judgment that the employee is disorganized. Check the account together before assigning a cause or assuming why someone acted as they did.

Support does not mean taking responsibility for every file. Ask the employee to suggest a next step when that fits their experience and decision-making authority. The manager remains responsible for the resources and trade-offs within their own role. Delegation without access to necessary decisions can leave someone alone with exactly the same obstacle.

Include a question about your own contribution: which instruction or response from me would make this clearer? Listen without immediately defending the current approach. Where a fact needs checking, say so and agree on when you will respond. An honest, bounded commitment is more useful than an answer offered only to move the conversation along.

How do you keep a useful record of commitments?

Close with a short set of actions and ask both people to restate them. For each action, record the intended result, the person responsible, a date and the review point. Choosing not to act is also a decision; explain what information or change would justify reopening it later.

Keep the working note brief and limit access to the appropriate people under your own rules. Separate shareable operational actions from information needing more restricted handling. The note does not have to reproduce the whole discussion. A concern that belongs in another process should follow the appropriate channel rather than remaining unresolved in a check-in notebook.

Consider a fictional example from a small manufacturer in Granby. A technician tells her manager that she often waits for approval of a quality check before preparing the next production run. Instead of asking her to work faster, they clarify the handoff criteria, identify who responds and agree on when an extended wait should be raised. At their next appointment, they examine two files to understand what remains unclear. The example claims no client result or measured productivity gain.

When the issue concerns a team priority, connect the action with understandable objectives and key results. For a new hire, also use the 30-60-90 day onboarding plan to set appropriate expectations. Someone learning a role should not automatically be assessed against the same reference point as an experienced colleague.

How can M360 Compass support these conversations?

M360 Compass is a people management operating system for small and medium-sized businesses. Momentum connects shared agendas, issues, decisions, responsibilities and deadlines. These reference points can help keep an agreed operational action visible between conversations.

Performance and individual development plans connect feedback with skills and development priorities. When a meeting identifies a useful learning action, the manager can place it within a continuing development discussion. RoleAlign also supports clarification of responsibilities and expectations when the same grey area keeps coming up.

Those capabilities assist preparation and follow-through; they do not guarantee attentive listening or trust. Check the access arrangements and information appropriate to your configuration before documenting a conversation. Deciding whether to record a sensitive point, seek support or change a responsibility remains a management responsibility.

After several meetings, review the practice itself. Did appointments happen? Did actions receive a response? Can both people explain what was decided? That review examines a working habit. It does not, by itself, demonstrate improved engagement or establish that the meeting caused another organizational result.

Common questions about regular check-ins

How often should we meet?

A weekly or every-other-week rhythm can be a starting point. Adjust it to the employee’s independence, workplace changes and the needs of the work. An urgent issue or important request should not have to wait for the next appointment.

What if the employee says very little?

Share topics beforehand, ask a specific question and allow time to think. Offer an opportunity to return to a topic later. Silence alone is not evidence that someone has disengaged from their work.

Can we cancel when everything seems fine?

First check whether the employee had something to raise. If the meeting needs to move, agree on another time immediately. Repeated cancellations can make the availability of support difficult to predict.

How do we avoid another meeting with little value?

Focus on a difficulty, decision or support need. Read straightforward status updates beforehand where practical. End with an understandable next step and review it at the following conversation.

Protect the time, listen to a real situation and follow through on a commitment. To connect conversations with responsibilities and development, request a demonstration of M360 Compass.