The 1:1 that nobody looks forward to

Most CS managers hold 1:1s. Fewer hold 1:1s that their agents look forward to. The difference between a 1:1 that is genuinely valuable and one that is merely scheduled is not the frequency or the duration — it is the purpose, the structure, and the quality of the conversation that happens within it.

The 1:1 that nobody looks forward to follows a predictable pattern. The manager opens with a review of last week's metrics. The agent listens to numbers they already know. The manager identifies one or two things that need to improve. The agent nods. Both parties leave without anything having genuinely shifted. The same conversation happens the following week, and the week after that.

The 1:1 that people look forward to is different in kind, not just in execution. It is a conversation where the agent feels genuinely seen — not as a set of metrics but as a person with a perspective, a development trajectory, and a relationship with their work that matters. It is a conversation where something is agreed and tracked, where the manager demonstrates knowledge of the individual's specific situation rather than applying a generic script, and where the agent leaves feeling clearer, more capable, or more motivated than when they arrived.

Building that kind of 1:1 requires structure, a coherent feedback model, and — the element most often absent from management training — an understanding of how different people receive and process feedback differently.

The purpose of the 1:1

The 1:1 serves three distinct purposes that need to be balanced across the conversation. When one purpose dominates at the expense of the others, the meeting loses its value for either the manager or the agent.

Performance review is the backward-looking component — reviewing recent performance data, discussing what went well and what didn't, connecting current performance to the scorecard. This is the component most managers over-invest in. It is necessary but not sufficient. A 1:1 that is entirely performance review is a metrics debrief, not a development conversation.

Development is the forward-looking component — discussing the agent's goals, identifying skill gaps, planning learning activities, tracking progress against the development plan agreed in the previous session. This is the component most managers under-invest in. Agents who feel their development is genuinely attended to are more engaged, more likely to stay, and more likely to grow into higher-value roles.

Relationship is the connective component — understanding the agent's current state, their experience of the team and the work, their level of engagement and motivation. This is not small talk. It is the intelligence-gathering that allows a manager to notice early signals of disengagement, frustration, or personal difficulty that, unaddressed, become operational problems. A manager who only knows their agents' performance metrics but not their state of mind is managing blindly.

A useful allocation across a 30-minute 1:1 is roughly: 10 minutes on performance, 15 minutes on development, 5 minutes on relationship and check-in. This weighting — which feels counterintuitive to many managers who have been trained to focus on metrics — reflects the reality that performance is a lagging indicator and development is a leading one.

Structuring the 1:1: the GROW model in practice

The GROW model — Goal, Reality, Options, Way Forward — provides the structural backbone for a development-oriented 1:1. It is the same coaching framework covered in the WFM series, applied here in the specific context of 1:1 conversations.

Goal sets the focus for the session. What are we working on today? This might be a specific performance gap identified in the scorecard, a development objective from the previous session, a skill the agent wants to build, or a situation they want to think through. The goal should be set collaboratively at the start of the conversation — not imposed by the manager — which gives the agent ownership of the direction of the conversation.

In practice: "Looking at this week, what would be most useful to focus on today?" or "Last time we agreed you'd work on reducing your re-open rate — how has that been going and what do you want to explore?"

Reality establishes the current state — where things actually are relative to the goal. This is where performance data is introduced, but as context for the coaching conversation rather than as a report being delivered to the agent. The manager's role is to help the agent see their current reality clearly, including aspects they may be avoiding or underestimating.

In practice: "Looking at your QA scores for the last three weeks, what do you notice?" or "You mentioned you'd been trying a different approach to complex escalations — what's been your experience?"

Options generates possibilities for improvement. This is the most important phase of the GROW model and the one most managers shortcut by jumping straight to advice. The discipline is to ask questions that help the agent generate their own options before offering the manager's perspective. Agents who generate their own solutions are more committed to implementing them than those who receive solutions from their manager.

In practice: "What are some different approaches you could try?" or "If you were coaching someone else on this, what would you suggest?" or "What's worked for you in similar situations before?"

