In the case of the latter, new solutions can be added to the wiki to grow knowledge. They also can refer to the wiki whenever they're unsure how to tackle a particular problem - whether there's an established solution, or if they have to come up with a new way of doing things. By writing down tech team processes, new engineers won't be so reliable on more experienced team members for historical knowledge. Technical teams can benefit from wiki content, too. □□□Īll the knowledge developers need to succeed. Each row contains a link to the team member's intro document, and also contains vital stats such as their arrival date, languages spoken, field of knowledge, and preferred emoji. Team Directory homepageĪt Slite, we use a Smart Table as the front page of our team directory. Tip: Take advantage of wiki features like comments and discussions to engage with colleagues' profiles, then follow up with a meeting to discuss their common interests. The best part about creating a wiki for your people? They can get to know each other on their own time. This way, newer team members can get to know more experienced ones, and vice versa. One of the best ways to keep everyone on the same page during a stage of change or growth is to create a team directory. We'll look at two company wide examples, and two team-specific ones, and share a template for you to create your own version of each. Keeping the last goal - learning and growth - in mind, we'll share some of the ways we use our own wiki at Slite. Create opportunities for self-paced learning.No matter how you choose to organize your wiki, remember your goals, which might be: Others create specialized wikis for certain departments, then nest those within a larger team wiki. Some companies need only one wiki for the entire organization. Now that you know what a wiki is, why it's useful, and how to create and design an effective internal wiki for your team, let's look at a few examples.
0 Comments
Leave a Reply. |