A Two-Axis Way to Pick the Right Accountability Setup for Your Actual Failure Pattern

Debugging a failing system starts with reproducing the failure, not reading documentation about failures in general. Most advice about “why you don’t follow through on your goals” skips that step. It treats non-follow-through as a single bug with a single fix — more willpower, a better app, a stricter partner — when in practice it’s closer to four distinct failure modes that happen to produce the same visible symptom: the thing didn’t get done.

This is an attempt at a more specific diagnostic, built on two axes that, in my experience mapping other people’s stated problems against what they actually described, do most of the sorting work.

Axis one: knowledge gap or follow-through gap

The first axis asks whether you’re missing information about what to do, or you already know exactly what to do and don’t do it anyway.

A knowledge gap looks like: “I’m not sure what time I should actually be going to bed to hit an early wake time,” or “I don’t know if I should eat before or after a morning workout.” These are answerable questions. The right response is research, a plan, maybe a professional’s input — not accountability infrastructure, which does nothing for a person who genuinely doesn’t know the target they’re supposed to hit.

A follow-through gap looks different: “I know I should be asleep by 10:30. I know it every single night. I am, most nights, still awake at 11:45 for reasons I can’t fully explain to myself.” No missing information. The plan is correct and unexecuted. This is the category accountability systems are actually built for, and it’s also the category most people misdiagnose as a knowledge problem — reading one more article, buying one more book, when the actual bottleneck was never information at all.

Most people asking “how do I become a morning person” have already, at some point, encountered every piece of relevant information on the subject — the same overexposure decision fatigue research describes when a person has the facts and still can’t act on them. The bottleneck usually isn’t axis one. It’s worth checking anyway, because the fix for a real knowledge gap (a plan) is close to useless against a follow-through gap, and vice versa — running the wrong fix against the wrong failure mode is how “I tried everything and nothing worked” narratives get built, when what actually happened is one tool got tested against the wrong bug.

Axis two: night-before or in-the-moment

The second axis asks when the failure actually originates, not when it becomes visible. A failure that surfaces at 6:15am when the alarm goes off might have been decided at 6:15am, or it might have been decided at 11:40pm the night before and simply hadn’t rendered yet.

Night-before failures are decisions made hours before the visible symptom: staying up late, having a drink that disrupts sleep architecture, leaving the phone on the nightstand instead of across the room, not setting out clothes. By the time the alarm fires, the outcome is close to locked in — the person hitting snooze at 6:15 made the decisive choice at 11:40, and no amount of 6:15am intervention reaches back in time to fix it.

In-the-moment failures are decisions made at the point of execution itself, independent of preparation: the alarm goes off, the plan was sound, sleep the night before was adequate, and the failure is still a snooze button pressed in a half-conscious reflex that a well-prepared night doesn’t prevent.

These need different interventions even when they look identical from outside. A night-before failure needs something that acts on the evening — a commitment that costs something to break before the failure window even opens, like a check-in with someone the night before rather than only at the moment of waking. An in-the-moment failure needs something positioned at the point of execution itself — an alarm that can’t be silenced by reflex, a consequence that fires at 6:15, not 11:40.

The four combinations

	Knowledge gap	Follow-through gap
Night-before origin	Research what a realistic wind-down actually requires — most people underestimate how early the “decisive hour” is	An evening commitment with a cost attached — someone checking that the phone left the room, not someone checking that you woke up
In-the-moment origin	Learn what the first 10 minutes after waking should look like (light, movement, no snooze)	Something positioned at the alarm itself — social, financial, or physical — that doesn’t rely on already being alert enough to choose correctly

The bottom-right cell — in-the-moment, follow-through gap — is the one most commercial accountability products are actually built for, which explains both what they’re good at and what they can’t touch. A tool built for the bottom-right cell will do very little for someone whose real problem lives in the top-left, no matter how well-built it is, because it’s solving a bug that isn’t the one running.

Why this matters more than it sounds like it should

The practical value of sorting a problem into one of these four cells isn’t philosophical. It changes what “trying harder” should even mean. Someone in the top-left cell (a genuine knowledge gap about evening wind-down) doesn’t need a stricter accountability system — they need fifteen minutes with a sleep-hygiene guide, and no amount of social pressure at 6:15am substitutes for information they don’t have. Someone in the bottom-right cell can read every article that exists and still fail the exact same way tomorrow, because the problem was never informational.

