Make it easier for everyone to track the status of tasks by sending tasks one email at a time, and make the requests very clear. When a person has completed a task they just have to reply "Done" to that email, delete the email from their inbox and then move on to the next task.
Grouping related tasks
Obviously, if you are requesting many small changes to the same page, use one email as they're related to the same topic. In this case number each task that you wish to be completed, as per "Do you number small tasks related to 1 topic". If all the tasks are very simple and everything was done as specified, the person who completed the tasks replies with a single "Done" to the whole email.
Warning: Don't group unrelated topics
Figure: Good Example - A few related tasks in one email
Breaking up monster tasks
If you have a very large task that requires days of work, it is better to break it up and send separate emails. So that a task "Boil the Ocean" would become:
- "Boil the Ocean #1",
- "Boil the Ocean #2",
- "Boil the Ocean #3" etc.
The advantages are that you get an email history on a specific part and it is easier to include someone else.
Tip: Understand tasks sizes by reading: Estimating - Do you know how to size user stories effectively?
Figure: Bad Example - One email for multiple separate tasks Figure: Good Example - Separate emails for separate tasks
TODO: Make grey boxes with clear separated emails - change from IIS to Git Repo + will become 3 emails
When replying to these emails, reply to each email individually. Don't consolidate them all into one as it leaves unfinished email threads.