Could, Would, Knew: A Working Model for Why Morning Commitments Break

Morning commitments break down for one of three distinct reasons: you weren’t capable of following through, you were capable but didn’t want to in the moment, or there was no clear point where you registered that today counted as a commitment day at all. Most people diagnose every missed morning as the second case — a failure of willpower — which is exactly why the fixes they reach for keep failing to hold.

Call the three branches capacity, motivation, and trigger. Capacity is whether you were physically and logistically able to do the thing — sleep, illness, a dead phone, a canceled train. Motivation is whether, given that you were able, you wanted to in that specific moment. Trigger is whether anything in your morning flagged that this particular day required action at all, as opposed to looking like just another day that happened to resemble every other day. Each is a separate variable, and a failure in one produces the same visible outcome — nothing happened — as a failure in either of the others.

That’s the core problem with how most people talk about broken routines. From the outside, an empty gym slot on a Tuesday looks identical whether you were sick, whether you decided the workout wasn’t worth it, or whether you never clocked that it was a running day in the first place. The three failures collapse into one symptom. Most advice, and most products built to address the symptom, treat it as if it only ever has one cause.

Could you have done it

Start with capacity, because it’s the branch people are quickest to rule out and slowest to check.

Picture waking up with a 101-degree fever, sheets damp, throat too raw to swallow water comfortably. There is no version of that morning where the missed commitment reflects anything about character or resolve. The body wasn’t available. Less dramatic versions of the same failure are far more common: a phone that died overnight because the cable slipped half out of the socket, an alarm set for 6:00pm instead of 6:00am, a canceled train that made the 7:00am gym session logistically impossible, a kid who woke up sick at 5:30 and needed a parent instead.

Capacity failures share a property that makes them easy to misdiagnose after the fact: by the time you’re reviewing the missed morning later that day, you usually feel fine, so the earlier incapacity is invisible in hindsight. You remember that you didn’t go. You don’t as easily remember that, at 6:00am, going genuinely wasn’t an option. The retrospective self reconstructs the morning as a choice, because a choice is the only kind of event the retrospective self knows how to file.

The fixes people reach for here are the most straightforward of the three branches, and also the most narrow: a backup alarm, a second alarm across the room, a phone charger that doesn’t come loose, telling a boss in advance that a sick kid is a live risk this week. These fixes work — for capacity. They do nothing for the other two branches, which is the recurring theme of this whole model.

Would you have done it

Motivation is the branch nearly every self-help book, every productivity newsletter, and every habit app is built to address, because it’s the branch that feels the most fixable through better willpower, better inspiration, or a better system of rewards.

The scene here is familiar: you’re awake, capable, aware that today is a commitment day, and you simply don’t want to. The bed is warm. The specific reason today mattered more than tomorrow isn’t obvious in the moment, even if it’s obvious on paper. Nothing external is stopping you. The only thing between you and the commitment is your own preference, right now, weighed against a future self’s preference that isn’t in the room to argue its case.

This is the branch that streak counters, motivational quotes, and completion animations are built to patch, and to be fair, they sometimes do — for a while, for people who were already close to compliant. The trouble is that the entire habit-app industry has converged on solving this one branch almost exclusively, to the point that the corpus of advice on broken routines reads as if capacity and trigger don’t exist. That’s the core critique in why habit apps optimize for engagement instead of behavior change: a lot of the tooling built around morning routines is really built to keep you opening the app, which only maps onto real behavior change if the miss you’re having is a motivation miss in the first place. Applied to a capacity failure — you were sick — a streak break just adds guilt on top of an outcome you never controlled. Applied to a trigger failure, it does nothing at all, because you have to already be aware of the commitment to feel bad about the streak.

Did you know today was the day

The third branch is the one that gets skipped in almost every conversation about broken routines, partly because it doesn’t produce the emotional residue the other two do. A capacity failure comes with frustration. A motivation failure comes with guilt. A trigger failure often comes with nothing at all — not even the memory of having decided against it — because the commitment was never evaluated in the first place.

A recurring commitment needs an unambiguous marker that distinguishes “today, this applies” from “today, it doesn’t,” and that marker is easier to lose than people expect. A runner on a Tuesday/Thursday schedule hits a public holiday that shifts the week around; the alarm still goes off at the usual time, the body still executes its usual half-asleep script, and because the script for a non-running day and the script for “I forgot it’s a running day” look identical from the inside, the run doesn’t happen and isn’t missed until well past the point where making it up is realistic. A commitment to read for twenty minutes before checking a phone gets skipped on the one morning that starts with an urgent work call already in progress, because the specific window the habit depended on never opened that day. A phone gets set to silent for a meeting the afternoon before and nobody remembers to undo it, so the alarm doesn’t fail — the phone just never surfaces it.

Nobody chose to skip these. The choice never got made, because the moment where a choice would have been made never registered. That’s the part worth sitting with: a capacity or motivation failure at least involves an instant you can point to and remember — I was too sick, I decided not to. A trigger failure frequently can’t be reconstructed at all, because there was no instant. The day simply passed through, unflagged, indistinguishable from every day the commitment didn’t apply.

