.webp)
Most organisations have manager coaching happening somewhere. The problem is that it is happening inconsistently, invisibly, and disconnected from everything else the L&D function is investing in.
One manager has structured monthly one-to-ones with development goals documented. Another has informal conversations over coffee that are never recorded. A third tells their team, "You should talk to HR about development." None of this is tracked. None of it connects to the LMS courses the L&D team is publishing. None of it feeds into the skills matrix or the succession planning conversation.
A coaching programme changes this not by adding bureaucracy, but by creating enough structure that coaching becomes consistent, trackable, and genuinely connected to the L&D ecosystem rather than parallel to it.
What "Manager Coaching" Actually Means in an L&D Context
The term "coaching" is used loosely in most organisations. For the purposes of an L&D-managed programme, it is worth being precise. Manager coaching in this context means:
- Structured, regular one-to-one sessions between a line manager and a direct report
- A defined focus: skill development, performance goals, role progression, or a specific development area
- Documented session notes that record what was discussed, what actions were agreed upon, and what development activities are linked
- A connection to the L&D system coaching sessions linked to relevant courses, skills matrix updates, or IDP goals
This is different from performance management (which is about evaluation and accountability) and different from mentoring (which is typically less structured and driven by the mentee's agenda). Coaching in this context is the regular, documented development conversation that sits alongside the formal L&D curriculum.
A common confusion managers have
The distinction between a coaching conversation and a performance check-in. A coaching conversation is development-focused: "Where are you against your goals and what do you need to move forward?" A performance check-in is evaluation-focused: "How are you performing against your targets?" Both are valid; conflating them creates sessions that feel evaluative to the employee and produce no usable development data for L&D.
Why Most Coaching Programmes Fail
Organisations that have tried to introduce structured coaching programmes and seen them fade after three to six months typically encounter the same failure modes:
The 5 Components of a Working Coaching Programme
1. The Session Cadence and Format
Monthly one-to-one coaching sessions of 45 to 60 minutes are the practical standard for most organisations. Fortnightly is more effective for employees in intensive development phases new hires, high-potentials, or those on performance improvement plans. Quarterly is the minimum for any session to be meaningfully called a "programme."
The session format should follow a consistent structure: (1) review agreed actions from the previous session, (2) focus area for this session, (3) coaching conversation, (4) agreed actions and linked development activities. This structure takes five minutes to apply and means every session is comparable, documented, and actionable.
2. The Documentation Template
The documentation burden on managers is the most common reason coaching programmes collapse. A five-page competency framework template that takes 45 minutes to complete is not a coaching record it is a compliance exercise that managers will avoid.
The documentation should capture four things: the session date and duration, the development focus area, the key points from the discussion (3 to 5 bullet points), and the agreed actions with linked development activities. Nothing more. A manager should be able to complete this in 8 to 10 minutes after the session.
In real-world implementations
The coaching programmes that sustain beyond 12 months almost universally have simple documentation. The ones with elaborate templates, multi-dimensional competency ratings, and mandatory sign-off chains are abandoned by month four. Completion design, not comprehensiveness.
3. The Connection to the L&D System
This is the component that elevates a coaching programme from a management activity to an L&D function. Three specific connections make the difference:
- Course assignment from coaching: A manager can recommend or assign a course from the LMS directly within the coaching record. The employee receives the assignment; the completion is tracked alongside the coaching session.
- Skills goal linking: the development focus area in the coaching session maps to a specific skill in the organisation's skills framework. Each session that addresses the skill updates the employee's development record.
- ILP connection: coaching session goals connect to the employee's individual learning plan, creating a single development record that combines self-directed learning, assigned training, and manager coaching.
Without these connections, the coaching programme is a parallel activity that the L&D function cannot influence, measure, or learn from.
4. Manager Capability Development
Managers who have not been trained in coaching typically deliver one of two things in a coaching session: advice (telling the employee what to do) or appraisal (evaluating how the employee is performing). Neither is coaching.
A prerequisite coaching skills module for managers covering the difference between coaching, mentoring, and managing; a practical question framework for development conversations; how to use the documentation system takes three hours to complete and measurably improves session quality. It is the most consistently under-invested component of coaching programme rollouts.
The manager module should also cover what not to do in a coaching session: avoid performance evaluation language, do not use the session to deliver performance concerns (there are other channels for this), and do not let the session become an informal update meeting.
5. Reporting and L&D Visibility
The L&D function needs programme-level visibility of the coaching programme to demonstrate impact and identify development themes. This does not mean reading individual session notes that would rightly feel intrusive to employees and managers alike.
Programme-level reporting should show: session completion rate by team and department, most common development focus areas across the organisation, course assignment rate from coaching sessions, and skills development movement in teams with active coaching versus teams with low coaching engagement.
This data serves two functions: demonstrating the programme's contribution to development outcomes, and informing L&D programme design if 40 per cent of coaching sessions in a department are focused on a specific skill gap, that is a signal to build or source a targeted learning resource.
Implementation Timeline
Coaching that isn't tracked doesn't count. See how Trainery connects manager coaching sessions to your LMS, skills framework, and development records — in one place. Get a Demo
.webp)
.svg)
.svg)
.svg)
