|
Team issues are often caused by a lack of understanding. We often assume others know how we work, how to help us succeed, and if they don’t, they just figure it out over time. Team member user manuals can help with this though! A team member user manual is a short, personal guide that explains how to work well with someone. Think of it as the user manual for a human being. A user manual answers these questions about each team member:
When done well, they:
How to Create a User Manual There’s no right format for a team member user manual and they can be a simple document or an elaborate, creative slide deck, or anything in between. Each team member should write out the following information about themselves (in no particular order):
Some people will keep this a practical document and others will tell a story. Both are acceptable and valuable. Sharing User Manuals After each team member writes their user manual in the form of a Word document, PowerPoint, SharePoint site, or another format, they should be posted in a place that’s easy to share with their team. If the team is small enough, the next best step is to schedule a meeting where everyone shares their manual to enhance understanding and build a stronger team. PS: A shared space like Microsoft SharePoint is a great place to store and organize team member user manuals so they don’t disappear into inboxes or folders no one remembers to look at. If you want help setting that up in a clean, simple way, that’s exactly the kind of thing we help teams do at The Outlier Team. Just reply to this email for more information. Perry Myers |
We help small businesses with technology, strategy, and leadership and have a passion for sharing what we have learned. Subscribe to our newsletter to get helpful weekly content.
The Cost of Silence Several years ago, I went through one of the most difficult experiences of my professional career. A few weeks before Christmas, our CEO informed my boss that an outside IT consulting firm would be coming in to help evaluate our technology operations. At the time, I was the IT manager. The announcement raised a lot of questions. Why were they being brought in? What were they evaluating? What would happen afterward? Unfortunately, very few answers were provided. Weeks went...
Over the last two weeks, we’ve discussed meetings that run the business and improve the business. Today, let’s examine the third category: meetings that build the team. Before we do, I’d like to share a story. One summer morning at 2:00 AM, our team received an email that would turn into one of the largest technology incidents the world had ever experienced. Nearly every server and computer at our organization and others throughout the world would not power on. As people woke up, they began...
Meetings That Improve the Business Several years ago, our team was dealing with a frustrating login issue. About one person each week would be affected, and the disruption typically lasted only a few minutes. The team responsible for resolving the issue was actively working with the vendor. We held problem-solving sessions, investigated possible causes, and provided daily updates through email and Teams messages. The work was being done. People were understandably frustrated and wanted the...