Way Forward converts the conversation into commitment. What specifically will the agent do, by when, and how will both parties know it has been done? The way forward should be specific enough to be trackable — not "I'll try to improve my escalation communication" but "I'll use the new escalation handoff template for every T2 transfer this week and we'll review three examples in our next session."

The GROW model does not require rigidly following four sequential phases. It is a framework for keeping the conversation developmental — ensuring it moves from situation awareness to committed action rather than circling in discussion without resolution.

Preparing for the 1:1

The quality of a 1:1 is largely determined before it begins. Managers who arrive at 1:1s having reviewed the agent's scorecard data, recalled the commitments made in the previous session, and prepared two or three specific observations or questions have fundamentally different conversations from those who open their notes for the first time when the agent sits down.

Effective 1:1 preparation takes ten minutes and covers four things:

Review the scorecard. What has changed since the last session? What is improving, what is declining, what is stable? Identify one or two specific data points to explore in the conversation — not a comprehensive metrics review, but the most important signal in the current period.

Review previous commitments. What did the agent agree to do in the last session? Has it been done? What evidence is there of follow-through or lack of it? Opening a 1:1 by acknowledging when an agent has followed through on a commitment — and noticing when they haven't — signals that the conversations are connected and that commitments are taken seriously.

Review QA findings. Are there specific interactions from the past period that illustrate a quality pattern worth exploring? Having a specific ticket or call to reference makes feedback concrete rather than abstract — "I noticed this in ticket 4821 on Tuesday" is more useful than "I've noticed you sometimes struggle with complex escalations."

Consider the individual's current state. Is there anything known about this agent's current situation — a recent personal difficulty, a change in their workload, a team dynamic issue — that should inform how this conversation is approached? The relationship component of the 1:1 requires that the manager brings knowledge of the individual, not just their metrics.

Giving feedback that lands

Feedback is the mechanism through which performance data is converted into behaviour change. Most managers understand this in principle. Fewer have developed the skill of delivering feedback in a way that the recipient can actually receive, process, and act on.

The failure modes in feedback delivery are well-documented. Feedback that is too vague to act on. Feedback that is delivered in a way that triggers defensiveness rather than reflection. Feedback that focuses on the person rather than the behaviour. Feedback that is only negative — a catalogue of what went wrong with nothing that acknowledges what went right. Feedback that is so hedged and qualified that the central message gets lost.

Three principles produce feedback that consistently lands better than the alternatives.

Specific over general. Specific feedback is actionable. General feedback is demoralising. "Your written communication isn't clear enough" gives the agent nothing to work with. "In the response you sent to the Nexus account on Thursday, you included three different possible explanations for the payment discrepancy without telling the customer which one you thought applied — that would have left them more confused than when they started" gives the agent exactly what to fix and why.

Behaviour over character. Feedback about what someone did is received differently from feedback about who they are. "You escalated this ticket without completing the handoff template" describes a behaviour. "You're careless about documentation" describes a character. The first invites correction. The second invites defensiveness. The distinction seems subtle but is consistently significant in how feedback is received.

Balanced and proportionate. The SBI model — Situation, Behaviour, Impact — provides a structure for feedback that is both specific and balanced. Describe the situation in which the behaviour occurred. Describe the specific behaviour. Describe the impact of that behaviour — on the customer, on the team, on the outcome.

"In the Morrison account escalation last Wednesday — the situation — you proactively updated the customer every six hours with progress reports even though nothing had changed — the behaviour — and the customer specifically mentioned in their follow-up survey that they felt well-informed throughout — the impact."

The same structure works for developmental feedback: "In the Johnson ticket on Monday, you closed the ticket after fixing the immediate error without checking whether the underlying data issue had been corrected — the customer contacted us again two days later with the same problem. The impact was a repeat contact and a DSAT rating. What would you do differently?"

Receiving feedback: the manager's blind spot

Most management training focuses on giving feedback. Less attention is paid to receiving it — and a manager who cannot receive feedback from their agents is not modelling the behaviour they are asking agents to demonstrate.

