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.
Team User Manuals
|
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 |
The Outlier Team
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.
"Why are so many people in this meeting?" I remember asking myself that question after attending a 90-minute committee meeting early in my career. Before that role, I had worked with an organization that was intentionally reducing the number of meetings employees attended. Meetings became shorter. Agendas became clearer. When a topic required deeper discussion, only the people who were directly involved met afterward. At the time, I assumed that was normal. Then I joined another organization...
Organizations often miss out on ROI because they struggle with using technology. Not because of lack of availability or training, but because of lack of adoption processes. One of the most effective ways we’ve seen organizations enhance adoption and increase technology usage and ROI is by building a Systems, Automation, and Technology (SAT) Committee. What is a SAT Committee? A SAT Committee is a cross-functional group made up of: Power users (the people who live in and are experts with your...
The last couple of weeks we have talked about pull systems and how to set them up in Microsoft Planner. This week, let’s discuss how to decide what work needs to be done next. When deciding what to work on next as a team, it’s important to assess strategic alignment, business value and return on investment, technical feasibility, resource availability, risk profile, stakeholder support, timeline/urgency, and regulatory and compliance areas. One can do this by considering the following...