The original design for PULSE was straightforward: show users their weekly numbers. Meeting percentage, focus hours, category breakdown, trends. Lay out the data cleanly, let people draw their own conclusions. We thought the insight would be in the numbers.
What We Noticed
We were partly right. Users who looked at their numbers regularly made better decisions about their calendars than users who did not. That part worked as expected. What we did not anticipate was the gap between users who looked at the data and users who also wrote anything alongside it — even two or three sentences.
The writing users were different in a specific way: they made more durable changes. Not just recognizing a pattern and making a note of it, but actually restructuring their calendars and keeping the restructure. The data alone seemed to produce awareness. The writing seemed to produce commitment.
The Feature Evolution
We added a prompted reflection question alongside the weekly data. Not a journal prompt, not an open-ended field — a specific, short question that forces you to interpret what you are seeing rather than just observe it.
- →What worked this week?
- →What got crowded out?
- →What do you want to protect next week?
Three questions, one per week in rotation. The expectation was a sentence or two per question. Not a report, not a deep reflection session — just enough to put the interpretation in words.
The Unexpected Outcome
Users who wrote even two to three sentences weekly reported feeling significantly more in control of their time than users who reviewed the same data without writing. The numbers were the same. The feeling was not.
The mechanism, as best we can understand it: writing makes the pattern concrete in a different way than reading a number does. When you write "focus time got crowded out by three unplanned calls on Tuesday," you have committed to an interpretation. It is no longer a number on a chart that you noticed and moved on from. It is a sentence in your own words that names a specific thing that happened.
What This Changed About the Product
We had been building PULSE as an analytics tool. The Reflect feature reframed it as something slightly different: a structured feedback loop between your calendar data and your own understanding of what the week was actually like. The data is the input. The writing is where you process it. The combination is what produces the kind of awareness that leads to real calendar change, not just recognition.