Making 1:1s genuinely bidirectional — creating space for the agent to give feedback to the manager about what is and isn't working — requires explicit invitation and demonstrated response. If a manager asks "is there anything I could do differently to support you better?" and then defends or dismisses what they hear, agents learn quickly not to answer honestly.

The discipline of receiving feedback is: listen without defending, ask clarifying questions to make sure you've understood, acknowledge what you've heard specifically, and — where appropriate — follow up in the next session with what changed as a result of what the agent said. That follow-through is what signals to the agent that the invitation was genuine.

Personality models: adapting to the individual

One of the most consistent findings in management development research is that feedback and coaching effectiveness varies significantly depending on how it is delivered relative to how the recipient processes information and responds to challenge. A feedback approach that works well with one agent may be ineffective or counterproductive with another — not because the content is wrong but because the delivery style doesn't match the recipient's communication and motivation preferences.

Two personality frameworks are widely used in management and coaching contexts to develop this adaptive capability: DISC and OCEAN. Neither is a definitive map of human personality. Both are useful lenses that help managers develop more nuanced awareness of how different people prefer to communicate, receive feedback, and be motivated.

DISC: communication style in practice

DISC is a behavioural model that describes how people tend to communicate and respond in work contexts across four dimensions:

D — Dominance characterises people who are direct, results-oriented, and decisive. They value efficiency, dislike ambiguity, and respond best to feedback that is direct, concise, and focused on outcomes rather than process. They can be impatient with lengthy explanations and may interpret indirect feedback as evasiveness.

I — Influence characterises people who are enthusiastic, collaborative, and relationship-oriented. They are motivated by recognition, social connection, and positive energy. They respond well to feedback that acknowledges their contribution before addressing development areas, and can disengage from feedback that is purely critical without acknowledgement.

S — Steadiness characterises people who are patient, reliable, and team-oriented. They value stability, consistency, and clear expectations. They can be resistant to sudden change and may need more time to process feedback before responding. They respond best to feedback delivered in a calm, supportive context rather than in a high-pressure or confrontational setting.

C — Conscientiousness characterises people who are analytical, detail-oriented, and quality-focused. They value accuracy, data, and logical reasoning. They respond best to feedback that is specific, evidence-based, and well-reasoned. They may resist feedback that is vague or insufficiently substantiated.

Most people are a blend of two or three DISC dimensions rather than a pure type. The value of DISC for managers is not in labelling agents but in developing awareness that different people have different default communication preferences — and that adapting delivery to those preferences significantly improves the likelihood that feedback is received and acted on.

In practice: a high-D agent who is told in careful, diplomatic language that their escalation rate is concerning may leave the conversation without fully registering the message. The same message delivered directly — "your escalation rate is 40% above the team average and I need to see it come down — let's figure out what's driving it" — will land clearly and invite a direct response. Conversely, delivering that same direct message to a high-S agent without context, acknowledgement, or support may trigger anxiety and defensiveness rather than committed action.

OCEAN: the deeper personality lens

OCEAN — also known as the Big Five — is a more comprehensive personality framework that has stronger empirical support than DISC and is increasingly used in organisational development contexts. It describes personality across five dimensions that are relatively stable across contexts and time:

Openness to experience reflects intellectual curiosity, creativity, and receptiveness to new ideas. High-openness agents tend to embrace change, enjoy learning new approaches, and engage well with development conversations that introduce new frameworks or ways of thinking. Low-openness agents prefer familiar routines and may resist approaches that deviate significantly from established practices.

Conscientiousness reflects organisation, dependability, and goal orientation. High-conscientiousness agents are reliable, thorough, and self-motivated — they tend to follow through on development commitments without significant external prompting. Low-conscientiousness agents may need more structure, shorter feedback loops, and more active accountability to maintain development momentum.

Extraversion reflects sociability, assertiveness, and positive emotionality. High-extraversion agents are energised by interaction and recognition and may respond particularly well to public acknowledgement of achievement. Low-extraversion agents — introverts — may find public recognition uncomfortable and prefer feedback delivered privately and one-on-one.

