6 of 10Image
5. Clean up your code
When under pressure, we sometimes don't write the cleanest code or we may just forget to add comments. Everyone knows the benefits of clean code: easier debugging and rewriting and, in some cases, more efficient execution. We also know that when code is written poorly, cleaning it up can be a pain — so quieter times lend themselves to tackling this potentially laborious task.
Image credit: Shutterstock
6. Test new systems and software
We're always looking for new systems to use but we rarely have the time to test them out. It might be an open-source CMS you've been meaning to try for ages or some new groupware. When things are quiet you may finally get the chance to get those systems up and running and check them over to see if they're up to the job.
Image credit: Churl/Flickr
7. Document systems and software
Documentation is often left until last yet it's one of the most important tasks around. Without it, your systems end up relying on people's memories — and with the inevitable staff turnover, you could find yourself in a hole. When people leave, you still need to be able to log on to mission-critical servers. Take the opportunity of quiet periods to push on with the process of documenting your systems, software and users. In the end, you'll be glad you did.
Image credit: Boetter/Flickr