OJT Isn't Teaching — It's Designing a Path to Autonomy
“I’ve been put in charge of training a junior colleague, but I don’t know where to start.” “I keep doing the work myself, and they never quite become independent.” I don’t think trainers wrestling with this are rare. Going through a recent training program, I recognized myself running straight into that exact wall.
The real endpoint of OJT isn’t a one-time skill
The first thing the training reframed for me was bigger than I expected: the real endpoint of on-the-job training isn’t a one-time skill transfer — it’s establishing a culture where people grow.
Building an organization where people actually grow requires three layers to align: environment (strategy, HR systems, and other structural scaffolding), skill (a systematic method for training people), and mindset (a proactive stance toward developing others). The mindset layer struck me the hardest. “I struggled through this myself, so my junior colleague should too” — that sounds like toughening someone up, but it’s actually closer to abandoning the job of developing them. Instead of romanticizing your own past struggle, the shift is to use what you learned from it to build a better path for the person coming up behind you. That shift toward taking responsibility for someone else’s growth is, I think, where real development begins.
A six-month roadmap toward working without support
For the training exercise, I set this goal: “understanding the business context, have the trainee able to explain the system’s spec and design alone, without a supervisor’s support, within six months” — then designed phases by working backward from it.
| Phase | Theme | Learning cycle |
|---|---|---|
| 1 (Why) | Understand why it exists, what problem it solves | Investigate → explain → revise |
| 2 (What) | Get an overview of capabilities through hands-on use | Operate → question → investigate → ask |
| 3 (How) | Read design intent from specs and design docs | Read → write in your own words → get reviewed |
| 4 (Integrate) | Consolidate context, design, and features into one document | Structure → write → mid-review → revise |
| 5 (Independence) | Explain to stakeholders, trainer present | Rehearse → deliver → reflect |
What stayed consistent across every phase was never leaving “go look into it” or “go read it” as the entire instruction — always pairing a chance to explain with a chance to get feedback. And treating confusion as something to welcome rather than penalize, so the trainee feels safe saying “I don’t understand this.” That posture echoes what I wrote in Knowing psychological safety isn’t enough — the four stages: understand, design, implement, reproduce — turning understanding into something actually implemented.
Reading setbacks through the iceberg model
When a junior colleague stumbles, is the visible mistake the only thing getting addressed? The training introduced a way of reading setbacks through an iceberg model. What’s visible above the waterline — the mistake, the misstep — sits on top of three possible root causes hidden below: a skill gap (run through the training again, staying alongside them until they build a success), a mindset issue (approach it through questions and dialogue rather than lecturing, since the person often isn’t even aware of it), or flagging motivation (acknowledge growth by comparing them to their own past self, and recalibrate if the goal is too far out of reach). Not handing over the answer, and instead asking a question that leads someone to their own realization, is the same instinct behind From Funeral to Adventure: A Manager’s Real Art of Asking — treating the other person as someone whose own understanding is worth drawing out.
Five postures a trainer needs
| Posture | What it looks like |
|---|---|
| Don’t rush | Growth paces differently for everyone — stay with the plan |
| Don’t hand over the answer | Ask a question that makes them think, and let the answer come from them |
| Wait for their words | Don’t fear silence — let them get there in their own language |
| Turn failure into the next step | Treat it as material for reflection, not something to punish |
| Name growth explicitly | Say “you can do this on your own now,” out loud |
“Don’t hand over the answer” is, I think, one of the hardest things to hold onto in day-to-day work. The busier you are, the more tempting it is to just say “here’s how you do it.” Every time I optimize for that moment’s efficiency, though, I’m taking away a chance for someone else to think it through themselves — the training forced me to confront that directly. Telling someone “you can do this on your own now” isn’t just an evaluation. It’s the same practice I described in Autonomy support runs both ways: reading Why We Do What We Do — how you behave can directly support someone else’s sense of competence.
Closing thoughts
Handing over knowledge alone can be done with a briefing or a shared document. But a junior colleague is only truly “grown” once they can think for themselves, investigate for themselves, organize what they’ve learned, and explain it in their own words. That’s the point where OJT actually creates value.
And getting someone there requires the trainer to bring their own resolve and posture to the table. Developing someone else is itself a way you grow. In the process of designing someone else’s growth, the trainer grows too — that realization was the biggest thing I took from this training.
I cover the actual six-month OJT plan template I built for this in How to Use an OJT Plan Template: Goals to Final Review.
Related Articles
- Knowing psychological safety isn’t enough — the four stages: understand, design, implement, reproduce — turning understanding into something a team can actually reproduce
- From Funeral to Adventure: A Manager’s Real Art of Asking — asking questions that draw out someone’s own understanding
- Autonomy support runs both ways: reading Why We Do What We Do — how your own behavior can nurture someone else’s sense of competence