I've found that spending a good chunk of my time documenting things has paid off in spades in for my team. Writing out common processes (what is our particular

I've found that spending a good chunk of my time documenting things has paid off in spades in for my team. Writing out common processes (what is our particular flavor of gitflow, how do we use it with Github, how are issues tracked, etc.) and common interfaces (what do you pass to this endpoint to get what results) makes every single person on the team function better. It also reduces the amount of time I have to spend answering questions--link to the wiki and move on. Now, actually getting others to buy-in to this is a different story: they don't usually see the point in working to sow the same sort of benefits they reap on a daily basis. I think a good lead needs to constantly strive to spread knowledge about the work as widely as possible.