{"id":9180,"date":"2026-11-19T13:21:07","date_gmt":"2026-11-19T07:51:07","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=9180"},"modified":"2026-11-19T13:51:41","modified_gmt":"2026-11-19T08:21:41","slug":"one-on-one-meetings","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/leadership\/one-on-one-meetings\/","title":{"rendered":"One on One Meetings That Build Performance, Not Status Updates"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A practical 30-minute 1:1 meeting agenda includes:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">5 minutes for an employee check-in<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">10 minutes for priorities and blockers<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">10 minutes for feedback and development<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">5 minutes for decisions and follow-up actions<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The employee should contribute to the agenda, while the manager remains responsible for creating a productive conversation and acting on agreed commitments.<\/span><\/p>\n<h2><b>Key Takeaways<\/b><\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">One-on-one meetings should help managers and employees understand performance conditions, not simply duplicate project status reporting.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A flexible 30-minute agenda can balance employee concerns, priorities, feedback, development, and management commitments.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Effective managers distinguish individual capability needs from workload, decision, dependency, and organisational constraints.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The SBI feedback model helps make feedback specific, while dialogue helps establish the appropriate response.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Connecting individual conversations to organisational priorities can reveal execution risks and support meaningful development.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Skip-level meetings can help leaders identify organisational barriers when employee feedback is handled responsibly.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manager follow-through, issue resolution, conversation usefulness, and development progress provide more meaningful evidence than meeting completion alone.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">One-on-one meetings become part of an effective performance system when the organisation can act on the conditions those conversations reveal.<\/span><\/li>\n<\/ul>\n<h2><b>Introduction<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">On paper, the team appears to be under control.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The status meeting has provided visibility into the work. It has not necessarily revealed the conditions affecting the people responsible for delivering it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">One-on-one meetings give managers an opportunity to understand those conditions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They create dedicated space to discuss expectations, workload, capability, feedback, professional development, and the support employees need to perform effectively.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, conducting regular one-on-one meetings does not automatically improve performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The conversations are happening, but the conditions affecting performance remain unchanged.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A productive 1:1 helps managers understand what is happening, distinguish individual development needs from organisational constraints, and determine what action is required.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The purpose is not simply to have a better conversation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It is to help people perform, develop, and contribute more effectively by improving the conditions within which they work.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h2><b>What Are One on One Meetings? And What They Are Not<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A common team update may not uncover either issue. A focused 1:1 can.<\/span><\/p>\n<h3><b>The difference between a 1:1 and other management meetings<\/b><\/h3>\n<table>\n<tbody>\n<tr>\n<td><b>Meeting type<\/b><\/td>\n<td><b>Primary focus<\/b><\/td>\n<td><b>Expected outcome<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Project status meeting<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Deliverables, timelines and dependencies<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Updated project information<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Team meeting<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Coordination and shared priorities<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Collective decisions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Performance review<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Results and behaviour over a review period<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Formal performance assessment<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Daily stand-up<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Immediate work coordination<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Short-term execution clarity<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">One on one meeting<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Individual effectiveness and development<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Resolved concerns and agreed actions<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Consider an employee who misses a delivery commitment. A status meeting records the delay and asks for a revised date.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A useful 1:1 investigates whether the cause is unclear ownership, competing priorities, delayed decisions, insufficient capability or a lack of support.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That distinction changes the manager&#8217;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.<\/span><\/p>\n<h2><b>Why One on One Meetings Fail: Six Common Management Mistakes<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Organisations can have recurring 1:1 meetings on every manager&#8217;s calendar and still see little improvement in employee performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>1. Turning every conversation into a status update<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Employees spend the meeting explaining completed tasks, pending work and delivery dates. There is little time to discuss what is affecting their effectiveness.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should review routine project information before the meeting and use conversation time for issues that require individual attention.<\/span><\/p>\n<h3><b>2. The manager controls the entire agenda<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">When managers decide every discussion point, employees have limited opportunity to raise their own concerns.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Share the agenda in advance and invite employees to add topics. This creates shared ownership without removing the manager&#8217;s responsibility to address important performance matters.<\/span><\/p>\n<h3><b>3. Cancelling meetings repeatedly<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An occasional rescheduling may be unavoidable. Repeated cancellations, however, communicate that individual development and employee concerns are less important than other management activities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Protect the recurring meeting time and reschedule promptly when necessary.<\/span><\/p>\n<h3><b>4. Giving feedback without specific examples<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Statements such as improve your communication or show more ownership do not explain what behaviour needs to change.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should describe observable actions, explain their impact and discuss the expected behaviour.<\/span><\/p>\n<h3><b>5. Avoiding difficult conversations<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Managers sometimes postpone discussions about missed commitments, poor collaboration or declining performance because they do not want to create discomfort.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Avoidance allows small issues to become recurring problems. Address concerns early, using evidence and a constructive tone.<\/span><\/p>\n<h3><b>6. Failing to follow up<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Employees may raise a concern, receive an assurance and discover that nothing changes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h2><b>What Is the 1:1 Revealing: An Employee Performance Issue or an Organisational Constraint?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">One of the most important management capabilities is distinguishing between an individual performance concern and the organisational conditions influencing it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Consider an employee who repeatedly misses delivery commitments.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager may initially conclude that the employee needs stronger planning skills, greater ownership, or better time management.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, a focused one-on-one conversation may reveal several different explanations.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Performance condition<\/b><\/td>\n<td><b>What the manager should examine<\/b><\/td>\n<td><b>Appropriate response<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Capability gap<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does the employee have the knowledge and skills required to perform the work?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Coaching, practical learning, feedback, or development support<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Unclear expectations<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does the employee understand the intended outcome and their responsibilities?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Clarify expectations, priorities, and success criteria<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Excessive workload<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are the employee&#8217;s commitments realistic given available capacity?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Reprioritise work, adjust commitments, or redistribute responsibilities<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Decision constraint<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Is progress dependent on authority or approval the employee does not have?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Make the decision, clarify authority, or escalate appropriately<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Cross-functional dependency<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does another team or stakeholder control an essential input?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Coordinate with the relevant owner and resolve the dependency<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Individual accountability concern<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Has the employee failed to fulfil reasonable responsibilities despite clear expectations and appropriate support?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Address the specific performance concern and agree on improvement actions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Recurring organisational problem<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are similar concerns appearing across several employees or teams?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Examine the wider management, execution, or performance system<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">The same visible performance gap can require very different management responses.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">An employee who needs to develop a capability may benefit from coaching.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">An employee who is waiting for a management decision may need the manager to intervene.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">An employee receiving conflicting priorities from several stakeholders may need leadership to resolve the underlying trade-off.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">These conditions can also exist together.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An employee may need to improve how they communicate delivery risks, while the manager needs to address unrealistic commitments or unresolved dependencies.<\/span><\/p>\n<h3><b>Ask What Is Within the Employee&#8217;s Ability to Influence<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A useful management question is:<\/span><\/p>\n<p><b>What can the employee reasonably change, and what requires action from the manager or the organisation?<\/b><\/p>\n<p><span style=\"font-weight: 400;\">This question helps managers avoid two common mistakes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The first is taking responsibility for every problem and creating unnecessary employee dependence.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The second is asking employees to solve problems that require authority, resources, or organisational changes beyond their control.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An effective one-on-one meeting should clarify both individual and managerial responsibilities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When a concern repeatedly appears across several conversations, managers should also consider whether the problem requires a broader organisational response.<\/span><\/p>\n<p><b>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.<\/b><\/p>\n<h2><b>A 30-Minute Agenda Managers Can Reuse<\/b><\/h2>\n<h3><span style=\"font-weight: 400;\">A useful one-on-one meeting agenda provides structure without making the conversation mechanical.<\/span><\/h3>\n<h3><span style=\"font-weight: 400;\">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.<\/span><\/h3>\n<h3><span style=\"font-weight: 400;\">The following 30-minute format provides a practical starting point for recurring conversations.<\/span><\/h3>\n<table>\n<tbody>\n<tr>\n<td>\n<h3><span style=\"font-weight: 400;\">Time<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Discussion area<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">What the conversation should achieve<\/span><\/h3>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3><span style=\"font-weight: 400;\">0\u20135 minutes<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Employee check-in and previous commitments<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Understand the employee&#8217;s current situation and review important outstanding actions<\/span><\/h3>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3><span style=\"font-weight: 400;\">5\u201315 minutes<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Priorities, workload, and blockers<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Identify the conditions affecting performance and determine where support or decisions are required<\/span><\/h3>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3><span style=\"font-weight: 400;\">15\u201325 minutes<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Feedback and development<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Exchange specific feedback, recognise contributions, and discuss meaningful development opportunities<\/span><\/h3>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3><span style=\"font-weight: 400;\">25\u201330 minutes<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Decisions, responsibilities, and follow-up<\/span><\/h3>\n<\/td>\n<td>\n<h3><span style=\"font-weight: 400;\">Agree on employee and manager commitments, ownership, and review dates<\/span><\/h3>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span style=\"font-weight: 400;\">The agenda should remain flexible.<\/span><\/h3>\n<h3><span style=\"font-weight: 400;\">Some conversations may require more time for a difficult performance concern, a development discussion, or a significant change in the employee&#8217;s responsibilities.<\/span><\/h3>\n<h3><span style=\"font-weight: 400;\">Other conversations may focus primarily on a decision or organisational constraint that needs immediate attention.<\/span><\/h3>\n<h3><span style=\"font-weight: 400;\">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.<\/span><\/h3>\n<h3><b>First 5 minutes: Understand the employee&#8217;s current situation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Start with an open question about how the employee is experiencing the week. Avoid beginning with a list of pending tasks.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ask what is taking most of their attention, what has gone well and whether anything is making work difficult.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If an employee mentions workload pressure, understand the volume of work and competing priorities before advising them to manage time better.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The purpose is to listen and understand, not immediately judge or solve.<\/span><\/p>\n<h3><b>Next 10 minutes: Examine priorities and blockers<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Ask the employee to identify the outcomes that matter most and explain where progress is getting delayed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager should clarify who owns the dependency, what decision is pending and whether the delivery commitment needs to change.<\/span><\/p>\n<h3><b>Next 10 minutes: Discuss feedback and development<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Choose one or two topics that could improve the employee&#8217;s effectiveness. These may include collaboration, decision-making, communication, technical capability or readiness for greater responsibility.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Avoid presenting a long list of improvement areas. Discuss specific observations and give the employee an opportunity to explain their perspective.<\/span><\/p>\n<h3><b>Final 5 minutes: Close with clear commitments<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Summarise the decisions and agree on who will take each action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A conversation becomes useful when it changes what happens after the meeting.<\/span><\/p>\n<h3><b>Reusable One-on-One Meeting Template<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The following template helps managers and employees prepare for recurring conversations and maintain continuity between meetings.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Meeting field<\/b><\/td>\n<td><b>What to capture<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Employee, manager, and date<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Meeting participants and discussion date<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Employee agenda<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Topics the employee would like to discuss<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Previous commitments<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Outstanding employee and manager actions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Current priorities<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Important outcomes and responsibilities<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Workload and execution conditions<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Capacity concerns, competing priorities, dependencies, or decision constraints<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Feedback and recognition<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Specific observations, employee perspectives, and contributions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Development focus<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Capabilities to strengthen and opportunities to apply them<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Decisions required<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Issues that require managerial or organisational action<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Agreed actions<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Employee commitments, manager commitments, and other actions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ownership and review date<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Who will act, what is expected, and when progress will be reviewed<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">A separate action record can help maintain clarity.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Agreed action<\/b><\/td>\n<td><b>Owner<\/b><\/td>\n<td><b>Expected date<\/b><\/td>\n<td><b>Evidence of progress<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Resolve the outstanding cross-functional approval<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Manager<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Agreed date<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Decision obtained or escalation path established<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Update the delivery plan following the decision<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Employee<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Agreed date<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Revised commitments communicated<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Prepare for a stakeholder presentation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Employee and manager<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Agreed date<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Preparation completed and feedback provided<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">The examples above are illustrative.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should review outstanding commitments before each meeting and avoid repeatedly transferring unresolved organisational problems back to the employee.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Meeting notes should capture information necessary for effective follow-through rather than become a detailed record of every personal discussion.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Where sensitive matters arise, managers should follow applicable confidentiality, access, retention, and organisational reporting requirements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The template should support a useful conversation, not become another administrative reporting obligation.<\/span><\/p>\n<h3><b>How often should managers hold 1:1 meetings?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The right frequency depends on the employee&#8217;s experience, role and current working conditions.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Employee or work context<\/b><\/td>\n<td><b>Suggested frequency<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">New employees<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Weekly<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Employees taking on new responsibilities<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Weekly or fortnightly<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Teams undergoing major change<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Weekly<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Experienced employees with stable responsibilities<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Fortnightly<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Senior professionals with high autonomy<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Fortnightly or monthly<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">These are starting points rather than fixed rules. Managers should adjust frequency when responsibilities change, delivery pressure increases or an employee needs additional support.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Consistency matters more than scheduling frequent meetings that have no clear purpose.<\/span><\/p>\n<h2><b>Questions to Ask, Grouped by Purpose<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The quality of one on one meetings depends on the questions managers ask and how carefully they listen to the answers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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&#8217;s current needs instead of following a fixed questionnaire.<\/span><\/p>\n<h3><b>Check-in and wellbeing<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">These questions help managers understand how employees are experiencing their work.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How has your workload been this week?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What has been the most positive part of your work recently?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Is anything affecting your ability to concentrate or perform?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Do you have the support required to manage your responsibilities?<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager should also respect personal boundaries. Employees do not need to disclose private information to receive appropriate workplace support.<\/span><\/p>\n<h3><b>Blockers and priorities<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">These questions help managers connect individual work with execution.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What are the most important outcomes you need to deliver?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which task is taking longer than expected?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are you waiting for a decision or input from another team?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are your priorities clear, or are you receiving conflicting requests?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What decision could I help you make?<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">A missed deadline does not always indicate poor employee performance. It may reflect unclear decision rights, delayed approvals or dependencies outside the employee&#8217;s control.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should investigate the underlying cause before deciding what corrective action is appropriate.<\/span><\/p>\n<h3><b>Career growth and development<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Development questions help employees connect current responsibilities with future aspirations.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which part of your role would you like to become better at?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What responsibility would you like to take on next?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Is there a skill you have not had enough opportunity to practise?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What kind of assignment would help you prepare for your next career step?<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Development becomes meaningful when the employee gets an opportunity to apply what they learn.<\/span><\/p>\n<h2><b>Giving Feedback in a 1:1 With the SBI Model<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Feedback is an essential part of <\/span><a href=\"https:\/\/rework.withgoogle.com\/intl\/en\/guides\/following-the-data-the-research-behind-great-managers\" rel=\"nofollow noopener\" target=\"_blank\"><span style=\"font-weight: 400;\">effective people management skills<\/span><\/a><span style=\"font-weight: 400;\">. However, vague feedback often creates confusion because employees are told what is wrong without understanding which behaviour needs to change.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><a href=\"https:\/\/www.ccl.org\/articles\/leading-effectively-articles\/sbi-feedback-model-a-quick-win-to-improve-talent-conversations-development\/\" rel=\"nofollow noopener\" target=\"_blank\"><span style=\"font-weight: 400;\">SBI feedback model<\/span><\/a><span style=\"font-weight: 400;\"> provides a straightforward way to make feedback specific and constructive.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">SBI stands for:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Situation: Identify when and where the behaviour occurred.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Behaviour: Describe the observable action without assuming intent.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Impact: Explain the effect on the team, customer or business outcome.<\/span><\/li>\n<\/ul>\n<h3><b>Applying SBI to a workplace situation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Consider an employee who repeatedly misses delivery commitments.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A vague comment might be that the employee needs to become more responsible. This describes a judgement, not the behaviour that needs attention.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An SBI-based conversation could sound like this:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager can then ask what caused the delays and whether the employee had enough clarity, support and decision-making authority.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This creates room for an honest discussion without immediately assigning blame.<\/span><\/p>\n<h3><b>Using SBI for positive feedback<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">SBI is also useful for recognising effective behaviour.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">During the customer escalation meeting, you summarised the client&#8217;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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Specific recognition tells employees which behaviours contribute to stronger outcomes.<\/span><\/p>\n<h3><b>What SBI Cannot Replace: Understanding, Dialogue, and Action<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The SBI feedback model helps managers describe a specific situation, observable behaviour, and its impact.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, it does not automatically establish why the behaviour occurred or what action will improve performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Consider the following feedback:<\/span><\/p>\n<p><b>Situation:<\/b><span style=\"font-weight: 400;\"> During the last two sprint reviews.<\/span><\/p>\n<p><b>Behaviour:<\/b><span style=\"font-weight: 400;\"> The agreed delivery dates changed without an early update.<\/span><\/p>\n<p><b>Impact:<\/b><span style=\"font-weight: 400;\"> The testing team had limited time to prepare, creating additional pressure before release.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This provides a specific starting point for discussion.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager should then invite the employee&#8217;s perspective.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The answers may reveal an individual communication gap, an unclear escalation process, a dependency outside the employee&#8217;s control, or several contributing conditions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The appropriate response should follow that understanding.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A useful feedback conversation therefore includes:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Specific observations rather than assumptions about personality or intent.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">An opportunity for the employee to explain their perspective.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A shared understanding of the expected behaviour and relevant performance conditions.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Appropriate employee and manager commitments.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Follow-up to establish whether the agreed changes are helping.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The same principles apply to positive feedback.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Recognising a specific contribution helps employees understand what they did effectively and how that behaviour supported the intended outcome.<\/span><\/p>\n<p><b>SBI makes feedback more specific. Effective management dialogue determines what the feedback means and what should happen next.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Organisations can strengthen these capabilities through practical<\/span><a href=\"https:\/\/nextagile.ai\/workshop\/delegation-and-feedback-workshop\/\"> <span style=\"font-weight: 400;\">delegation and feedback workshops<\/span><\/a><span style=\"font-weight: 400;\"> that help managers develop their ability to set expectations, listen, coach, provide feedback, and support employee ownership.<\/span><\/p>\n<h2><b>Handling Difficult Conversations During One on One Meetings<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Not every 1:1 conversation will be comfortable. Managers may need to discuss repeated missed commitments, <\/span><a href=\"https:\/\/nextagile.ai\/workshop\/conflict-management-workshop\/\"><span style=\"font-weight: 400;\">disagreements about performance<\/span><\/a><span style=\"font-weight: 400;\">, declining motivation or expectations that cannot currently be met.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A productive conversation should separate the observed issue from assumptions about the person.<\/span><\/p>\n<h3><b>When an employee disagrees with feedback<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Do not treat disagreement as resistance. Ask which part of the feedback the employee sees differently and invite examples.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Compare the available evidence before deciding on an action. The objective is to establish a shared understanding, not to win an argument.<\/span><\/p>\n<h3><b>When an employee repeatedly misses commitments<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Examine the pattern rather than discussing only the latest missed deadline.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>When an employee feels overwhelmed<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Understand what is creating the pressure. It could be excessive workload, unclear priorities, stakeholder demands or responsibilities outside the employee&#8217;s role.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>When an employee wants a promotion<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Acknowledge the aspiration and discuss the capabilities required for the next role.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Be clear about current opportunities and organisational constraints. Agree on development actions that can demonstrate readiness rather than making promises about promotion timelines.<\/span><\/p>\n<h3><b>When should a manager coach or intervene?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Managers should not solve every problem on behalf of employees. Doing so can reduce ownership and create unnecessary dependence.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Provide direction when responsibilities or expectations are unclear. Escalate concerns involving serious risk or formal organisational processes through the appropriate channels.<\/span><\/p>\n<h2><b>Connecting 1:1s to OKRs and Performance Reviews<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">One on one meetings become more valuable when individual responsibilities are connected to organisational priorities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>Connect individual priorities to OKRs<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Suppose an organisation has an objective to improve customer retention.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A product team may contribute through better reliability, faster issue resolution and improved customer communication. Each employee has a different responsibility within that objective.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">During a 1:1, the manager can ask which key result the employee&#8217;s work supports, what could affect their contribution and whether any current activity is consuming time without improving the intended outcome.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This helps employees understand why their work matters. It also helps managers identify misalignment before it affects business results.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Not every employee responsibility needs to map directly to an individual Key Result.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Employees may contribute through shared team outcomes, essential operational responsibilities, risk management, customer support, or capabilities that enable future performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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 <\/span><a href=\"https:\/\/nextagile.ai\/blogs\/okr\/what-is-okr\/\"><span style=\"font-weight: 400;\">OKR structure<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should also recognise when an employee&#8217;s contribution depends on outcomes, decisions, or resources controlled by others.<\/span><\/p>\n<h3><b>Use 1:1s to identify execution risks<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A regular conversation can uncover these issues before they become visible in the performance dashboard.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager can then clarify ownership, resolve dependencies or escalate decisions that require leadership involvement.<\/span><\/p>\n<h3><b>Make performance reviews a continuation of regular conversations<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Formal performance reviews should not introduce unexpected feedback.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers can use recurring 1:1s to document contributions, discuss challenges, recognise effective behaviour and track development goals.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This creates a more balanced review because performance is considered across the review period rather than judged mainly on recent events.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A consistent<\/span><a href=\"https:\/\/nextagile.ai\/blogs\/leadership\/management-rhythm\/\"> <span style=\"font-weight: 400;\">management rhythm<\/span><\/a><span style=\"font-weight: 400;\"> connects individual conversations with team reviews, planning cycles and performance discussions without creating unnecessary reporting activity.<\/span><\/p>\n<h2><b>How One-on-One Meetings Fit Into the Enterprise Performance System<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">One-on-one meetings are an important part of <\/span><a href=\"https:\/\/nextagile.ai\/performance-management-consulting-services\/\"><span style=\"font-weight: 400;\">continuous performance management<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They help managers and employees connect expectations, performance evidence, feedback, development, and action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, their effectiveness also depends on the wider organisational system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">These conditions extend beyond the quality of the individual conversation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Performance architecture provides a way to understand how strategic priorities, goals, execution conditions, capability, evidence, accountability, and management decisions influence one another.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Within this architecture, one-on-one meetings provide an opportunity to understand how the system is experienced by individual employees.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They can reveal where expectations are unclear, where development support is needed, and where organisational conditions are preventing effective performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The manager can then determine the appropriate response.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Some issues require individual coaching or feedback. Others require management decisions, cross-functional coordination, or broader organisational action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When similar concerns recur across several employees or teams, the organisation should examine whether its existing performance mechanisms are contributing to the problem.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">One-on-one meetings should therefore connect with team management practices, continuous performance management, and appropriate leadership decision-making.<\/span><\/p>\n<p><b>The conversation helps reveal what is happening. The wider performance system must provide the ability to respond.<\/b><\/p>\n<h2><b>Skip Level Meetings: When and How to Run Them<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, a team member may meet a department head directly without their immediate manager participating.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>When should organisations conduct skip-level meetings?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Skip-level meetings are useful during <\/span><a href=\"https:\/\/nextagile.ai\/enterprise-agile-transformation\/\"><span style=\"font-weight: 400;\">organisational transformation<\/span><\/a><span style=\"font-weight: 400;\">, restructuring, persistent execution problems or periods when senior leaders need a clearer view of employee experience.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, these meetings should not become a way to bypass managers or create competing reporting structures.<\/span><\/p>\n<h3><b>A practical skip-level meeting agenda<\/b><\/h3>\n<table>\n<tbody>\n<tr>\n<td><b>Time<\/b><\/td>\n<td><b>Discussion<\/b><\/td>\n<td><b>Purpose<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">0 to 5 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Introduction and context<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Explain the purpose of the discussion<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">5 to 15 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Employee experience<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Understand what supports or affects performance<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">15 to 25 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Organisational barriers<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Identify issues involving decisions and coordination<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">25 to 30 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Closing and follow-up<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Confirm themes and next steps<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Senior leaders can ask what is working well, where employees experience friction, whether organisational priorities are clear and what leadership could improve.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Questions should invite honest observations rather than encourage employees to criticise their immediate managers.<\/span><\/p>\n<h3><b>Handle Sensitive Feedback Responsibly<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Skip-level meetings can help senior leaders understand employee experiences and organisational barriers that may not be visible through regular management reporting.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, they also create responsibilities around trust, confidentiality, and appropriate action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Before the conversation, explain its purpose, how information may be used, and the limits of confidentiality.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Employees should understand that some concerns, particularly those involving safety, harassment, discrimination, serious misconduct, or legal obligations, may require action through formal organisational processes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Employees should not experience retaliation for raising legitimate concerns or using appropriate reporting channels.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Where a concern requires formal investigation, the senior leader should follow the organisation&#8217;s established procedures rather than attempt to resolve it through an informal management conversation alone.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Skip-level meetings should complement, not replace, appropriate grievance, safeguarding, ethics, or employee reporting mechanisms.<\/span><\/p>\n<h3><b>Distinguish Individual Concerns From Organisational Patterns<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">One employee&#8217;s experience may identify an important issue that requires attention.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, an individual observation does not automatically establish that the same problem exists across the organisation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Senior leaders should examine relevant evidence, consider other perspectives where appropriate, and distinguish between individual concerns, management capability issues, and recurring organisational constraints.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, several employees may report that important decisions are repeatedly delayed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This creates a connection between employee feedback and organisational improvement.<\/span><\/p>\n<h3><b>Close the Feedback Loop Without Compromising Trust<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Skip-level meetings lose credibility when employees repeatedly share concerns without seeing an appropriate response.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Senior leaders should establish which issues require action, assign responsibility, and communicate relevant progress where possible.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Not every concern can be resolved immediately. Some may require investigation, changes to organisational priorities, or decisions involving several functions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Employees should receive appropriate acknowledgement and follow-up without compromising another person&#8217;s privacy or the integrity of a formal process.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When sharing broader themes with management teams, leaders should protect sensitive information and avoid identifying individual employees unnecessarily.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The objective is not to collect more feedback or create an alternative reporting hierarchy.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It is to improve leadership&#8217;s understanding of the organisation and strengthen its ability to respond to the conditions affecting people and performance.<\/span><\/p>\n<h2><b>Running One-on-One Meetings in Hierarchy-Conscious Workplaces<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The extent of this influence varies across organisations, teams, industries, and individuals.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A team member may agree to a deadline despite recognising that it is unrealistic. An employee may hesitate to question a senior stakeholder&#8217;s decision. Another may raise a concern privately but avoid discussing it during a larger review.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">These behaviours do not necessarily indicate a lack of ownership or willingness to contribute.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should therefore avoid interpreting silence as agreement or the absence of complaints as evidence that everything is working well.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">One-on-one meetings can provide a useful opportunity to understand concerns that employees may not feel comfortable raising in a larger setting.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, trust depends on more than inviting employees to speak.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers need to demonstrate through their responses that respectful disagreement, early risk communication, and constructive feedback are welcome.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>Create space for employees to speak honestly<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Instead of asking whether everyone agrees with a decision, ask what risks the team may be overlooking.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When an employee raises a concern, explore the issue before defending the existing approach. Consistent responses help employees understand that respectful disagreement is acceptable.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This is an important part of building<\/span><a href=\"https:\/\/nextagile.ai\/blogs\/leadership\/how-to-build-psychological-safety-in-the-workplace\/\"> <span style=\"font-weight: 400;\">psychological safety at work<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h3><b>Do not interpret silence as commitment<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">If an employee accepts a deadline, ask what dependencies and resources are required to meet it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should also share the agenda before the meeting and give employees time to prepare difficult topics.<\/span><\/p>\n<h3><b>Adapt the conversation to the individual<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should adapt their communication style without lowering expectations around accountability and performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Structured<\/span><a href=\"https:\/\/nextagile.ai\/corporate-leadership-training\/\"> <span style=\"font-weight: 400;\">leadership training for managers<\/span><\/a><span style=\"font-weight: 400;\"> can help build the listening, coaching, delegation and feedback capabilities required to lead different teams effectively.<\/span><\/p>\n<h3><b>Maintain the same quality in remote and hybrid teams<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Remote employees can become disconnected when most interactions focus on task allocation and virtual status reviews.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should protect recurring 1:1 time, use a private communication channel and avoid multitasking during conversations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h2><b>How to Measure Whether Your One-on-One Meetings Are Working<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">A manager may complete every scheduled one-on-one meeting and still fail to improve employee effectiveness.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A more useful approach examines the quality of the conversation, the actions it produces, and the outcomes those actions are intended to influence.<\/span><\/p>\n<h3><b>Six Areas to Examine<\/b><\/h3>\n<table>\n<tbody>\n<tr>\n<td><b>Measurement area<\/b><\/td>\n<td><b>Management question<\/b><\/td>\n<td><b>Possible evidence<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Meeting consistency<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are employees receiving regular, appropriate opportunities for individual conversations?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Meeting continuity and rescheduling patterns<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Conversation usefulness<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Do employees find the discussions relevant, supportive, and constructive?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Employee feedback and examples of useful discussions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Manager follow-through<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are managers completing commitments that require their action or authority?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Progress against manager-owned actions and unresolved decisions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Issue resolution<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are the conditions affecting employee performance being addressed?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Resolution of blockers, recurring issues, and escalation outcomes<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Development progress<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are employees receiving meaningful opportunities to build and apply capabilities?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Demonstrated learning, practical assignments, feedback, and development progress<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Performance conditions<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Are relevant aspects of work becoming clearer or more effective?<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Changes in priority clarity, workload, decision waiting, collaboration, or relevant delivery outcomes<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">These indicators should be interpreted in context.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, an increase in concerns raised during one-on-one meetings may indicate that employees feel more comfortable discussing problems.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Similarly, completing an agreed action does not necessarily establish that the underlying problem has been resolved.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A manager may escalate a dependency on time while the decision itself remains outstanding.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The relevant question is whether the action has improved the condition affecting performance.<\/span><\/p>\n<h3><b>Review Recurring Organisational Constraints<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">At regular intervals, managers should examine whether similar concerns appear across several employee conversations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Several employees report competing priorities.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multiple team members are waiting for the same cross-functional decision.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Development commitments are repeatedly postponed because delivery workloads leave insufficient capacity.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Employees raise similar concerns about unclear expectations or conflicting responsibilities.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">These patterns may indicate a management or organisational constraint rather than separate individual performance problems.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Managers should examine the evidence and determine whether the appropriate response involves their own management practices, coordination with other teams, or escalation to leadership.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Sensitive individual information should not be unnecessarily shared when discussing broader organisational themes.<\/span><\/p>\n<h3><b>Avoid Turning One-on-One Meetings Into Another Measurement Burden<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The purpose of measuring one-on-one effectiveness is to improve management practice, not to create a new employee surveillance system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organisations should avoid evaluating managers solely on meeting completion rates, the number of concerns recorded, or the percentage of actions closed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Such measures can encourage superficial compliance, premature action closure, or reluctance to discuss difficult issues.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The most useful review asks:<\/span><\/p>\n<p><b>Are these conversations helping employees and managers identify important performance conditions, take appropriate action, and learn whether that action is making a difference?<\/b><\/p>\n<p><span style=\"font-weight: 400;\">If the answer is yes, one-on-one meetings are becoming a meaningful part of the organisation&#8217;s performance system rather than another recurring management activity.<\/span><\/p>\n<h2><b>Conclusion: Better One-on-One Meetings Should Lead to Better Management<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A recurring calendar invitation does not guarantee a meaningful management conversation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If the time is used only to collect status updates, employees may experience the meeting as another reporting requirement.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If concerns are discussed but important commitments are repeatedly left unresolved, employees may gradually lose confidence in the value of the conversation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Effective one-on-one meetings create space for employee perspectives, recognition, feedback, development, and appropriate management action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Sometimes the employee needs coaching or capability development.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Sometimes the manager needs to clarify expectations, resolve competing priorities, or make a decision.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Sometimes the organisation needs to address a wider execution or performance constraint.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The discipline is understanding which response is required.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A practical starting point is to review your last three one-on-one conversations with each direct report.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Where the same concerns continue to appear, examine why the conditions affecting performance have not changed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At NextAgile, our consulting perspective connects managerial effectiveness with leadership capability, continuous performance management, execution conditions, and organisational decision-making.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The appropriate response may involve <\/span><a href=\"https:\/\/nextagile.ai\/leadership-coaching-services\/\"><span style=\"font-weight: 400;\">manager coaching<\/span><\/a><span style=\"font-weight: 400;\">, leadership development, changes to management practices, or improvements to the wider organisational system. If your managers need to move beyond status reporting and build <\/span><a href=\"https:\/\/nextagile.ai\/workshop\/building-ownership-and-accountability-workshop\/\"><span style=\"font-weight: 400;\">stronger employee ownership<\/span><\/a><span style=\"font-weight: 400;\">, connect with our team at <\/span><a href=\"mailto:consult@nextagile.ai\"><span style=\"font-weight: 400;\">consult@nextagile.ai<\/span><\/a><span style=\"font-weight: 400;\"> to explore how we can support your leadership development priorities.<\/span><\/p>\n<h2><b>Frequently Asked Questions<\/b><\/h2>\n<h3><b>1. How often should managers hold 1:1s with each direct report?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Most managers should schedule one on one meetings weekly or fortnightly. <\/span><a href=\"https:\/\/www.gallup.com\/workplace\/350057\/gallup-finds-silver-bullet-coach-once-per-week.aspx\" rel=\"nofollow noopener\" target=\"_blank\"><span style=\"font-weight: 400;\">Weekly conversations<\/span><\/a><span style=\"font-weight: 400;\"> 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.<\/span><\/p>\n<h3><b>2. Should the employee or the manager own the 1:1 agenda?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>3. What should you do when an employee has nothing to discuss?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>4. Is it fine to cancel a 1:1 when the week is busy?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>5. How do you run 1:1s with remote or hybrid team members?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n<h3><b>6. What notes should a manager keep after each 1:1?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">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.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>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&#8230;<\/p>\n","protected":false},"author":4,"featured_media":9184,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[141],"tags":[],"class_list":["post-9180","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-leadership"],"_links":{"self":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/9180","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/comments?post=9180"}],"version-history":[{"count":3,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/9180\/revisions"}],"predecessor-version":[{"id":9183,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/9180\/revisions\/9183"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media\/9184"}],"wp:attachment":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media?parent=9180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/categories?post=9180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/tags?post=9180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}