SWS #06: Using a manual to solve YOUR biggest problems
There are loads of things you can document in a team manual.
You need to focus on the ones that solve your BIGGEST business problems.
Check it out: https://t.co/d8ReCp4Iw9
SWS #05: How a manual solves 4 BIG problems:
- Business leaders that are too busy
- The same mistakes keep happening
- Employees not quickly or fully onboarded
- Being reliant on key people
Check it out: https://t.co/WeDNdUuatU
We’re trained to always think about the business case.
But your manual is about so much more than good business!
Read on in SWS #01: This is bigger than business
https://t.co/P7XsqnOSVD
Product tip: Add a quick summary to each checklist you create
The summary should ideally include:
- When the checklist should be used
- Who should use it
- How long it will typically take
- Why it’s important (if not obvious!)
#Tip#AirManual#ProcessDocumentationTip
Be prepared to get new joiners up to speed in the event that a team member leaves.
How? By ensuring that guidance, checklists, onboarding and training are already in place.
Watch to this video to learn more.
https://t.co/0WhvOZN2zx
#AirManual#ProcessesDocumented
Product tip: Add a quick summary to each checklist so that anyone opening the checklist will understand when to use it, and what to expect.
The summary should include:
- When the checklist should be used
- Who should use it
- How long it will typically take
- Why it’s important!
One thing we hear from our customers is “I want to document everything”.
This is a bad idea!
Why? If you try to document everything at once, it means that you will be documenting some content that no-one urgently needs.
Doing so will feel like a distraction, and you’ll end up feeling demoralized and stopping.
Instead, prioritize the most important content then train your teams to deliver it.
But how do you know how to prioritize the most important content?
Are you prepared in the event that a team member leaves?
Getting people up to speed can often be time consuming and costly!
Don't leave these things for when you need them —everything should already be in place.
Learn more here.
https://t.co/0WhvOZN2zx
AirManual tip: When documenting checklists for your team to use, keep it high level.
In other words, only add detail where it’s really needed!
Once you’ve captured the high-level steps, you already have a process that your team can use.
If it needs a little extra guidance, or an image, a video, or a link… then go ahead and add it.
But don’t feel like you need to add extra detail to extra step. Y
our colleagues are (hopefully) smart people, so the high level description will often be enough.
Process documentation can be difficult.
It doesn't matter whether you're trying to document a complicated process, or just trying to help your team to do a simple task.