One-on-One Meeting Agenda: Progress, Support, Development and Follow-Up

A one on one meeting agenda creates protected space for an employee and manager to discuss progress, support, feedback and development. It should improve shared understanding and action, not turn every conversation into a status interrogation or a hidden performance record.

Managers remain responsible for fair, context-aware judgment. Apply applicable employment law, organizational policy, collective arrangements, accommodations and approved HR procedures. A generic agenda cannot authorize discipline, change employment terms or replace qualified HR guidance.

Set the purpose and cadence together

Agree what the recurring meeting is for: understanding priorities, removing blockers, exchanging feedback, supporting development and maintaining the working relationship. Clarify which topics belong in project reviews, formal performance processes, compensation discussions or confidential HR channels instead.

Choose a cadence that fits the role and employee’s needs. Protect the time, but make rescheduling explicit when unavoidable. Repeated cancellations can signal that employee support is being treated as optional. Allow either person to request an additional conversation when waiting would create avoidable harm or delay.

Set expectations for preparation, note-taking and confidentiality. Employees should know what is recorded, where it is stored and who can access it.

Copy this one on one meeting agenda

ONE-ON-ONE AGENDA

Employee / manager / date:
Topics added by employee:
Topics added by manager:
Confidentiality and note-taking expectations:

CHECK-IN
What needs attention today?
Workload, wellbeing or context to consider:

PROGRESS AND PRIORITIES
Progress since the last meeting:
Current priorities and tradeoffs:
Decisions or clarity needed:

SUPPORT AND FEEDBACK
Blockers / dependencies / manager actions:
Feedback from employee to manager:
Feedback from manager to employee:

DEVELOPMENT
Skills, interests or opportunities:
Support, exposure or learning action:

FOLLOW-UP
Decision / rationale:
Action / owner / due date:
Sensitive item routed separately:
Next meeting / topics to revisit:

Treat this as a flexible conversation guide. Do not require disclosure of health, family or other private information that the employee does not need to provide through this forum.

Start with the employee’s context

Open by asking what would make the meeting useful and which topic needs attention first. A brief personal check-in can support connection, but managers should not pressure employees to disclose private circumstances. Respect boundaries and route accommodation or health matters through approved confidential processes.

Listen for changes in workload, confidence, role clarity or team dynamics. Avoid diagnosing emotions or treating a quiet response as agreement. Ask concrete, non-leading questions and allow time to think.

If an employee raises a safety, harassment, discrimination, ethics or mental-health concern, follow the organization’s escalation and support procedure. Do not promise secrecy that policy or law may not allow.

Review progress without creating a status dump

Discuss outcomes, learning and changing conditions rather than reading every task aloud. Ask what moved, what did not and why. Separate facts from assumptions, and consider dependencies that the employee does not control.

Use evidence appropriate to the work, but do not use surveillance or decontextualized activity measures as a substitute for management judgment. If a formal performance concern exists, managers should follow approved HR guidance and provide clear, timely information rather than hiding it inside casual conversation.

A client status report template offers a useful pattern for separating completed work, change, risk and requested decisions, even when the one-on-one concerns internal work. This leaves more room for support.

Discuss credit and contribution accurately. Managers should understand collaborative work without forcing employees to compete for visibility. Ask which outcomes are difficult to see and which colleagues or dependencies contributed. Correct misunderstandings before they become performance assumptions.

Where priorities changed, preserve the previous expectation and the manager’s revised direction. Employees should not be judged later against an obsolete plan that was never clearly updated.

Clarify priorities and tradeoffs

Identify the most important outcomes before the next meeting and what can move if capacity changes. Managers should make tradeoffs explicit instead of assigning several “top priorities.” Confirm deadlines, quality expectations, decision rights and dependencies.

Ask where expectations conflict or information is missing. Record any decision and who must communicate it to affected colleagues. A decision log template helps when a priority choice needs durable rationale beyond the one-on-one.

Avoid transferring all planning burden to the employee. The manager is responsible for clarifying organizational context and escalating structural resource problems.

Remove blockers through specific support

Describe the blocker, effect, evidence checked and decision or access needed. Distinguish a task the employee can own from an organizational constraint the manager must resolve. “Keep trying” is not a useful response to missing authority or conflicting direction.

Agree a manager action with a date: obtain a decision, connect a stakeholder, protect focus time, adjust scope or escalate risk. Use conversation-to-action-items practices when several owners and dependencies need a shared record.

Check what authority the employee already has. A blocker may be solved by clarifying a decision boundary rather than requiring repeated manager approval. When delegation changes, state the scope, constraints, resources and escalation point. Do not transfer accountability without access or support.

