Treat important emails as part of the experience
By Gyata Tabiri · Revised October 30, 2026
An email often arrives in the middle of something a person is trying to do. I look at that moment as part of the experience: what has just happened, what needs to happen next, and whether the message makes that step easier.
Map the moment
Write down what triggers the message, what the recipient already knows, and what they need to do next. Consider a late arrival, an expired link, or a task that has already been completed. These are content and experience questions before they become layout questions.
Give the message an owner
Someone needs to maintain the wording, template, and sending logic. They may be different people. A useful review brings those responsibilities together and checks that the destination still fulfills the promise in the email.
Measure the relevant action
For a reset message, the useful outcome is whether people can reset their access. For an inquiry campaign, it may be a completed inquiry. Opens and clicks describe part of the journey, but do not establish that the person completed the task or that a design change caused the result.
Start small
Choose one important message, inspect its trigger and destination, and document what needs attention. An example inventory can include the trigger, owner, template version, primary action, and recovery path. That creates a manageable starting point without asking the team to rebuild every message.
That perspective helps a design or development discussion connect with product, content, and support needs. The email can then be reviewed against the task it supports, as well as how it looks.