Most L&D teams in India inherit a training calendar rather than a learning design. The calendar has thirty-four dates on it, each one a two-day programme, each one with a venue, a trainer and a feedback form. Ask the team what changed in the business as a result and the honest answer is usually a pause, then a description of attendance percentages.
The calendar is not a stupid artefact. It is what procurement asks for, what the budget is built around, and what a trainer can be paid to deliver. It is also an event model, and an event model has a known ceiling.
The event and the journey
An event is a room, a date and a facilitator. Its unit of value is the day. A journey is a sequence that starts before the room and continues well after it, and its unit of value is a behaviour that is still visible in week nine.
The practical difference is not length. A five-day programme is still an event if all five days sit in the same week and nothing follows. A three-session journey of two hours each can be a genuine journey if the spacing is used for practice, review and a second attempt at the same task.
What makes it a journey is that the participant does something, gets a reaction to it, and does it again after a gap.
| Dimension | Event | Journey |
|---|---|---|
| Duration | One to three consecutive days | Eight to twelve weeks, four to six contact hours in total |
| Pre-work | Reading, if any | A real situation and a baseline assessment |
| Practice | In the room, on generic cases | In the room and at work, on the participant’s own cases |
| Manager role | Informed afterwards | Briefed before, checks in twice |
| Measurement | Reaction form on the last afternoon | Baseline and day-sixty re-assessment on the same instrument |
| Cost profile | Trainer fee plus venue, paid once | Fewer contact hours, more design and coordination time |
| Typical failure | Nothing changes after the room empties | Over-engineered, abandoned in week three |
Read the cost row carefully. A journey is usually cheaper in trainer days and more expensive in design and coordination, which means the saving appears in one budget line and the cost in another. Finance will notice only the first unless someone explains it.
What sits between the sessions
The content of the gaps matters more than the content of the sessions. Four things do most of the work.
- Pre-work with an artefact. Not reading. A one-page note from the participant describing a real situation they will handle differently, sent to the facilitator a week before session one. This is the diagnosis and the commitment in one document.
- Spaced practice. Two or three short assignments at roughly week two, week four and week seven, each taking under thirty minutes, each producing something the participant can show. Spacing is what converts a memory into a habit.
- Manager check-ins. Fifteen minutes inside a one-to-one that was already scheduled. The manager asks two questions, sees the artefact, and says whether the behaviour was visible. No new system, no form.
- A second assessment. The same instrument as the baseline, run again at day sixty, so the comparison is honest rather than rhetorical.
The manager check-in is the one that gets dropped first and matters most. Without it, the participant is practising for a facilitator who will never see them again. With it, someone with authority over their work is quietly watching for the behaviour, which is a stronger incentive than any certificate.
The sixty-day re-assessment
The re-assessment should be the same instrument used at baseline, administered by someone who did not facilitate the sessions. If the baseline was a scored role play, the day-sixty check is a scored role play with a different scenario. If the baseline was a sample of written work, the day-sixty check is a fresh sample scored blind.
Two rules make the result usable. First, score per behaviour rather than overall, so the report can say which of the four markers moved. Second, tell participants at the start that the day-sixty check exists and what it involves. A re-assessment that arrives as a surprise reads as an audit, and people respond to audits by protecting themselves rather than by demonstrating change. This is the same logic that makes assessment centres credible when they are designed as a development instrument rather than a filter.
Sixty days is a deliberate choice. Thirty is too early, because the behaviour is still being consciously performed and the novelty is doing the work. Ninety is long enough for a reorganisation, a transfer or a new manager to explain the result instead of the design. Sixty sits in the window where the answer means something.
Where journeys fail
Three failure modes account for most of the disappointments.
The first is scope inflation. A journey with eleven modules and a competency per module becomes an administrative programme, and participants start treating the assignments as compliance tasks to be cleared. Two or three behaviours across eight weeks is a realistic ceiling.
The second is a facilitator with no line of sight to the work. If the person reviewing the week-four assignment has never seen the participant’s actual output, the feedback drifts towards generic encouragement.
The third is a sponsor who signs off the design and disappears. Journeys need someone senior enough to ask, in month two, why the manager check-ins are not happening, and to mean it. Without that person, the week-seven session quietly becomes optional, and optional sessions do not happen in a quarter with a deadline in it.
A journey is not a longer programme. It is a programme in which something happens after the room empties.
Design the first one in a week
Pick one team, one behaviour and one measure. Write the pre-work note on a single page. Schedule four contact points over eight weeks, none longer than three hours. Brief the reporting managers in a thirty-minute call and give them the two questions to ask. Book the day-sixty re-assessment before session one, with the assessor named.
Then run it with twelve people and compare the day-sixty scores to the baseline. If the movement is real, you have an argument for the next programme that does not depend on a feedback score. If it is not, you have learned that in eight weeks instead of a year, and you still have the calendar to fall back on.
Development design support for this model sits under programmes, and the first conversation is usually about which behaviour is worth eight weeks. The conversation with employees changes shape too, because when a manager can point to a specific behaviour that improved, development becomes something the person can see rather than a promise made at appraisal, which is part of why people stay where that conversation is real.