3 ms·
Write a knowledge base, or Wiki, or FAQ, or whatever. A place where they can re-read the same thing 10000 times. Maybe add some examples too, in cases where it
by drclau 5y ago
Write a knowledge base, or Wiki, or FAQ, or whatever. A place where they can re-read the same thing 10000 times. Maybe add some examples too, in cases where it makes sense (i.e. code).
Even better, make them write it, and you just review it. It'll help them learn faster.
If you have a junior who already understand problem X, ask them to explain it to someone else too. It'll help solidify the knowledge, and at the same time offload you too.
Take my comment as wisdom that came with age and experience, if you will :). I don't think the above would have been my first thought 10 or 15 years back.
- lanstin 5y agoOne approach I have been experimenting with is copied from surgeons: see one, do one, teach one. We have documents and so on, but for novel Devops-ish rocedures, I will document it, but then pick some to watch on screen share, then the next time they will drive, and I will watch their screen share, then the next time they will demo to another person. It is great for tasks in between we do it every day” and “we’ve never done it before”. Also it builds confidence (and often the docs are better after the train gets a good writer as the see one person).