Combining training with mentoring means treating competency development as a programme rather than an event. The workshop supplies structure and safe practice; the mentoring relationship carries the material into real work, where habits, colleagues and deadlines decide whether anything actually changes. This article describes how those parts fit together and how the result is judged.
Quick Overview
- Why a Training Event Is Not a Development Programme
- The Three Shapes Development Work Takes
- What Training Does Well, and Where Its Reach Ends
- Why Knowledge Leaks Out After the Room Empties
- The Parts of a Combined Programme
- What the Mentoring Half Actually Involves
- Choosing the Form Before Choosing the Budget
- Where Combined Programmes Fail
- Evaluating Something Other Than Satisfaction
- How This Applies to a Technical Specialism
Why a Training Event Is Not a Development Programme
The complaint that starts most of these conversations is not that the training was bad. It is that the training was good and nothing happened afterwards. Participants rate the workshop highly, the trainer gets warm feedback, and weeks later the team is working the way it worked before. The organisation concludes that the topic was wrong, books a different course, and repeats the experience. Then it repeats the conclusion.
The diagnosis is usually somewhere else. A workshop is an intervention with a start and an end. The behaviour it targets lives in a system that did not attend the workshop: a manager with different priorities, colleagues with settled habits, a queue of work that was waiting while the participant was away. Nothing about the workshop obliges that system to change, and by default it does not.
Combining training with mentoring is the attempt to put a second mechanism next to the first one. The workshop owns the knowledge. The mentoring relationship owns the period afterwards, when the participant is trying to use the knowledge against resistance and would otherwise be doing it alone. Neither half substitutes for the other, and a programme that has only one of them fails in a predictable direction: workshops alone produce enthusiasm without change, mentoring alone produces conversations without content.
This is a claim about architecture, not about the craft inside any single session. How a mentor opens a difficult subject with a mentee, how the contract for that conversation is set, what to do when the mentee reacts badly — those belong to the practice of mentoring. What follows here is one level above: what the parts are, how they are sequenced, and what has to be true for the sequence to hold.
The Three Shapes Development Work Takes
Organisations tend to run development work in one of three shapes, and most of the disappointment comes from picking the wrong one rather than from executing the chosen one badly.
The point training. A defined body of knowledge, delivered in a short block, aimed at a skill the participant can start using immediately. This is the oldest and most common shape, and for the right subject it is entirely adequate.
The training cycle. A series of connected workshops spread over weeks, with implementation tasks between the sessions. The gap between sessions is the point: it is where the material meets the job and the participant discovers what they did not understand.
The development programme. Workshops, supported practice, mentoring and evaluation combined into one process with a single owner. This is the shape that costs the most and is required least often — but when it is required, the two cheaper shapes do not substitute for it.
| Aspect | Point training | Training cycle | Development programme |
|---|---|---|---|
| Horizon | Days | Weeks | Months |
| Format | Workshop, in person or online | Series of workshops with tasks between them | Workshops, mentoring and implementation |
| What it does well | Fast, structured transfer of a defined skill | Spreads learning out; forces application between sessions | Individualises support; carries change past the point where enthusiasm fades |
| What it costs | Least budget, least organisational effort | Requires participant discipline over weeks | Requires commitment from participants, managers and the organisation |
| Where it fits | Tools, procedures, an introduction to a field | Complex skills, habit change | Transformation of a working area, leadership development, new ways of working |
The table is a decision aid, not a ranking. A team that needs to learn a reporting tool before the end of the quarter is not underserved by a point training; it is well served by one, and wrapping a full development programme around it would waste everyone’s time and teach the organisation that development work is slow and expensive — a lesson it will apply next time to a case where the programme was genuinely warranted.
What Training Does Well, and Where Its Reach Ends
It is worth being precise about what the workshop half contributes, because the argument for adding mentoring is often made by understating it.
A well-designed workshop gives the participant a structured body of material that somebody competent has already selected, ordered and stripped of the noise they would otherwise wade through alone. It gives them practice in a setting where mistakes are free — the exercise fails, the trainer explains why, nothing downstream breaks. It gives them exposure to other people’s problems, which is the part that cannot be reproduced by reading, because the value comes from hearing how a peer in a different organisation solved something you are currently stuck on. And it gives them distance: a day away from the queue is often the first opportunity in months to think about the work rather than do it.
Those four things are real, and no amount of on-the-job support produces them. The reach of a workshop ends at a specific and predictable point: the moment the participant returns to the environment that produced the problem. At that boundary the workshop has done everything it can do, and whatever happens next is governed by conditions it never touched.
The mistake is not booking the workshop. The mistake is expecting the workshop to be responsible for what happens on the other side of that boundary.
Why Knowledge Leaks Out After the Room Empties
Two well-documented mechanisms explain most of the leakage, and neither of them is a failure of the trainer.
The first is memory decay. The forgetting curve describes how sharply retention of newly learned material drops in the period after learning when nothing reinforces it, and the countermeasure it implies is not more intensity at the start but repetition distributed over time — the principle behind spaced repetition. A programme that front-loads everything into one block and then goes silent is working against the way retention behaves.
The second is the problem of application. The literature on the transfer of learning deals with exactly this question: what makes a skill acquired in one setting reappear in a different one. Transfer is not automatic. It depends on how closely the practice setting resembles the working setting, on whether the participant recognises the situation as one where the new approach applies, and on whether the environment rewards the attempt or punishes it.
Read together, those two mechanisms describe a specific need rather than a general one. What the participant requires after the workshop is not more content. It is spaced contact with someone who can help them recognise the situation and who is available at the moment they are stuck. That is a fair description of mentoring, and it is the reason mentoring is the natural second half rather than an optional extra.
The Parts of a Combined Programme
A combined programme is usually built out of five parts. Naming them separately matters, because organisations frequently buy the second and the fourth and then wonder why the result is uneven.
Diagnosis and planning. Before anything is delivered, the programme establishes what the organisation is actually trying to change and how it will know. That means conversations with the people who own the outcome, an honest reading of the current level of the competency in question, and an individual plan for each participant that reflects their starting point and their role. Skipping this step produces a programme that teaches a population average nobody belongs to.
Foundation workshops. The formal transfer of material, weighted heavily toward practice. Simulations, case work, role plays and group projects carry the load; the theory is present but compressed and tied to problems the participants recognise. This is the part most organisations already know how to buy.
Supported practice. Structured assignments carried out in the participant’s real working environment, sequenced from the simple to the demanding, backed by reference material and a place to compare notes with other participants. This part is what converts a workshop into a programme, and it is the part most often dropped when a budget is trimmed.
Mentoring sessions. Regular meetings, individual or in a small group, in which the participant brings what actually happened. The mentor works on specific situations from the participant’s own week rather than on prepared examples, names what is going well, and helps plan the next step. The mentor’s leverage comes less from having the answer than from asking the question that makes the participant find it.
Evaluation and consolidation. At the end, a deliberate reading of what changed, using both measures and conversation, followed by a plan for keeping it. Where the environment itself was the obstacle, this is where that is said out loud rather than recorded as an individual shortcoming.
The sequence matters as much as the contents. Diagnosis before delivery, practice before mentoring has anything to work on, evaluation after enough time has passed for behaviour to have either held or slipped. A programme that runs these parts in a different order tends to produce mentoring sessions with nothing concrete in them.
What the Mentoring Half Actually Involves
Mentoring inside a development programme is narrower than mentoring in general, and the narrowness is deliberate. The relationship exists to support the implementation of specific competencies, which gives it an agenda that a general mentoring relationship does not have.
In practice, sessions are typically held on a regular cadence over several months, long enough to cover a full cycle of attempt, failure, adjustment and second attempt. A session generally opens with what has happened since the last one, spends the bulk of its time on one or two situations the participant brings, and closes with something specific to try before the next meeting. Between sessions the participant keeps a record of what they attempted and what resulted, which is what makes the next conversation concrete rather than impressionistic.
What a mentor is doing in those sessions is often misread as advice-giving, and mentors who read it that way tend to burn out and lose the mentee’s engagement at the same time. The material the participant brings is usually messier than a case study: partial information, a decision already made, and an account shaped by whoever told it. The useful move is generally to slow that account down and separate what happened from the interpretation wrapped around it before discussing what to do next. That is harder than supplying an answer, and it is the reason mentor selection is a design decision rather than an administrative one.
The distinction worth holding on to is between mentoring and a mentoring programme. Designing the pairing, setting the cadence, agreeing confidentiality, preparing both sides before their first meeting — that is programme design, and it is a subject in its own right. What a combined development programme adds on top of it is the obligation to also own the content: to decide what is taught formally, what is practised on the job, and what only surfaces in a one-to-one conversation. A mentoring programme that is not anchored to a defined body of material drifts into general career discussion, which is valuable but is not what the organisation commissioned.
Choosing the Form Before Choosing the Budget
The form should be chosen from the objective, not from the money available, because the wrong form at the right price is still wasted.
A point training is the right instrument when the target is a defined technical skill or a new procedure, when a tool is being introduced and people need to be able to operate it, or when the aim is to open a subject and create appetite for going further.
A training cycle fits when the competency is complex enough that a single exposure will not fix it, when an existing habit has to be displaced rather than a gap filled, and when the group is homogeneous enough that the same sequence serves everybody.
A development programme is required when the organisation is changing how a whole area works, when the population is leaders and key specialists whose behaviour sets the tone for others, or when the competency in question is strategic enough that a partial result is not worth having.
The honest version of this decision includes a fourth option that vendors rarely raise: do nothing yet. If the obstacle is a process, a tool or a manager’s priorities rather than a competency, then a development programme will produce well-trained people who still cannot act, and the organisation will conclude that development does not work.
Where Combined Programmes Fail
Four failure modes account for most of the disappointment, and each has a countermeasure that has to be designed in rather than improvised later.
The wrong mentors. Deep expertise and the ability to develop someone else are different capabilities, and the first is far more common than the second. An expert who answers every question denies the participant the thinking that produces retention. The countermeasure is selecting mentors against the second capability, preparing them for the role, and giving them somewhere to take their own difficulties.
Standardisation against flexibility. A programme with no common frame delivers a different quality to every participant; a programme with too rigid a frame delivers the same irrelevant content to all of them. The countermeasure is a defined structure with explicit room inside it — the sequence is fixed, the material inside each session is not.
Time that was never really committed. Combined programmes ask for participation over months, from people whose calendars were full before the programme started. When the commitment is assumed rather than agreed, attendance decays quietly and the programme ends with a cohort of three. The countermeasure is stating the time cost precisely before enrolment and getting an explicit agreement from participants and their managers.
Evaluation that measures the wrong thing. Satisfaction surveys are easy to run and tell you almost nothing about whether behaviour changed. The countermeasure is agreeing what will be measured, at which level, before the programme starts, when it is still possible to capture a baseline.
None of these is exotic. All four are visible in advance, which is what makes them worth designing against.
Evaluating Something Other Than Satisfaction
Evaluation of training and development is a field with established models, and using one of them is considerably better than inventing a questionnaire. The Kirkpatrick model organises evaluation into successive levels, and the extension associated with Phillips adds a financial layer on top of them. In the order they are usually applied, the levels ask:
- Reaction — what participants thought of the experience, gathered immediately, useful for improving delivery and for nothing else.
- Learning — whether knowledge and skill actually increased, established by comparing a measurement before the programme with one after it, plus practical demonstration.
- Behaviour — whether the new competency is visible in daily work, read some months later through structured observation and through the judgement of the people who work with the participant.
- Results — whether the indicators the organisation cares about moved, using measures agreed with the sponsor before the programme rather than selected afterwards.
- Return on investment — whether the financial value of the change exceeds what the programme cost, which requires isolating the programme’s contribution from everything else that happened in the same period.
The levels get harder and more expensive as the list descends, and most organisations are honest enough to stop partway. That is a legitimate choice provided it is a choice. What is not legitimate is presenting reaction data as evidence of effect, which is the most common form of self-deception in this field.
The practical rule is that the evaluation plan is written at the same time as the programme design, with the sponsor in the room. An indicator chosen after the fact tends to be the one that happens to look good.
How This Applies to a Technical Specialism
Nothing above is specific to soft skills, and it is worth showing the argument working on a technical example rather than asserting that it generalises.
Take a specialist course in packet-level network diagnostics. As a body of material it is close to ideal for a point training: the subject is bounded, the exercises have right answers, and a competent participant leaves able to do something they could not do on Monday. There is no case for wrapping a long programme around it — the advanced network diagnostics with Wireshark format exists precisely because that shape fits that content.
The picture changes one step further along. The follow-on discipline of advanced network troubleshooting is not only a tool skill: it is judgement exercised under time pressure, usually while other people are waiting and someone senior is asking for an estimate. That is a competency the workshop can teach and cannot install. It is the kind of skill where a mentoring wrapper earns its cost, because what the participant needs afterwards is not more material but someone to review the calls they made during a real incident.
The same distinction appears in software work. A course on bot design and implementation delivers an architecture and a method; whether the engineer then makes good design decisions in their own codebase, against their own constraints, is decided over months in the work itself. The form follows the content, not the subject area — and this is why the question point training or programme? has to be asked separately for every competency, not answered once for a department.
There is a career-path dimension to this as well, and it points in a useful direction for anyone deciding what to fund. The argument for pairing training with mentoring is strongest exactly where the return on training is being questioned, which is the same ground covered in Are Network Engineer Trainings Worth It? — the return depends heavily on what happens in the months after the course, not on the course. And for anyone mapping the sequence of competencies rather than a single course, the network engineer career path sets out the progression that a combined programme would be designed to accelerate. Read in that order, the two questions turn out to be one question: whether the organisation is buying a course or buying a change in what somebody can do.
Frequently Asked Questions
How long does a combined training and mentoring programme usually run?
Long enough for participants to apply the material in real work and bring the results back. In practice that means a horizon measured in months rather than days, because the behaviour being changed has to be attempted, fail, be adjusted and be attempted again before anyone can say it has held. A programme shorter than that is a workshop with a follow-up call attached to it, which is a reasonable thing to buy but should not be called a development programme.
What is the difference between a mentoring programme and a combined development programme?
A mentoring programme owns the relationship: pairing, cadence, preparation of both sides, confidentiality, and the handling of what goes wrong between two people. A combined development programme owns that plus the content — it decides what is taught formally, what is practised on the job under supervision, and what can only be addressed one to one. Buying the relationship without the content produces good conversations with no shared reference point; buying the content without the relationship produces the workshop problem this article opens with.
Is mentoring worth adding to purely technical training?
It depends on what the training is for, not on whether the subject is technical. A bounded tool skill with clear right answers generally survives on its own, because the participant can verify their own work and correct it. A skill exercised under pressure, against colleagues’ habits, a manager’s priorities and an incomplete picture, generally does not — and that description covers a great deal of senior technical work. The test is not is this soft or technical? but can the participant tell, unaided, whether they did it well?
Who has to be involved for a combined programme to work?
Three parties, and the one most often left out is the middle one. The participant has to commit the time and do the work between sessions. The mentor has to be selected and prepared for the role rather than volunteered for it. The participant’s manager has to know what is being attempted and adjust expectations accordingly during the period when the participant is deliberately working in an unfamiliar way. A programme designed without the manager tends to produce participants who learn a new approach and then quietly abandon it because nobody above them expected the temporary drop in speed.