One on one meetings are recurring conversations between a manager and an individual employee. They help managers understand work challenges, remove blockers, provide feedback, discuss career development and strengthen employee ownership.
Effective one on one meetings go beyond project updates. They create a structured space to discuss what is affecting performance and what support an employee needs to deliver better outcomes.
A practical 30-minute 1:1 meeting agenda includes:
5 minutes for an employee check-in 10 minutes for priorities and blockers 10 minutes for feedback and development 5 minutes for decisions and follow-up actions The employee should contribute to the agenda, while the manager remains responsible for creating a productive conversation and acting on agreed commitments.
Key Takeaways One-on-one meetings should help managers and employees understand performance conditions, not simply duplicate project status reporting. A flexible 30-minute agenda can balance employee concerns, priorities, feedback, development, and management commitments. Effective managers distinguish individual capability needs from workload, decision, dependency, and organisational constraints. The SBI feedback model helps make feedback specific, while dialogue helps establish the appropriate response. Connecting individual conversations to organisational priorities can reveal execution risks and support meaningful development. Skip-level meetings can help leaders identify organisational barriers when employee feedback is handled responsibly. Manager follow-through, issue resolution, conversation usefulness, and development progress provide more meaningful evidence than meeting completion alone. One-on-one meetings become part of an effective performance system when the organisation can act on the conditions those conversations reveal. Introduction A delivery team has completed its weekly review. Every employee has shared progress, the project dashboard is updated, and the manager has recorded the tasks that remain incomplete.
On paper, the team appears to be under control.
Yet two employees are struggling with conflicting priorities. One is waiting for a decision from another department. Another has stopped raising concerns because previous requests received no response.
The status meeting has provided visibility into the work. It has not necessarily revealed the conditions affecting the people responsible for delivering it.
One-on-one meetings give managers an opportunity to understand those conditions.
They create dedicated space to discuss expectations, workload, capability, feedback, professional development, and the support employees need to perform effectively.
However, conducting regular one-on-one meetings does not automatically improve performance.
An employee may explain the same blocker every week. A manager may provide constructive feedback without resolving conflicting priorities. Development goals may be discussed repeatedly without creating opportunities to practise new capabilities.
The conversations are happening, but the conditions affecting performance remain unchanged.
This is the distinction between a one-on-one meeting as a recurring management activity and a one-on-one meeting as part of an effective performance system.
A productive 1:1 helps managers understand what is happening, distinguish individual development needs from organisational constraints, and determine what action is required.
Sometimes the employee needs coaching. Sometimes the manager needs to make a decision. Sometimes the organisation needs to resolve a cross-functional dependency or reconsider how work is prioritised.
The purpose is not simply to have a better conversation.
It is to help people perform, develop, and contribute more effectively by improving the conditions within which they work.
This article explains how managers can build that practice through a reusable meeting agenda, practical questions, the SBI feedback model, difficult conversations, performance alignment, and effective follow-through.
What Are One on One Meetings? And What They Are Not One on one meetings are scheduled conversations between a manager and an individual team member. They provide a dedicated opportunity to discuss work, expectations, feedback, challenges and professional growth.
Their value comes from understanding the individual behind the performance numbers. Two employees working on the same initiative may have very different experiences, responsibilities and support requirements.
For example, one employee may be struggling because another department has not provided essential information. Another may be ready to handle a larger responsibility but lacks the confidence to take the next step.
A common team update may not uncover either issue. A focused 1:1 can.
The difference between a 1:1 and other management meetings Meeting type Primary focus Expected outcome Project status meeting Deliverables, timelines and dependencies Updated project information Team meeting Coordination and shared priorities Collective decisions Performance review Results and behaviour over a review period Formal performance assessment Daily stand-up Immediate work coordination Short-term execution clarity One on one meeting Individual effectiveness and development Resolved concerns and agreed actions
Consider an employee who misses a delivery commitment. A status meeting records the delay and asks for a revised date.
A useful 1:1 investigates whether the cause is unclear ownership, competing priorities, delayed decisions, insufficient capability or a lack of support.
That distinction changes the manager’s response. Instead of repeatedly asking when the work will be completed, the manager can identify what needs to change for the employee to deliver it.
Why One on One Meetings Fail: Six Common Management Mistakes Organisations can have recurring 1:1 meetings on every manager’s calendar and still see little improvement in employee performance.
The problem usually lies in how managers approach these conversations. A meeting becomes ineffective when it collects information without producing better decisions or stronger working relationships.
1. Turning every conversation into a status update Employees spend the meeting explaining completed tasks, pending work and delivery dates. There is little time to discuss what is affecting their effectiveness.
Managers should review routine project information before the meeting and use conversation time for issues that require individual attention.
2. The manager controls the entire agenda When managers decide every discussion point, employees have limited opportunity to raise their own concerns.
Share the agenda in advance and invite employees to add topics. This creates shared ownership without removing the manager’s responsibility to address important performance matters.
3. Cancelling meetings repeatedly An occasional rescheduling may be unavoidable. Repeated cancellations, however, communicate that individual development and employee concerns are less important than other management activities.
Protect the recurring meeting time and reschedule promptly when necessary.
4. Giving feedback without specific examples Statements such as improve your communication or show more ownership do not explain what behaviour needs to change.
Managers should describe observable actions, explain their impact and discuss the expected behaviour.
5. Avoiding difficult conversations Managers sometimes postpone discussions about missed commitments, poor collaboration or declining performance because they do not want to create discomfort.
Avoidance allows small issues to become recurring problems. Address concerns early, using evidence and a constructive tone.
6. Failing to follow up Employees may raise a concern, receive an assurance and discover that nothing changes.
Every important discussion should result in a clear decision, an assigned owner or an agreed next step. Trust grows when employees see that their concerns lead to action.
What Is the 1:1 Revealing: An Employee Performance Issue or an Organisational Constraint? One of the most important management capabilities is distinguishing between an individual performance concern and the organisational conditions influencing it.
Consider an employee who repeatedly misses delivery commitments.
The manager may initially conclude that the employee needs stronger planning skills, greater ownership, or better time management.
However, a focused one-on-one conversation may reveal several different explanations.
Performance condition What the manager should examine Appropriate response Capability gap Does the employee have the knowledge and skills required to perform the work? Coaching, practical learning, feedback, or development support Unclear expectations Does the employee understand the intended outcome and their responsibilities? Clarify expectations, priorities, and success criteria Excessive workload Are the employee’s commitments realistic given available capacity? Reprioritise work, adjust commitments, or redistribute responsibilities Decision constraint Is progress dependent on authority or approval the employee does not have? Make the decision, clarify authority, or escalate appropriately Cross-functional dependency Does another team or stakeholder control an essential input? Coordinate with the relevant owner and resolve the dependency Individual accountability concern Has the employee failed to fulfil reasonable responsibilities despite clear expectations and appropriate support? Address the specific performance concern and agree on improvement actions Recurring organisational problem Are similar concerns appearing across several employees or teams? Examine the wider management, execution, or performance system
The same visible performance gap can require very different management responses.
An employee who needs to develop a capability may benefit from coaching. An employee who is waiting for a management decision may need the manager to intervene. An employee receiving conflicting priorities from several stakeholders may need leadership to resolve the underlying trade-off. These conditions can also exist together.
An employee may need to improve how they communicate delivery risks, while the manager needs to address unrealistic commitments or unresolved dependencies.
Ask What Is Within the Employee’s Ability to Influence A useful management question is:
What can the employee reasonably change, and what requires action from the manager or the organisation?
This question helps managers avoid two common mistakes.
The first is taking responsibility for every problem and creating unnecessary employee dependence.
The second is asking employees to solve problems that require authority, resources, or organisational changes beyond their control.
An effective one-on-one meeting should clarify both individual and managerial responsibilities.
When a concern repeatedly appears across several conversations, managers should also consider whether the problem requires a broader organisational response.
The purpose of the conversation is not to assign every problem to the employee. It is to identify the appropriate owner and response for the condition affecting performance.
A 30-Minute Agenda Managers Can Reuse A useful one-on-one meeting agenda provides structure without making the conversation mechanical. The employee should have meaningful input into the agenda, while the manager remains responsible for addressing important performance concerns, providing appropriate support, and following through on commitments. The following 30-minute format provides a practical starting point for recurring conversations. Time Discussion area What the conversation should achieve 0–5 minutes Employee check-in and previous commitments Understand the employee’s current situation and review important outstanding actions 5–15 minutes Priorities, workload, and blockers Identify the conditions affecting performance and determine where support or decisions are required 15–25 minutes Feedback and development Exchange specific feedback, recognise contributions, and discuss meaningful development opportunities 25–30 minutes Decisions, responsibilities, and follow-up Agree on employee and manager commitments, ownership, and review dates
The agenda should remain flexible. Some conversations may require more time for a difficult performance concern, a development discussion, or a significant change in the employee’s responsibilities. Other conversations may focus primarily on a decision or organisational constraint that needs immediate attention. The objective is not to complete every agenda item in every meeting. It is to use the available time for the discussion that matters most while ensuring that important topics are not repeatedly postponed. First 5 minutes: Understand the employee’s current situation Start with an open question about how the employee is experiencing the week. Avoid beginning with a list of pending tasks.
Ask what is taking most of their attention, what has gone well and whether anything is making work difficult.
If an employee mentions workload pressure, understand the volume of work and competing priorities before advising them to manage time better.
The purpose is to listen and understand, not immediately judge or solve.
Next 10 minutes: Examine priorities and blockers Ask the employee to identify the outcomes that matter most and explain where progress is getting delayed.
Suppose an employee cannot complete a product release because the testing team has not confirmed the required inputs. Asking them to follow up again may not solve the problem.
The manager should clarify who owns the dependency, what decision is pending and whether the delivery commitment needs to change.
Next 10 minutes: Discuss feedback and development Choose one or two topics that could improve the employee’s effectiveness. These may include collaboration, decision-making, communication, technical capability or readiness for greater responsibility.
Avoid presenting a long list of improvement areas. Discuss specific observations and give the employee an opportunity to explain their perspective.
Final 5 minutes: Close with clear commitments Summarise the decisions and agree on who will take each action.
For example, the manager may resolve a cross-functional dependency, while the employee prepares a revised delivery plan. Both should know when the next update is expected.
A conversation becomes useful when it changes what happens after the meeting.
Reusable One-on-One Meeting Template The following template helps managers and employees prepare for recurring conversations and maintain continuity between meetings.
Meeting field What to capture Employee, manager, and date Meeting participants and discussion date Employee agenda Topics the employee would like to discuss Previous commitments Outstanding employee and manager actions Current priorities Important outcomes and responsibilities Workload and execution conditions Capacity concerns, competing priorities, dependencies, or decision constraints Feedback and recognition Specific observations, employee perspectives, and contributions Development focus Capabilities to strengthen and opportunities to apply them Decisions required Issues that require managerial or organisational action Agreed actions Employee commitments, manager commitments, and other actions Ownership and review date Who will act, what is expected, and when progress will be reviewed
A separate action record can help maintain clarity.
Agreed action Owner Expected date Evidence of progress Resolve the outstanding cross-functional approval Manager Agreed date Decision obtained or escalation path established Update the delivery plan following the decision Employee Agreed date Revised commitments communicated Prepare for a stakeholder presentation Employee and manager Agreed date Preparation completed and feedback provided
The examples above are illustrative.
Managers should review outstanding commitments before each meeting and avoid repeatedly transferring unresolved organisational problems back to the employee.
Meeting notes should capture information necessary for effective follow-through rather than become a detailed record of every personal discussion.
Where sensitive matters arise, managers should follow applicable confidentiality, access, retention, and organisational reporting requirements.
The template should support a useful conversation, not become another administrative reporting obligation.
How often should managers hold 1:1 meetings? The right frequency depends on the employee’s experience, role and current working conditions.
Employee or work context Suggested frequency New employees Weekly Employees taking on new responsibilities Weekly or fortnightly Teams undergoing major change Weekly Experienced employees with stable responsibilities Fortnightly Senior professionals with high autonomy Fortnightly or monthly
These are starting points rather than fixed rules. Managers should adjust frequency when responsibilities change, delivery pressure increases or an employee needs additional support.
Consistency matters more than scheduling frequent meetings that have no clear purpose.
Questions to Ask, Grouped by Purpose The quality of one on one meetings depends on the questions managers ask and how carefully they listen to the answers.
A useful question should encourage the employee to explain a situation rather than provide a quick yes or no response. Managers should select questions based on the employee’s current needs instead of following a fixed questionnaire.
Check-in and wellbeing These questions help managers understand how employees are experiencing their work.
How has your workload been this week? What has been the most positive part of your work recently? Is anything affecting your ability to concentrate or perform? Do you have the support required to manage your responsibilities? If an employee says the workload is becoming difficult, understand the situation before recommending a solution. There may be competing priorities, unrealistic deadlines or responsibilities that have gradually accumulated.
The manager should also respect personal boundaries. Employees do not need to disclose private information to receive appropriate workplace support.
Blockers and priorities These questions help managers connect individual work with execution.
What are the most important outcomes you need to deliver? Which task is taking longer than expected? Are you waiting for a decision or input from another team? Are your priorities clear, or are you receiving conflicting requests? What decision could I help you make? A missed deadline does not always indicate poor employee performance. It may reflect unclear decision rights, delayed approvals or dependencies outside the employee’s control.
Managers should investigate the underlying cause before deciding what corrective action is appropriate.
Career growth and development Development questions help employees connect current responsibilities with future aspirations.
Which part of your role would you like to become better at? What responsibility would you like to take on next? Is there a skill you have not had enough opportunity to practise? What kind of assignment would help you prepare for your next career step? Managers should connect these discussions to practical opportunities. An employee who wants to improve stakeholder management, for example, could lead an upcoming cross-functional review with coaching and feedback afterwards.
Development becomes meaningful when the employee gets an opportunity to apply what they learn.
Giving Feedback in a 1:1 With the SBI Model Feedback is an essential part of effective people management skills . However, vague feedback often creates confusion because employees are told what is wrong without understanding which behaviour needs to change.
The SBI feedback model provides a straightforward way to make feedback specific and constructive.
SBI stands for:
Situation: Identify when and where the behaviour occurred. Behaviour: Describe the observable action without assuming intent. Impact: Explain the effect on the team, customer or business outcome. Applying SBI to a workplace situation Consider an employee who repeatedly misses delivery commitments.
A vague comment might be that the employee needs to become more responsible. This describes a judgement, not the behaviour that needs attention.
An SBI-based conversation could sound like this:
During the last two sprint reviews, the agreed delivery dates changed without an early update. This left the testing team with limited time to prepare and created additional pressure before release.
The manager can then ask what caused the delays and whether the employee had enough clarity, support and decision-making authority.
This creates room for an honest discussion without immediately assigning blame.
Using SBI for positive feedback SBI is also useful for recognising effective behaviour.
During the customer escalation meeting, you summarised the client’s concerns and helped the engineering team agree on a response. This prevented the discussion from becoming defensive and helped the team move towards a resolution.
Specific recognition tells employees which behaviours contribute to stronger outcomes.
What SBI Cannot Replace: Understanding, Dialogue, and Action The SBI feedback model helps managers describe a specific situation, observable behaviour, and its impact.
However, it does not automatically establish why the behaviour occurred or what action will improve performance.
Consider the following feedback:
Situation: During the last two sprint reviews.
Behaviour: The agreed delivery dates changed without an early update.
Impact: The testing team had limited time to prepare, creating additional pressure before release.
This provides a specific starting point for discussion.
The manager should then invite the employee’s perspective.
What was happening when the delivery dates changed? When did the employee become aware of the risk? Were expectations about communicating delays clear? Did the employee have access to the information and authority required to act?
The answers may reveal an individual communication gap, an unclear escalation process, a dependency outside the employee’s control, or several contributing conditions.
The appropriate response should follow that understanding.
The employee may need to communicate emerging risks earlier. The manager may need to clarify escalation expectations or resolve a dependency. Both may need to change how delivery commitments are reviewed.
A useful feedback conversation therefore includes:
Specific observations rather than assumptions about personality or intent. An opportunity for the employee to explain their perspective. A shared understanding of the expected behaviour and relevant performance conditions. Appropriate employee and manager commitments. Follow-up to establish whether the agreed changes are helping. The same principles apply to positive feedback.
Recognising a specific contribution helps employees understand what they did effectively and how that behaviour supported the intended outcome.
SBI makes feedback more specific. Effective management dialogue determines what the feedback means and what should happen next.
Organisations can strengthen these capabilities through practical delegation and feedback workshops that help managers develop their ability to set expectations, listen, coach, provide feedback, and support employee ownership.
Handling Difficult Conversations During One on One Meetings Not every 1:1 conversation will be comfortable. Managers may need to discuss repeated missed commitments, disagreements about performance , declining motivation or expectations that cannot currently be met.
Avoiding these discussions can create uncertainty for both sides. The manager may assume that the employee understands the problem, while the employee may have no clear idea of what needs to change.
A productive conversation should separate the observed issue from assumptions about the person.
When an employee disagrees with feedback Do not treat disagreement as resistance. Ask which part of the feedback the employee sees differently and invite examples.
Compare the available evidence before deciding on an action. The objective is to establish a shared understanding, not to win an argument.
When an employee repeatedly misses commitments Examine the pattern rather than discussing only the latest missed deadline.
Check whether priorities are realistic, responsibilities are clear and the employee has the capability and resources to deliver. If expectations have been understood and support is available, agree on specific performance improvements and review dates.
When an employee feels overwhelmed Understand what is creating the pressure. It could be excessive workload, unclear priorities, stakeholder demands or responsibilities outside the employee’s role.
The manager may need to reprioritise work, redistribute responsibilities or resolve a dependency. Asking the employee to work harder will not fix a structural problem.
When an employee wants a promotion Acknowledge the aspiration and discuss the capabilities required for the next role.
Be clear about current opportunities and organisational constraints. Agree on development actions that can demonstrate readiness rather than making promises about promotion timelines.
When should a manager coach or intervene? Managers should not solve every problem on behalf of employees. Doing so can reduce ownership and create unnecessary dependence.
Coach when the employee has the capability to explore solutions. Intervene when the issue requires managerial authority, cross-functional coordination or a decision the employee cannot make independently.
Provide direction when responsibilities or expectations are unclear. Escalate concerns involving serious risk or formal organisational processes through the appropriate channels.
Connecting 1:1s to OKRs and Performance Reviews One on one meetings become more valuable when individual responsibilities are connected to organisational priorities.
This does not mean every conversation should become an OKR review. The manager should understand whether the employee has the clarity, capability and support required to contribute to agreed outcomes.
Connect individual priorities to OKRs Suppose an organisation has an objective to improve customer retention.
A product team may contribute through better reliability, faster issue resolution and improved customer communication. Each employee has a different responsibility within that objective.
During a 1:1, the manager can ask which key result the employee’s work supports, what could affect their contribution and whether any current activity is consuming time without improving the intended outcome.
This helps employees understand why their work matters. It also helps managers identify misalignment before it affects business results.
Not every employee responsibility needs to map directly to an individual Key Result.
Employees may contribute through shared team outcomes, essential operational responsibilities, risk management, customer support, or capabilities that enable future performance.
The purpose of connecting one-on-one conversations to OKRs is to improve understanding of priorities and contribution, not to force every task or individual responsibility into an OKR structure .
Managers should also recognise when an employee’s contribution depends on outcomes, decisions, or resources controlled by others.
Use 1:1s to identify execution risks Consider an employee responsible for reducing customer response time. Their progress may be affected by delayed approvals, unclear escalation authority or poor coordination between departments.
A regular conversation can uncover these issues before they become visible in the performance dashboard.
The manager can then clarify ownership, resolve dependencies or escalate decisions that require leadership involvement.
Make performance reviews a continuation of regular conversations Formal performance reviews should not introduce unexpected feedback.
Managers can use recurring 1:1s to document contributions, discuss challenges, recognise effective behaviour and track development goals.
This creates a more balanced review because performance is considered across the review period rather than judged mainly on recent events.
A consistent management rhythm connects individual conversations with team reviews, planning cycles and performance discussions without creating unnecessary reporting activity.
How One-on-One Meetings Fit Into the Enterprise Performance System One-on-one meetings are an important part of continuous performance management .
They help managers and employees connect expectations, performance evidence, feedback, development, and action.
However, their effectiveness also depends on the wider organisational system.
An employee may understand their goals but lack the resources required to achieve them. A manager may identify an execution constraint but lack the authority to resolve it. A team may receive useful feedback while competing organisational priorities remain unchanged.
These conditions extend beyond the quality of the individual conversation.
Performance architecture provides a way to understand how strategic priorities, goals, execution conditions, capability, evidence, accountability, and management decisions influence one another.
Within this architecture, one-on-one meetings provide an opportunity to understand how the system is experienced by individual employees.
They can reveal where expectations are unclear, where development support is needed, and where organisational conditions are preventing effective performance.
The manager can then determine the appropriate response.
Some issues require individual coaching or feedback. Others require management decisions, cross-functional coordination, or broader organisational action.
When similar concerns recur across several employees or teams, the organisation should examine whether its existing performance mechanisms are contributing to the problem.
One-on-one meetings should therefore connect with team management practices, continuous performance management, and appropriate leadership decision-making.
The conversation helps reveal what is happening. The wider performance system must provide the ability to respond.
Skip Level Meetings: When and How to Run Them A skip level meeting is a conversation between an employee and a manager who is two or more levels above them in the organisational hierarchy.
For example, a team member may meet a department head directly without their immediate manager participating.
These meetings give senior leaders a different perspective on how work is progressing across the organisation. They can reveal communication gaps, structural barriers and employee concerns that may not reach leadership through normal reporting channels.
When should organisations conduct skip-level meetings? Skip-level meetings are useful during organisational transformation , restructuring, persistent execution problems or periods when senior leaders need a clearer view of employee experience.
They can also help leadership understand whether priorities are clear, decisions are being made at the right level and teams have the resources required to deliver.
However, these meetings should not become a way to bypass managers or create competing reporting structures.
A practical skip-level meeting agenda Time Discussion Purpose 0 to 5 minutes Introduction and context Explain the purpose of the discussion 5 to 15 minutes Employee experience Understand what supports or affects performance 15 to 25 minutes Organisational barriers Identify issues involving decisions and coordination 25 to 30 minutes Closing and follow-up Confirm themes and next steps
Senior leaders can ask what is working well, where employees experience friction, whether organisational priorities are clear and what leadership could improve.
Questions should invite honest observations rather than encourage employees to criticise their immediate managers.
Handle Sensitive Feedback Responsibly Skip-level meetings can help senior leaders understand employee experiences and organisational barriers that may not be visible through regular management reporting.
However, they also create responsibilities around trust, confidentiality, and appropriate action.
Before the conversation, explain its purpose, how information may be used, and the limits of confidentiality.
Employees should understand that some concerns, particularly those involving safety, harassment, discrimination, serious misconduct, or legal obligations, may require action through formal organisational processes.
If an employee raises a concern about their immediate manager, the senior leader should listen carefully, clarify the nature of the issue, and avoid making assumptions or promising an outcome before the relevant facts have been examined.
Employees should not experience retaliation for raising legitimate concerns or using appropriate reporting channels.
Where a concern requires formal investigation, the senior leader should follow the organisation’s established procedures rather than attempt to resolve it through an informal management conversation alone.
Skip-level meetings should complement, not replace, appropriate grievance, safeguarding, ethics, or employee reporting mechanisms.
Distinguish Individual Concerns From Organisational Patterns One employee’s experience may identify an important issue that requires attention.
However, an individual observation does not automatically establish that the same problem exists across the organisation.
Senior leaders should examine relevant evidence, consider other perspectives where appropriate, and distinguish between individual concerns, management capability issues, and recurring organisational constraints.
For example, several employees may report that important decisions are repeatedly delayed.
Rather than treating each concern as a separate management problem, leadership can examine whether unclear decision rights, approval arrangements, or cross-functional dependencies are contributing to the pattern.
This creates a connection between employee feedback and organisational improvement.
Close the Feedback Loop Without Compromising Trust Skip-level meetings lose credibility when employees repeatedly share concerns without seeing an appropriate response.
Senior leaders should establish which issues require action, assign responsibility, and communicate relevant progress where possible.
Not every concern can be resolved immediately. Some may require investigation, changes to organisational priorities, or decisions involving several functions.
Employees should receive appropriate acknowledgement and follow-up without compromising another person’s privacy or the integrity of a formal process.
When sharing broader themes with management teams, leaders should protect sensitive information and avoid identifying individual employees unnecessarily.
The objective is not to collect more feedback or create an alternative reporting hierarchy.
It is to improve leadership’s understanding of the organisation and strengthen its ability to respond to the conditions affecting people and performance.
Running One-on-One Meetings in Hierarchy-Conscious Workplaces In some Indian organisations, as in workplaces across many countries, designation, seniority, reporting relationships, and established management practices can influence how employees communicate with leaders.
The extent of this influence varies across organisations, teams, industries, and individuals.
A team member may agree to a deadline despite recognising that it is unrealistic. An employee may hesitate to question a senior stakeholder’s decision. Another may raise a concern privately but avoid discussing it during a larger review.
These behaviours do not necessarily indicate a lack of ownership or willingness to contribute.
They may reflect previous experiences, uncertainty about how disagreement will be received, or a belief that raising a concern will not lead to useful action.
Managers should therefore avoid interpreting silence as agreement or the absence of complaints as evidence that everything is working well.
One-on-one meetings can provide a useful opportunity to understand concerns that employees may not feel comfortable raising in a larger setting.
However, trust depends on more than inviting employees to speak.
Managers need to demonstrate through their responses that respectful disagreement, early risk communication, and constructive feedback are welcome.
The objective is not to eliminate appropriate organisational authority. It is to create management relationships in which employees can communicate honestly, exercise appropriate judgement, and raise concerns without unnecessary fear.
Create space for employees to speak honestly Instead of asking whether everyone agrees with a decision, ask what risks the team may be overlooking.
When an employee raises a concern, explore the issue before defending the existing approach. Consistent responses help employees understand that respectful disagreement is acceptable.
This is an important part of building psychological safety at work .
Do not interpret silence as commitment If an employee accepts a deadline, ask what dependencies and resources are required to meet it.
If a team member agrees with a proposed decision, invite them to identify any risks they may have noticed. These questions create opportunities to discuss concerns without forcing employees into confrontation.
Managers should also share the agenda before the meeting and give employees time to prepare difficult topics.
Adapt the conversation to the individual Some employees prefer direct discussion, while others are more comfortable sharing written points before a meeting. New employees may need more guidance, while experienced professionals may benefit from a coaching-oriented approach.
Managers should adapt their communication style without lowering expectations around accountability and performance.
Structured leadership training for managers can help build the listening, coaching, delegation and feedback capabilities required to lead different teams effectively.
Maintain the same quality in remote and hybrid teams Remote employees can become disconnected when most interactions focus on task allocation and virtual status reviews.
Managers should protect recurring 1:1 time, use a private communication channel and avoid multitasking during conversations.
Share action summaries after the meeting and follow up on concerns that require coordination across locations. The objective is to maintain the quality of the relationship, not simply complete another calendar appointment.
How to Measure Whether Your One-on-One Meetings Are Working A manager may complete every scheduled one-on-one meeting and still fail to improve employee effectiveness.
Meeting completion indicates that the conversation took place. It does not establish whether employees received useful support, managers acted on their commitments, or performance conditions improved.
A more useful approach examines the quality of the conversation, the actions it produces, and the outcomes those actions are intended to influence.
Six Areas to Examine Measurement area Management question Possible evidence Meeting consistency Are employees receiving regular, appropriate opportunities for individual conversations? Meeting continuity and rescheduling patterns Conversation usefulness Do employees find the discussions relevant, supportive, and constructive? Employee feedback and examples of useful discussions Manager follow-through Are managers completing commitments that require their action or authority? Progress against manager-owned actions and unresolved decisions Issue resolution Are the conditions affecting employee performance being addressed? Resolution of blockers, recurring issues, and escalation outcomes Development progress Are employees receiving meaningful opportunities to build and apply capabilities? Demonstrated learning, practical assignments, feedback, and development progress Performance conditions Are relevant aspects of work becoming clearer or more effective? Changes in priority clarity, workload, decision waiting, collaboration, or relevant delivery outcomes
These indicators should be interpreted in context.
For example, an increase in concerns raised during one-on-one meetings may indicate that employees feel more comfortable discussing problems.
A reduction in reported concerns does not automatically establish that performance conditions have improved. Employees may also stop raising issues when previous discussions have not led to meaningful action.
Similarly, completing an agreed action does not necessarily establish that the underlying problem has been resolved.
A manager may escalate a dependency on time while the decision itself remains outstanding.
The relevant question is whether the action has improved the condition affecting performance.
Review Recurring Organisational Constraints At regular intervals, managers should examine whether similar concerns appear across several employee conversations.
For example:
Several employees report competing priorities. Multiple team members are waiting for the same cross-functional decision. Development commitments are repeatedly postponed because delivery workloads leave insufficient capacity. Employees raise similar concerns about unclear expectations or conflicting responsibilities. These patterns may indicate a management or organisational constraint rather than separate individual performance problems.
Managers should examine the evidence and determine whether the appropriate response involves their own management practices, coordination with other teams, or escalation to leadership.
Sensitive individual information should not be unnecessarily shared when discussing broader organisational themes.
Avoid Turning One-on-One Meetings Into Another Measurement Burden The purpose of measuring one-on-one effectiveness is to improve management practice, not to create a new employee surveillance system.
Organisations should avoid evaluating managers solely on meeting completion rates, the number of concerns recorded, or the percentage of actions closed.
Such measures can encourage superficial compliance, premature action closure, or reluctance to discuss difficult issues.
Where performance outcomes are examined, leaders should recognise that many factors influence those outcomes. Improvements in delivery, retention, or employee effectiveness should not automatically be attributed to one-on-one meetings alone.
The most useful review asks:
Are these conversations helping employees and managers identify important performance conditions, take appropriate action, and learn whether that action is making a difference?
If the answer is yes, one-on-one meetings are becoming a meaningful part of the organisation’s performance system rather than another recurring management activity.
Conclusion: Better One-on-One Meetings Should Lead to Better Management One-on-one meetings are valuable when they help managers and employees understand performance, build trust, exchange useful feedback, and improve the conditions in which work gets done.
A recurring calendar invitation does not guarantee a meaningful management conversation.
If the time is used only to collect status updates, employees may experience the meeting as another reporting requirement.
If concerns are discussed but important commitments are repeatedly left unresolved, employees may gradually lose confidence in the value of the conversation.
Effective one-on-one meetings create space for employee perspectives, recognition, feedback, development, and appropriate management action.
Sometimes the employee needs coaching or capability development.
Sometimes the manager needs to clarify expectations, resolve competing priorities, or make a decision.
Sometimes the organisation needs to address a wider execution or performance constraint.
The discipline is understanding which response is required.
A practical starting point is to review your last three one-on-one conversations with each direct report.
Consider whether employees had a meaningful opportunity to discuss what mattered to them, whether important concerns received an appropriate response, whether manager and employee commitments were followed through, and whether development discussions created useful opportunities.
Where the same concerns continue to appear, examine why the conditions affecting performance have not changed.
At NextAgile, our consulting perspective connects managerial effectiveness with leadership capability, continuous performance management, execution conditions, and organisational decision-making.
If your managers are conducting regular one-on-one meetings but employees continue to experience unresolved blockers, conflicting priorities, limited development opportunities, or ineffective performance conversations, we can explore what is preventing those conversations from translating into better performance.
The appropriate response may involve manager coaching , leadership development, changes to management practices, or improvements to the wider organisational system. If your managers need to move beyond status reporting and build stronger employee ownership , connect with our team at consult@nextagile.ai to explore how we can support your leadership development priorities.
Frequently Asked Questions 1. How often should managers hold 1:1s with each direct report? Most managers should schedule one on one meetings weekly or fortnightly. Weekly conversations are useful for new employees, changing responsibilities and fast-moving projects. Experienced employees with stable responsibilities may need fortnightly meetings. Consistency and relevance matter more than frequency.
2. Should the employee or the manager own the 1:1 agenda? The employee should have meaningful input because the meeting needs to address their concerns and development needs. The manager remains responsible for maintaining consistency, providing coaching and addressing important performance issues. Shared ownership creates a more balanced conversation.
3. What should you do when an employee has nothing to discuss? Do not force a conversation simply to fill the scheduled time. Ask about current priorities, workload, development or possible improvements. If there are no immediate concerns, use the time for coaching or feedback. You can also finish early while maintaining the regular meeting schedule.
4. Is it fine to cancel a 1:1 when the week is busy? Managers should avoid cancelling recurring 1:1s whenever possible. Repeated cancellations signal that employee development and concerns are not a priority. If a meeting must be postponed, reschedule it promptly and complete any outstanding follow-up actions.
5. How do you run 1:1s with remote or hybrid team members? Use a private video or audio call, share an agenda in advance and avoid multitasking. Give remote employees the same opportunity to discuss concerns, feedback and development as office-based employees. Record agreed actions and follow up between meetings when necessary.
6. What notes should a manager keep after each 1:1? Managers should record key discussion points, decisions, action owners, deadlines and follow-up requirements. Notes should focus on work-related information rather than unnecessary personal details. Keep them confidential, follow organisational data-handling policies and share relevant action summaries with the employee.
Anuj Ojha is Co-Founder & Consulting Head at NextAgile. Anuj has designed & led multiple turnkey transformation journeys across industries, domains & geographies and has 16+ years of experience as an agile practitioner. He has worked with CXOs, CTOs & Key Leaders to translate their business objectives on the ground, contextualizing org transformations and creating buy-in across level, leading a team of coaches/consultants to implement agility across 150+ teams & trained more than 12k team members. Anuj’s core area of interest is business agility & working with leaders & teams to achieve long term sustainable, Agile culture & mindset.