Skip to main content
1 of 3
Dibstar
  • 4.5k
  • 5
  • 23
  • 41

There are two ways I have used in the past to get around this problem (particularly when my team has been lumped with a new software package and we’ve all had to get ourselves up to speed quickly):

Pair programming / buddy working is a great way of learning if you are both able to spend time simultaneously on the task – this enables a live review of each other’s work and anything that comes up which is unexpected can be addressed immediately. As problems are identified immediately and addressed at the same time, there is less wastage in terms of resource, and tasks will typically be finished to a superior quality.

Knowledge share / learning library: this is better if you are not able to work together on the same task as the same time. The key benefits of this approach are that by documenting wat you have learned in a way that can be easily understood by others, you become more comfortable with the key concepts. If you are going to use this approach, setting aside some dedicated time to run over what you have learnt that week with your colleague can be incredibly useful as discussing concepts is usually a better way for the other person to learn than simply by reading a guide. This reduces wasted time as you can both learn independently but still have access to learning that you might not have done yourself.

Dibstar
  • 4.5k
  • 5
  • 23
  • 41