The Digest Email
One scheduled summary replaces a stream of interruptions with a single readable moment.
The problem it solves
Products generate more events than any person wants pushed at them. Sending each one trains people to mute the channel. A digest batches them into one arrival the user can plan around.
A digest is a scheduled batch. Everything that happened since the last one gets collected, ranked, and sent as a single message. The user trades immediacy for control, and most of the time that is a trade they want.
The design question is not frequency. It is what earns a slot. A digest with a fixed template that fires whether or not anything happened is a newsletter with your logo on it, and people unsubscribe from newsletters. A digest that sometimes says nothing happened is more trustworthy than one that always finds five things.
What goes in the slot
- Things addressed to this person: mentions, replies, assignments, approvals.
- Things that changed in something they own or follow.
- Things they would have searched for anyway, surfaced early.
- Nothing else. Promotional items in a digest teach people the digest is promotional.
Rank by whether the item needs a decision from this person, then by recency. Cap the list. A digest listing forty items is an archive, and archives do not get read on a phone at breakfast.
Three digest jobs
- Catch up
- For users who were away. Emphasise what changed and what is waiting on them. Works daily or weekly depending on how fast the product moves.
- Discover
- For users who would not have come looking. Emphasise the best of what is new. Quality of ranking is the whole product here, and a weak week should mean a shorter email.
- Reflect
- For users building a habit. Emphasise what they did rather than what the product did. Closer to a weekly review than to a notification.
Every digest needs a subject line that survives the inbox list view. Put the single most specific item in it. A subject line reading Your weekly summary competes with every other product sending the same words at the same hour. A subject line naming the person who replied to them does not.
Worked example
A quiet week
Imagine a project tool whose Monday digest normally carries eight items. This week a team was on holiday and there are two. The tempting fix is to pad with tips and suggested features. The better move is to send two items and a short line saying it was a quiet week. The cost is one thin email. The return is that the user keeps believing the length of the email means something.
When it fits
- Activity arrives faster than a user would choose to read it, but almost none of it is urgent.
- The user has a predictable moment in their week, like a Monday planning slot, that the send can attach to.
- You can rank items by relevance to this specific person rather than by global popularity.
- You would rather own one reliable channel than ten interruptions.
When it backfires
- The content is genuinely time sensitive. Batching a delivery failure or a security alert into a weekly email is a support incident waiting to happen.
- Ranking is weak, so the digest is mostly noise. Users learn the pattern in about three sends and stop opening, and winning that attention back is harder than earning it was.
- The digest fires on a fixed template regardless of activity. Empty weeks padded with filler tell the user the email is about your metrics.
- It is used as a second marketing channel. One promotional insert moves the email from useful to ignorable, and the unsubscribe takes the useful part with it.
Products using it
GitHub
Batches repository and thread activity into scheduled notification emails, with per-repository and per-thread controls over what qualifies.
Slack
Sends a missed-activity summary to users who were not online, listing mentions and unread channel highlights rather than every message.
Substack
Offers readers a periodic roundup of posts from their subscriptions instead of a separate email per publication.
The psychology under it
The takeaway
A digest earns its place by being the only interruption, which means the day it starts carrying filler is the day it stops working.
Finished the teardown? Bank it and the day counts toward your run.