Beyond the Tracker: A Coaching Agenda for One-to-Ones That Build Capability

Ask a UK manager what happens in a one-to-one and you will often hear a familiar list: project updates, deadlines, risks, actions. Ask what happens to the person in the conversation—their confidence, their capability, their sense of direction—and the answer is less clear. The meeting has become a reporting line, not a development conversation.

This is understandable. Managers are accountable for delivery. One-to-ones are one of the few recurring slots where progress can be checked. But when the agenda is dominated by status, the meeting becomes a project update that could have been an email. The manager stays in the role of overseer. The team member stays in the role of reporter. Capability does not grow; dependency does.

The cost of the status-update habit

A status-led one-to-one is not neutral. It teaches people that the most important thing to bring to their manager is a clean progress report. It rewards certainty and discourages early disclosure of difficulty. It makes it harder for someone to say, 'I am not sure how to approach this' or 'I am losing confidence in this piece of work.'

Over time, the manager becomes a bottleneck. Decisions queue up. Problems surface late, when they are more expensive to solve. The team member learns to wait for direction rather than think for themselves. The meeting is busy, but it is not building the capability the organisation needs.

The alternative is not to abandon progress entirely. It is to rebalance the agenda so that progress is one part of a wider conversation about capability, judgement and support.

A simpler, coaching-led agenda

A coaching-led one-to-one can be built around three elements: one meaningful question, one development focus and one commitment. The structure is deliberately light. It can fit into a 30-minute meeting and still leave room for the practical business of work.

One meaningful question

The question should be open, genuine and connected to the person's experience of their work. It is not a warm-up; it is the heart of the conversation. Examples include:

• What is taking more energy than it should at the moment?
• Where are you having to make a judgement call without enough information?
• What would make the next fortnight feel more manageable?
• What have you learned recently that you want to use more often?

The manager's job is to listen longer than feels comfortable and resist the urge to solve. A good question creates space for the team member to think aloud. That thinking is the development.

One development focus

Development does not have to mean a course or a promotion. It can be a capability the person wants to strengthen in the next month: chairing a meeting, giving clearer feedback, managing upwards, making decisions with incomplete data. The focus should be small enough to act on and specific enough to notice.

The manager can ask: 'What is one capability you want to get better at over the next four weeks?' Then agree what practice will look like and how you will both know it is happening. This is where the conversation moves from reflection to intent.

One commitment

End with one commitment, not a list. It might be something the team member will do before the next meeting, or something the manager will do to create the conditions for progress. Examples: 'I will draft the proposal and bring it to you for challenge by Thursday' or 'I will raise the resourcing issue with the programme board before we meet again.'

One commitment is easier to remember and easier to review. It also signals that the meeting has a purpose beyond reporting.

A practical template

A 30-minute one-to-one might look like this:

• Check-in (2 minutes). A brief, genuine question about how the person is arriving.
• One meaningful question (10 minutes). Listen, probe gently, resist solving.
• One development focus (10 minutes). Agree the capability, the practice and the evidence.
• One commitment (5 minutes). Confirm what happens next and by when.
• Notes and close (3 minutes). Capture actions and agree the next conversation.

For teams that still need a progress check, keep it light. Ask for a short written update before the meeting, or use a two-minute 'traffic light' summary at the start. The meeting itself should not become a read-through of the tracker.

Introducing the change without unsettling the team

Changing the format of one-to-ones can feel risky. People may worry that you are no longer interested in delivery, or that the meeting is becoming therapy. Be explicit about the purpose. Explain that progress still matters, but that you want to use the time to build capability and catch issues earlier.

Start with a short note or a team conversation. Say what will change, why, and what will stay the same. Then pilot it with a few volunteers or for one cycle. Ask for feedback: 'Did this feel useful? What should we keep? What should we drop?' Review after six weeks.

Model the change in your own behaviour. If you ask a meaningful question, do not fill the silence. If you agree a development focus, follow up on it. If you make a commitment, keep it. The team will judge the new agenda by whether it produces better conversations, not by the template itself.

From reporting to capability

A one-to-one is a small unit of management time with a disproportionate effect on culture. When it is used only for status, it reinforces a transaction. When it is used for real conversation, it builds judgement, confidence and trust.

The shift is not about adding another process. It is about reclaiming the time you already have. One meaningful question, one development focus and one commitment are enough to turn a progress meeting into a conversation that helps someone grow—and helps you lead.