Do you split emails by topic?


People often overlook or miss items in long, carefully drafted emails. To improve clarity and task completion, it's more effective to send separate emails for unrelated (or independent) tasks.

Each email should focus on one task or multiple tasks that are directly related or interdependent. This helps recipients complete the tasks, reply with "Done," delete the email, and move on to the next without confusion. Additionally, ensure your requests are clear and concise to minimize misunderstandings.

If you are requesting many smaller tasks under the same topic, you should group them in the same email. In this case, number each task that you wish to be completed.

Break up unrelated tasks

If you have a list of things to be done, and find that your requests are not directly related (don't depend on each other OR are not to be done in the same environment), it is better to break it up and send separate emails.

Figure: Bad example - One email for multiple unrelated tasks (domains vs styling)

Figure: Good example - Separate emails for unrelated tasks. A few related tasks in the same email

Break up monster tasks

If you have a very large task that requires days of work, it is also better to break it up and send separate related emails. A big task like "Boil the Ocean" would become several emails with consistent subjects:

  • "Boil the Ocean #1",
  • "Boil the Ocean #2",
  • "Boil the Ocean #3", etc

The advantages are that you get an email history for specific parts, making it easier to include someone else and follow up.

Tip: Understand tasks sizes by reading how to size user stories effectively.

Replying 'Dones'

When replying to emails, always reply to each email individually. Never consolidate separate emails into one as it leaves unfinished email threads.

Learn more about the best ways to reply "Dones".


We open source.Loving SSW Rules? Star us on GitHub. Star
Stand by... we're migrating this site to TinaCMS