Calendar reminders are the most common attempted fix here, and they’re a partial one at best. A notification that can be swiped away without being read isn’t functioning as a marker — it requires no acknowledgment, so a half-asleep dismissal leaves the exact same blank record a missing notification would have left. For a cue to close this branch, it has to require some response before it can be dismissed, not just appear and hope to be noticed.

Why most fixes only patch one branch

Line the common solutions up against the three branches and the pattern is obvious. A louder alarm, an alarm placed across the room, a backup charger — capacity fixes, and only capacity fixes. A streak, a motivational push notification, a reward for consistency — motivation fixes, and only motivation fixes. A calendar reminder, weak as it is — an attempted trigger fix, and not much else.

Almost nothing in wide use addresses more than one branch at once, and the practical result is that a person whose real problem is trigger absence will cycle through capacity fixes and motivation fixes, find neither one moves the number, and conclude the commitment itself was unrealistic — when the actual gap was never touched. This is a version of a broader pattern this blog has written about elsewhere: most accountability apps confuse commitment recording with commitment enforcement, building elaborate tracking on top of the assumption that the user already knows, every single day, whether today counts. If that assumption is wrong on a meaningful fraction of days, no amount of tracking rigor fixes it, because the tracking only starts once the trigger has already fired.

A way of seeing this that engineers will recognize

Software teams run a similar decomposition after an outage. Nobody asks “why didn’t the on-call engineer care” as a first question, because that conflates three separate and very different failures. Was the engineer reachable at all — phone charged, on the right rotation, not on a plane? That’s capacity. Did they see the page and misjudge the severity, deciding it could wait until morning? That’s closer to motivation, or at least judgment applied under real information. Or did the page never fire because a routing rule quietly pointed at the wrong number after a team reorg six months earlier? That’s a trigger failure, and it’s the one postmortems most often uncover, because it’s the one nobody would have thought to check first — there’s no visible near-miss to prompt suspicion, just an alert that silently never arrived.

Good postmortems separate these because the fix for each is unrelated to the others. You don’t put an engineer through more training when the real problem is that the page never reached a phone. Morning commitments reward the same separation, and for the same reason: treating every miss as a judgment failure means the fix you apply is aimed at a cause that, on a meaningful number of mornings, was never the actual one.

A related, established idea worth naming

This model rhymes with something more established: BJ Fogg, who runs the Behavior Design Lab at Stanford, first formalized his B=MAP model in a 2009 paper and later expanded it in his 2019 book Tiny Habits — behavior occurs when motivation, ability, and a prompt converge at the same moment. Capacity here maps loosely onto ability, motivation maps onto motivation, and trigger maps onto Fogg’s prompt. The overlap isn’t a coincidence; his work is part of what shaped the vocabulary this model borrows.

The differences matter, though, and are worth stating plainly rather than blurring the two together. Fogg’s model is general-purpose and forward-looking — a tool for building a new behavior so all three elements land at once. This model is scoped narrowly to recurring morning commitments and runs backward, applied after a miss to sort it into whichever branch broke. It isn’t a peer-reviewed theory, hasn’t been tested against data, and shouldn’t be mistaken for one. It’s a working tool, built specifically for this narrow situation, that happens to land in a similar shape to a better-known idea for a reasonable reason: both are trying to describe the same small number of things that have to be true at once for a person to act.

Applying it after a miss

The practical use of this model is a short debrief, run honestly, right after a commitment gets missed, before the retrospective self has had time to smooth the morning into a single story.

Could you have done it? If the honest answer is no — you were sick, the alarm malfunctioned, something outside your control blocked it — the fix belongs entirely in the capacity branch, and no amount of motivation work will touch it. Would you have done it, if someone had put the choice to you clearly at the time? If capacity was fine but the answer is still no, the miss belongs to motivation, and that’s the one branch where willpower-adjacent tools genuinely apply. Did you know, without having to reconstruct it after the fact, that today was a day it applied? If the honest answer is that you can’t remember deciding either way — no guilt, no frustration, just a blank — that’s very often a trigger failure wearing a motivation costume, and treating it as anything else won’t close the gap.

One narrow example of a tool built around the trigger branch specifically: DontSnooze pairs an alarm with a short window to send proof — a video or photo — that you’re up, and if that window closes, a friend who opted into the pact gets notified. That requirement exists to close the trigger-absence gap: a friend expecting proof creates an unambiguous cue that today counts, in a way a dismissible notification can’t. It says nothing about capacity or motivation, and isn’t built to.

Where this model breaks down

Two limitations are worth stating rather than glossing over. First, real mornings rarely fail cleanly along one branch. Bad sleep can quietly erode both capacity and motivation on the same morning, and a schedule disruption can wipe out the trigger while also making you less inclined to comply even if you’d noticed. Treating a miss as strictly one branch or another is a simplification that helps with a first pass, not a guarantee of a single clean cause.

Second, this model has nothing useful to say about the mornings where the underlying issue is chronic rather than incidental — a shift-work schedule that never lets sleep stabilize, a health condition that makes mornings unpredictable in a way no single day’s diagnosis captures. Those situations sit above any individual morning’s postmortem, and applying a three-question checklist to them risks making a chronic, ongoing circumstance look like a one-off miss with a one-off fix. The model is useful for exactly what it was built for: sorting the ordinary, recurring misses of an otherwise workable commitment into the branch that genuinely explains them, so the fix that gets applied has a reasonable chance of touching the real cause.