Documenting is a way of keeping a record for not only for our own benefit but for those also affected by what we do. It is how we make sure that others aren’t incapacitated in our absence. And, in some ways also helpful in training others. We’ve explored these and other reasons in earlier posts. And, in a post preceding (Best Documenting Practices) this one in the Document It series, we explored some best practices. This series would be incomplete without looking at how to document.
This is one of the posts in a Document It series. The idea of the series is to look at documenting as part of the way of working in church life. In this post we’ve established the importance. Among other reasons, we determined that documenting alleviates a single point of failure. This post addressed some myths of documenting, which often stop people from doing so. It is only logical that we look at best-documenting practices.
I’ll admit upfront: this list is not exhaustive, but I hope it’ll be helpful for you and your team. Church life needn’t suffer for no good reason. So, best practices are about standardizing how you document.
Documenting why and how we do something as a church or as a church tech team is important. It helps us keep important details safe, and accessible to others we work with. It is a way to safeguard that the Church’s mission is not compromised by our absence. You can read about the importance of documenting in this first published post in the series. We need to look into some of the things that get in the way of documenting. This makes a post on debunking the myths of documenting appropriately.
The other day I was talking to a friend and he confided in me that he is finding it hard to keep track of all the different threads going on in his life. It was especially tough switching between different types of tasks and not wasting time working out what to do next. He ended it by saying that he probably needed to get one of these task management tools to keep track of all the things he needs to do. The only problem was that he didn’t know which to pick.
After all, there are hundreds out there, many with very similar features, some with utterly unique items and many built around a specific methodology that may dramatically impact your adoption or not.
This makes it hard to pick one tool, which is why we put this roundup together. Unfortunately, that is also why it is hard to recommend just one option. As such, we’ve split the review into several different categories which include different tools which are recommended for different functions. At the same time, we do have one particular recommendation at the end which is probably a good starting point for most people.
With that in mind, this is going to be the layout for the rest of the review:
When it comes to productivity, a simple system is often going to trump a very complex one. There’s a very obvious reason for that, a complex system usually takes more time and effort to manage and is harder to remember. Something which is simple gets out of the way for you and lets you focus on the important part of productivity; getting your work done.
We all want to get stuff done, and get it done as easy as possible.
In your quest for productivity, you might have found a “hero” you wish you were as productive as. You study his or her tools and systems; you spend time implementing those tools on your workflow; you try hard to maintain the system… and you fail.
There might be a simple answer: Those tools don’t suit you.