An early version of the Juta recap email tried to include everything: full message transcripts, mood indicators, response-time stats, a running log of topics discussed. It looked thorough. It felt responsible. Almost nobody read past the first two lines.
That was the first real lesson: a family checking a recap at 8pm after a full day isn't looking for a report. They're looking for one thing, answered fast. Is my person okay today?
What we cut, and why
We cut the transcript. Reading a loved one's private conversation felt more like surveillance than connection anyway, and nobody asked for it. We cut the stats. A "response time: 4 minutes" data point told families nothing about how their parent was actually doing. We cut the running log, because a week's worth of history in every email just meant nobody found today's update.
What was left was smaller, and better: one paragraph, written like a person would say it out loud. Today was good. She mentioned the garden again. He asked about the grandkids' game this weekend. Short, specific, human.
The part that surprised us
We expected some pushback for cutting detail. Instead, open rates and reply-backs from families went up, not down. The families reading these emails aren't case managers. They're sons and daughters who want the same feeling a good phone call used to give them: a quick, warm sense that today was fine, not a dataset to parse after a long day.
The job of the recap isn't to prove something happened. It's to make a family feel, in fifteen seconds, that their person is okay.
Every design choice since has used that same test: does this make the fifteen-second version better, or just longer? See what a real recap looks like.