I Compared What I Told My Group Chat to What My Phone Recorded
For 30 mornings, I logged what I told my accountability group about waking up next to what my phone's own timestamps said. The gap wasn't huge, but where it showed up was more interesting than the size of it.
In this article3 sections
For thirty mornings I kept two records of the same fact: what I typed into my accountability group’s thread about whether I’d gotten up on time, and what my phone’s own timestamps — screen-on time, first app opened, first outgoing message — said actually happened. I wasn’t trying to catch myself lying. I was trying to find out whether “I got up on time” is even a fact with a clean yes or no, once you go looking for the exact minute.
Day one: alarm at 6:15, phone screen-on logged at 6:17, first message to the group sent at 6:19: “up, bit groggy but up.” That’s accurate enough that it’s barely interesting. Most of the thirty mornings looked like that — the reported version and the timestamped version agreed within a couple of minutes, which is the boring, expected result and worth saying plainly before the interesting part, because the interesting part is easy to overstate if you skip the boring majority.
The interesting part showed up on six mornings out of thirty, and it clustered in a specific way: every one of those six was a morning where I’d woken up on the alarm, then gone back to a state that wasn’t quite sleep and wasn’t quite awake — phone off, eyes closed, not dozing exactly, more like refusing to commit to the day — for somewhere between twelve and twenty-six minutes. On five of those six mornings, what I typed to the group was some version of “up,” sent as soon as I finally did get moving, with no mention of the gap. Not a lie, technically — I had gotten up, eventually, by the time I sent the message — but the message collapsed a twenty-minute stall into a single clean data point that made the morning look like every other on-time morning.
The gap wasn’t about clean failures
Here’s what surprised me: the mornings I actually missed the target — three of them, out of thirty — I reported accurately, immediately, no softening. “Slept through it, up at 7:40.” There was no ambiguity to manage on those mornings; the outcome was already bad, so there was nothing to round in a better direction. The distortion, such as it was, lived entirely in the mushy middle — the mornings that were technically fine but didn’t feel fine, where I had a real choice about how to describe twenty minutes of not-quite-anything.
That matches something I hadn’t been looking for going in: self-report doesn’t drift evenly across outcomes. It drifts hardest around the outcomes that don’t have an obvious honest answer, because an ambiguous morning requires a decision about how to describe it, and a decision made under mild self-interest tends to go the easier way. A clean success reports itself. A clean failure reports itself, because there’s nothing left to protect. It’s the twenty minutes in between where the story gets written after the fact instead of recorded during it.
What this does and doesn’t tell you
Thirty mornings, one person, no control group, no second data source besides my own phone’s logs — I want to be upfront that this is closer to a diary than a study, and the six-out-of-thirty gap could easily be a quirk of this specific month rather than a stable rate. I also can’t rule out that keeping this second log changed my behavior on the mornings I knew I’d be checking it later, which is its own kind of distortion layered on top of the one I was trying to measure.
What it did change for me: I stopped treating “up” as a single event, the same binary a working definition of a commitment device assumes by default, and started treating it as a range, and I started reporting the range instead of the endpoint — “up at 6:15, actually moving by 6:35” — to a group that, it turns out, didn’t care nearly as much about the twenty minutes as I’d assumed they would when I was the one deciding whether to mention it.
If your own check-in has ever quietly rounded a stall into a clean “up,” you’re not unusual — what makes a good accountability witness turns out to depend less on how strict they are about the report and more on whether the reporting method leaves room to round in the first place, which is the actual argument for a timestamped photo over a typed message: not that people lie, but that a photo doesn’t have a version of itself it can quietly choose to send instead.
Would a photo-based app have caught my own six mushy-middle mornings? Yes, all six — the window closes and the group sees a miss, with no twenty-minute buffer to describe favorably after the fact, which happens to be how DontSnooze works. Would it have caught what my typed check-ins were quietly good at — “up but my kid was sick all night,” the context a photo can’t carry and a friend can actually do something with? No. I traded one blind spot for a different one, and I’m not sure yet which trade I’d make again.
FAQ
Are people honest when they self-report to an accountability partner or group?
Mostly, but not evenly — small self-experiments and behavioral research both suggest self-reports drift most around borderline or embarrassing outcomes, not clean successes or clean failures, which is why verification methods tend to catch the cases self-report is worst at, not the average case.
Why do people round up when reporting habits to an accountability partner?
The leading explanation isn’t deliberate lying — it’s that an ambiguous outcome (waking up but staying in bed for twenty minutes, for instance) doesn’t have an obvious honest answer, and people tend to resolve that ambiguity in the direction that costs them less social friction to report.