Follow up on prior commitments. Managers lose credibility when employee actions are tracked closely while manager actions disappear.

Exchange feedback in both directions

Offer feedback close enough to the event to be useful. Describe the observable situation, behavior or output, its effect and the expected next step. Invite context and correction. Avoid labels about personality, motivation or identity.

Ask what the manager should start, stop or continue doing, and make it safe to answer honestly. Do not retaliate against critical feedback or demand immediate candor in a low-trust relationship. Acknowledge what you heard and state what will change or why a constraint remains.

Use a quality review meeting agenda as a structural example for separating evidence, deviation and action when preparing sensitive feedback. Formal employment decisions require approved evidence, review and HR process.

Do not save all positive feedback for formal reviews or all corrective feedback for one-on-ones. Recognition should be specific and credible. Corrective feedback should include an opportunity to respond and a realistic support path. If the manager made an incorrect assumption, acknowledge it and correct the record.

Support development without making promises

Discuss skills the employee wants to build, responsibilities they want to explore and experiences that could help. Connect development to both employee interests and realistic organizational needs. Do not imply a guaranteed promotion, compensation change or opportunity that has not been approved.

Choose a small next action: shadow a colleague, lead part of a meeting, receive targeted feedback, complete approved learning or document a stretch assignment. Define support and a review point. Development should not become unrecognized extra labor with no adjustment to workload.

A training needs assessment interview guide can help explore skill gaps and support needs without assuming that training is always the solution.

Revisit development actions after enough time to learn from them. Ask what the employee practiced, what evidence changed and what support was missing. Adapt the plan rather than treating an incomplete action as proof of low commitment. Opportunity allocation should be reviewed for fairness across the team.

Discuss workload and wellbeing responsibly

Ask about capacity, competing deadlines and sustainable working conditions. Focus on work design and support rather than requesting a medical explanation. If an employee discloses a need for accommodation or leave, use the confidential process and involve qualified HR owners as appropriate.

Look for repeated overtime, unclear coverage, excessive switching or emotionally difficult work. Agree practical changes within authority and escalate what requires broader action. A wellness check is not a clinical assessment, and managers should not attempt diagnosis or therapy.

In urgent situations, follow local emergency and employee-support procedures rather than relying on the next scheduled meeting.

Record decisions and protect privacy

Keep notes proportionate to the purpose. Record decisions, commitments and relevant context, not speculative judgments or unnecessary personal detail. Separate broadly shareable work actions from restricted employee information. Follow access, retention and employee-record policies.

Agree how shared actions will be visible between meetings. A private manager notebook can make it hard for the employee to correct errors or track commitments. Conversely, a public project board may be inappropriate for feedback or personal context. Use separate controlled locations with explicit audiences.

Let the employee correct factual errors. If notes may contribute to a formal process, be transparent and follow approved HR requirements. Do not backfill a performance narrative from informal fragments after a decision has been made.

Use meeting follow-up practices for reviewed action summaries, while routing confidential matters separately.

Use Kuno only with meaningful consent

Workplace recording can affect trust and may be regulated. Use Kuno only when the organization authorizes it, the employee receives clear notice, appropriate consent is obtained, and recording is genuinely suitable for the topic. Provide a practical non-recorded option.

For an authorized, openly recorded one-on-one, Kuno can help draft notes and follow-up actions for both participants to verify. It does not evaluate employees or make people decisions. Explore Kuno

Do not record sensitive HR, health or protected disclosures merely for convenience. Human review, restricted access and accountable judgment are essential.

End with ownership and follow-through

Summarize decisions, employee actions, manager actions, due dates and topics to revisit. Ask whether the summary reflects the conversation. If disagreement remains, record it accurately instead of manufacturing consensus.

Leave a few minutes for anything not yet discussed. Confirm whether an issue needs a separate meeting, HR support or faster escalation. Avoid ending immediately after difficult feedback without checking understanding, next steps and available support.

Managers should review patterns across their one-on-ones without creating a comparative employee surveillance system. Repeated workload conflicts or unclear decisions may indicate a team-level process issue. Address that cause while protecting individual confidentiality.

Between meetings, complete promised support and share relevant updates. Begin the next one-on-one by reviewing commitments, then adapt the agenda to current needs. Periodically ask whether the cadence and format remain useful.

Keep follow-up clear while preserving the human relationship. Kuno supports consented capture and draft action notes; managers and employees verify context, and accountable people retain every employment decision. See Kuno

FAQ

The frontmatter FAQ provides concise answers without repeating them in the body.