The quantified self, without the spreadsheets
In 2007, Gary Wolf and Kevin Kelly coined the phrase “self-knowledge through numbers.” They started the Quantified Self movement, a community of people who tracked their own bodies and behaviors with sensors, spreadsheets, and scripts. Blood pressure logs. Sleep histograms. Step counts cross-referenced with mood scores. The promise was simple: measure yourself, understand yourself.
Almost two decades later, the impulse has gone mainstream. Fitbits ship by the millions. Apple Watch closes rings. Strava segments have their own subculture. The average smartphone owner generates more biometric and behavioral data in a week than a QS pioneer collected in a year.
And yet most of that data sits unread.
The spreadsheet ceiling
The quantified self community ran into a problem that no sensor could solve. Data collection scaled beautifully. Data interpretation did not.
A heart rate log tells you your resting pulse was 58 bpm on March 12. It does not tell you that March 12 was the day you gave a presentation that went surprisingly well, then celebrated with a long walk through a neighborhood you had never explored. The number is precise. The number is also meaningless without the day around it.
QS practitioners knew this. The most dedicated ones maintained elaborate personal dashboards: Notion databases, Google Sheets with pivot tables, custom R scripts. Some spent more time organizing their data than living the days the data described. The community even developed a name for the failure mode: the “burden of tracking.”
Wikipedia’s entry on the quantified self cites research showing that self-tracking can become a source of stress rather than insight, particularly when people focus on collection but never reach the stages of analysis and reflection. The numbers accumulate. The meaning does not follow.
Numbers describe. Stories explain.
The QS movement’s tagline, “self-knowledge through numbers,” contains an assumption worth questioning. Numbers are a medium of description. They answer “what” and “how much.” They rarely answer “what was it like.”
Consider two records of the same Thursday:
The quantified version:
- 7,243 steps
- 6h 42m sleep
- 4 meetings (2h 15m total)
- 12 tasks completed
- Screen time: 9h 18m
The narrative version:
Thursday started slow after a short night. The morning was back-to-back meetings, but after lunch things opened up. You cleared a backlog of small tasks, pushed a fix that had been bothering you since Monday, and left early enough to walk home instead of taking the train. Steam says you played Hades for 40 minutes before bed.
Both are accurate. Only one will mean anything to you in six months.
The quantified version is a dashboard. The narrative version is a diary entry. Dashboards are useful for optimization. Diary entries are useful for remembering what your life felt like.
What the QS movement got right
Dismissing the quantified self would be a mistake. The movement established three ideas that turned out to be foundational:
1. Passive collection beats active logging. The reason Fitbit succeeded where handwritten exercise logs failed is that it removed the daily decision. You did not have to remember to record your run. The watch was already recording. Every successful self-tracking tool since has followed this principle.
2. Your existing tools already know more than you think. Google Calendar knows where you were. Todoist knows what you finished. GitHub knows what you built. Slack knows who you talked to. The QS insight was that these tools are sensors, even when their designers did not intend them to be.
3. Consistency matters more than depth. A QS practitioner with 300 days of basic data always had more insight than someone with 10 days of elaborate data. The long record is what reveals patterns, shifts, and seasons.
These three principles, passive collection, existing tools as sensors, and consistency over depth, are exactly the foundation that automatic journaling builds on. The difference is what happens after the data is collected.
From dashboard to diary
The quantified self stops at the dashboard. The data is structured, timestamped, and categorized, but it remains rows and columns. To extract meaning, you have to be your own analyst. You have to remember what the numbers refer to, connect events across different tools, and construct the narrative in your head.
This is the step that most people skip. Not because they are lazy, but because the cognitive work of turning data into understanding is real work, and it competes with everything else demanding attention at the end of the day.
Automatic journaling picks up where the dashboard leaves off. It takes the same data sources the QS movement identified (calendars, task managers, communication tools, fitness trackers, code repositories) and runs them through an LLM that does the narrative assembly. The output is not a chart. It is a paragraph, written in the order your day actually unfolded, connecting the meeting with the task with the walk with the game session.
You do not have to interpret the data. The interpretation is the product.
The QS community’s criticism, addressed
The quantified self community has been thoughtful about its own limitations. Three recurring critiques are worth addressing directly, because automatic journaling handles each one differently.
“Data fetishism.” Researchers have described how self-trackers can become more attached to the numbers than to what the numbers represent. A step count becomes a goal in itself, disconnected from whether the walk was enjoyable. A diary entry has no score to optimize. It is a record of a day, not a performance metric.
“Health literacy.” The QS community has acknowledged that most people lack the skills to analyze their own data meaningfully. Raw numbers require statistical literacy, context, and domain expertise to interpret correctly. A narrative diary entry requires none of those. You read it the way you read a letter from a friend describing their day.
“Burden of tracking.” The most common reason people abandon self-tracking is that it feels like work. An automatic diary removes the tracking burden entirely: the data flows from tools you were already using, and the diary appears without any action on your part.
What this looks like in practice
A quantified self setup for a typical knowledge worker might include a Fitbit for health data, Toggl for time tracking, a habit tracker, and a custom spreadsheet that pulls everything together. Maintaining this takes 15 to 30 minutes per day, plus periodic analysis sessions.
An automatic diary pulls from Google Calendar (meetings and events), Todoist (completed tasks), Slack (conversations), GitHub (commits and pull requests), and Steam (gaming sessions). The user connects these once. From then on, a diary entry appears every morning covering the previous day. No spreadsheets. No manual entry. No analysis sessions.
The first approach tells you that you spent 2.3 hours in meetings on Tuesday. The second approach tells you that Tuesday’s meetings ran long, but you still managed to ship the feature you had been working on, and you unwound with an hour of Stardew Valley before bed.
Both approaches respect the same insight: your tools know what you did. They differ on what to do with that knowledge.
The next generation of self-knowledge
The quantified self movement was ahead of its time. It recognized that ordinary life produces extraordinary amounts of data, and that this data could serve the person who generated it, not just the platforms that collected it. That insight has only become more true as software has grown more pervasive.
What has changed is the technology available to close the gap between data and understanding. In 2007, turning raw data into a readable account of your day required a human (you) sitting down with a spreadsheet. In 2026, an LLM can do the assembly step, the part that was always the bottleneck.
The quantified self asked: “What can I learn about myself from my data?”
Automatic journaling asks the same question, then answers it for you, every day, in a format you can read in two minutes and revisit for years.
deariary connects to the tools you already use (Google Calendar, Todoist, Slack, GitHub, Steam, Bluesky, and more) and generates a daily diary entry automatically. No spreadsheets required. The free plan includes one integration. Connect more to build a richer picture of each day.