Agreeableness reflects cooperativeness, empathy, and a desire for social harmony. High-agreeableness agents may be reluctant to express disagreement with feedback even when they have a legitimate perspective — they will appear to accept feedback that they haven't genuinely internalised. Low-agreeableness agents may challenge feedback more directly and require managers who can engage with pushback constructively rather than treating it as resistance.

Neuroticism — sometimes labelled emotional stability in its inverse form — reflects the tendency to experience negative emotional states in response to stress and challenge. High-neuroticism agents may respond to critical feedback with disproportionate anxiety or self-criticism, requiring managers to be particularly attentive to how developmental feedback is framed. Low-neuroticism agents tend to be emotionally stable and resilient in the face of challenging feedback.

Using personality models without stereotyping

A critical caveat for both DISC and OCEAN: these frameworks are tools for developing awareness, not labels for categorising people. Using them well requires treating them as hypotheses to test rather than conclusions to apply. An agent who scores high on agreeableness in a personality assessment is not necessarily someone who will suppress disagreement in every feedback conversation — they are someone for whom that tendency is worth being aware of and checking for.

The practical discipline is: use personality models to expand your repertoire of management approaches rather than to narrow your assessment of individuals. A manager who has developed awareness of DISC and OCEAN is better equipped to notice when their default feedback style is not landing, to consider why that might be, and to adapt their approach accordingly.

The signal that adaptation is needed is usually observable in the conversation: an agent who is becoming closed and defensive, one who is agreeing without genuine engagement, one who seems overwhelmed rather than motivated. These are signals that the current delivery approach is not serving the recipient — and personality awareness provides a framework for understanding why and adjusting.

Signals of team health in the 1:1

Individual 1:1s are also the primary source of intelligence about the health of the team as a whole. A manager who pays attention to what agents say — and what they don't say — across their 1:1 conversations will detect team health problems significantly earlier than one who relies on metrics alone.

Key signals worth attending to:

Consistent themes across multiple agents. When three or four agents raise the same concern in the same week — about a process, a team dynamic, a workload issue — the convergence is a signal that warrants action, not just acknowledgement.

Declining engagement in development conversations. Agents who were previously engaged in development discussions but have become passive and monosyllabic are showing early disengagement signals. The earlier this is noticed and addressed, the higher the probability of re-engagement before attrition becomes likely.

Unusual hesitation or guardedness. Agents who are normally open but have become cautious or vague in their responses may be experiencing something in the team environment — a conflict with a colleague, a concern about a manager's behaviour, an anxiety about job security — that they are not yet comfortable raising directly. Creating space for these concerns without forcing them — "is there anything else going on that it would be useful for me to know about?" — sometimes surfaces issues that would otherwise remain invisible until they become crises.

Energy and mood patterns. An agent who arrives at 1:1s consistently flat, low-energy, or cynical is showing a pattern that warrants attention beyond the performance conversation. Whether the cause is workload, team dynamics, personal circumstances, or early burnout, the pattern is a signal that the relationship component of the 1:1 needs more investment.

The 1:1 documentation discipline

The value of a 1:1 is not only in the conversation itself but in the continuity between conversations — the thread of commitments, progress, and development that connects each session to the last. That continuity requires documentation.

After every 1:1, a brief note should capture: the main topics discussed, any performance data reviewed, the development focus for the session, and — most importantly — the specific commitments made by both the agent and the manager, with the agreed timeline for each.

This note does not need to be lengthy. A half-page of structured notes serves the purpose. Its function is to make the next 1:1 preparation straightforward, to provide a record of development conversations that supports performance management decisions, and to demonstrate to the agent that what they say in 1:1s is taken seriously enough to be written down and followed up on.

The format can be as simple as four headings: what we discussed, what the data showed, what we agreed the agent will do, what the manager will do. Consistency of format across sessions makes the record easy to review and makes patterns of progress or stagnation visible over time.