This is also where a lot of self-improvement advice quietly fails people without either side realizing why: it’s frequently written by people solving a top-left or top-right problem (they didn’t know what to do, then learned it) and read by people with a bottom-right problem (they already knew, and needed a different kind of intervention entirely). The advice isn’t wrong. It’s aimed at a different cell than the reader is actually in.

Working an example through all four cells

It helps to run one concrete situation through the full grid rather than treat the cells abstractly. Take “I can’t get to the gym before work three days a week like I planned.”

Top-left (knowledge gap, night-before origin) would look like: the person genuinely doesn’t know how early they’d need to leave the house to make a 6am class, hasn’t accounted for a 20-minute drive plus parking, and is setting an alarm that was never going to work in the first place. The fix is arithmetic, not discipline — sit down with a calendar and a map and find the real number.

Top-right (knowledge gap, in-the-moment origin) looks different: the person knows the schedule is realistic, but doesn’t know what to do in the first five minutes after the alarm to avoid the drift back toward sleep — no plan for what happens between “alarm off” and “car keys in hand.” The fix is a specific first-five-minutes script, not more motivation.

Bottom-left (follow-through gap, night-before origin): the person knows exactly what time they need to leave and exactly how to structure the first five minutes, and still stays up too late watching something, every single night, in a way that makes the 6am plan impossible before it starts. The fix has to intervene on the evening — an earlier commitment, a person expecting a check-in before bed, something that makes 11:30pm cost more than it currently does.

Bottom-right (follow-through gap, in-the-moment origin): the alarm goes off on schedule, after an adequate night, and the person still turns it off and goes back to sleep out of pure reflex, with a plan that was otherwise sound. This is the cell where video-proof, socially-witnessed wake-up systems earn their keep, because the intervention has to exist at the exact second the failure happens, not before it and not after. It’s also the one cell where the fuel behind the fix doesn’t have to be a well-reasoned plan at all — irritation gets people out the door just as reliably as a witness does, for a session or two, even though the two fixes fail for completely different reasons over time.

Same stated problem — “I can’t get to the gym” — four different actual bugs, four different fixes. A person who’s actually in the bottom-left cell and buys a product built for the bottom-right cell (an alarm-moment intervention) will report, accurately, that it didn’t help, because the failure was never happening at the alarm. It was happening three hours earlier and simply showing up as a missed alarm the next morning, the way a bad decision made the night before finishes deciding the outcome before the alarm gets a vote.

A quick way to self-diagnose

Two questions, answered plainly about the last two weeks rather than about how things are supposed to work in theory, do most of the sorting:

“If I explained my plan out loud to someone else, would they immediately spot a hole in it?” If yes — if the plan itself doesn’t survive being said out loud — that’s a knowledge-gap signal, not a follow-through one. Fix the plan before adding any enforcement mechanism on top of a plan that was never going to work.

“When it goes wrong, can I point to a specific decision made the night before, or does it go wrong even on nights I did everything right?” If there’s always a specific night-before culprit — the late show, the drink, the phone on the nightstand — the origin is night-before, and the fix belongs in the evening. If it sometimes goes wrong even after a clean night, the origin is in-the-moment, and the fix has to sit at the point of waking itself.

Most people can answer both from memory without needing to track anything first. The two-week self-observation suggested earlier is for the harder cases — the ones where the real answer to either question is “it depends,” which usually means more than one cell is active at once and they’re compounding rather than one clearly dominating.

Where the framework is weakest

Real failure patterns don’t always sit cleanly in one cell — a person can have a night-before knowledge gap about wind-down timing and an in-the-moment follow-through gap about snoozing, layered on top of each other, and untangling which one is driving a given bad week takes more self-observation than a two-axis chart can do for you. This framework is a sorting tool for a first pass, not a diagnosis that replaces paying attention to your own actual mornings for a couple of weeks before concluding anything. Treat the four cells as a starting hypothesis to test against what you observe, not a conclusion to accept on the framework’s authority alone.

Two axes is also a simplification chosen for usefulness, not because the underlying problem only has two dimensions. A third axis — how much the failure costs when it happens, a missed flight versus a missed gym session — would sharpen the picture further, at the price of a chart nobody can hold in their head while standing in their kitchen at 6am trying to figure out what went wrong. Two axes is the version simple enough to actually use.