(Don’t) Read The Manual
<p>On my first day on the job, I’ve been given a link to the team’s documentation wiki, alongside a few important pointers on where to start.</p>
<p>This was very helpful in getting up to speed with setting up a development environment, but it lacked ideas and explanations only available at the time through face-to-face meetings.</p>
<p>Since then, our team has done a lot in improving ramp-up materials. For example, new employees update the wikis with gaps they recognize in their onboarding process. Another way is recording lectures, boot camp sessions, and video tutorials with the new employees, which helps capture questions and angles not explicitly explained in the written material.</p>
<p>Taking all this material, we created a thorough onboarding process that contains videos, as well as wikis, product explanations, and how-tos.</p>
<p>These are good approaches, and I sometimes come back to videos, wikis, and bootcamp materials to refresh my memory.</p>
<p>The problem is that I use these materials as a <strong>reference</strong> and at the same time I expect new employees to ramp up using the same materials.</p>
<p>At least for me, using reference materials for ramp-up doesn’t work, so I must understand if the same materials can be used for <em>reference</em> <strong>and</strong> <em>ramp-up</em><strong>.</strong></p>
<p><a href="https://levelup.gitconnected.com/dont-read-the-manual-3577e504f4a7"><strong>Visit Now</strong></a></p>