I would plan for some slower performance at the beginning of the project. There may also be some setup time. Try to get the setup standardized.
If you need significant familiarization, then you may need some training time. Well done training should be more efficient than just playing around with the tools. Self-paced training is fine, and may be more efficient. Get some cheat-sheets, or develop project specific cheat-sheets.
EDIT: Project specific cheet-sheets can be of three varieties (or a combination there-of).
- Abbreviated cheat-sheets for tools used by the project omitting features not used by the project.
- Cheat-sheets for project specific tools and or libraries. Basically, anything project specific that could be on a cheat-sheet.
- Merged cheat-sheets for particular work-flows using multiple tools.
Automate your processes when you can. The cheat-sheet would then point to the appropriate automated process.
Consider using a Wiki to hold your cheat-sheets. This is also a good place to document your process. (It helps to document alternatives looked at and why the chosen one was selected.)