What Airlines Know About Penalties That Most Habit Apps Don't

A penalty changes behavior only when two separate conditions are both met: the person has to be able to picture the specific cost before they break the commitment, and they have to have no realistic way to dodge, postpone, or quietly cancel it once the miss occurs. Most commitment devices fail at one of those two jobs, not because the penalty is too small, but because it’s vague on one axis or escapable on the other — and the clearest illustration of a penalty that hits both isn’t a habit app at all. It’s a federal regulation governing oversold airplane seats.

The industry that already solved this

U.S. airlines have been permitted to sell more tickets than they have seats since the practice was formalized decades ago, on the well-documented actuarial bet that a predictable share of ticketed passengers won’t show up. When that bet is wrong and a flight is oversold beyond the no-shows, someone gets bumped — and since 1978’s airline deregulation handed carriers much more freedom over pricing and capacity, the U.S. Department of Transportation has required a specific, tiered payout to whoever’s involuntarily denied a seat. Under 14 CFR Part 250, a passenger bumped for a delay of one to two hours domestically is owed 200% of their one-way fare, capped at a dollar figure DOT revises periodically for inflation (roughly $775 as of the current schedule); a delay over two hours doubles that to 400%, capped around $1,550. International flights follow a similar structure with longer delay windows. Airlines can’t decide case-by-case whether to pay it, and passengers don’t have to guess whether a penalty framework even exists — it’s published, it’s tiered by outcome, and it fires close to automatically.

Robert Crandall, American Airlines’ CEO through the 1980s, is widely credited with pushing the carrier to formalize yield management — using the airline’s own reservation data to model exactly how much to overbook each route without triggering more bumps than the payout math justified. That’s the part worth sitting with: American wasn’t trying to eliminate the penalty, it was trying to price its own risk of triggering one. A regime like that only makes sense as an optimization target if the penalty on the other side of it is fixed enough to model. You can’t run a spreadsheet against a consequence nobody can predict.

Two axes, not one

Most writing about penalties treats “how severe” as the only variable worth adjusting — bigger fine, harsher consequence, higher stakes. That’s a single dial standing in for two genuinely separate questions, and conflating them is why so much advice about penalties contradicts itself in practice. Call the framework the Consequence Grid, and give it two axes instead of one.

Advance visibility — can the person accurately picture the specific cost before they break the commitment, or is the penalty vague, abstract, or only discovered after the fact? A posted, itemized cost is high visibility. “Something bad probably happens” is low visibility, no matter how bad that something eventually turns out to be.

Enforcement certainty — once the miss happens, does the consequence land reliably, or is there a realistic escape hatch — renegotiation, forgetting, deleting the app, quietly not paying yourself? A payout that’s automatic and third-party-enforced is high certainty. A penalty that depends on the same person who broke the promise to also administer their own punishment is low certainty almost by construction, because the two jobs pull in opposite directions.

Cross those two axes and four quadrants fall out, and nearly every commitment device or penalty scheme you’ve ever encountered sits cleanly in one of them.

	High certainty (enforced regardless)	Low certainty (escapable, self-administered, or unevenly applied)
High visibility (cost is known in advance)	Posted Price — DOT denied-boarding compensation; a named friend seeing a specific failure	Idle Threat — a disclosed late fee that’s rarely actually charged; a workplace rule everyone knows is never enforced
Low visibility (cost is vague or discovered after the fact)	Ambush Fee — overdraft charges, surprise cancellation penalties buried in terms of service	Vapor Penalty — a lost streak icon, a vague sense that missing today “doesn’t really count,” a self-imposed rule with no outside party involved

Posted Price: known, and impossible to dodge

Denied-boarding compensation is the cleanest real-world example of the upper-left quadrant, because both variables are maximized on purpose. The airline can’t retroactively decide the delay was shorter than it was, and the passenger doesn’t need to have read the federal register to have a rough sense that getting bumped comes with a real, tiered payout (Maine’s lobster harbors also scale penalties in steps, by custom, from a rope on a buoy to a cut line) — enough airline travelers have either experienced it or heard about it that the expectation is broadly baked in, even without exact numbers memorized. That combination is what makes it function as a working part of the system rather than a piece of theater: American’s own optimization of how much to overbook only makes sense as a response to a cost that’s both anticipated and unavoidable on the airline’s side of the ledger. A reward can go wrong from the other direction: Hanoi’s rat-tail bounty paid for the receipt instead of the outcome, and the receipts multiplied while the rats did not decline.

Here’s the fully self-contained version of the claim, worth stating plainly on its own: a penalty sits in the Posted Price quadrant, and tends to actually change behavior, when the person facing it can name roughly what it costs before they act and cannot talk their way out of paying it afterward — denied-boarding compensation qualifies on both counts because it’s published under federal rule and disbursed without requiring the airline’s discretion, and that same combination, not the size of the number, is what separates a penalty that holds up from one that quietly stops working.

Named-friend social accountability lands in the same quadrant for a related but distinct reason. If you’ve told three specific people — not an abstract audience, three people whose names you can say out loud — that they’ll see it if you don’t follow through, you know in advance roughly what that costs socially, and there’s no administrative step where you get to decide, after the fact, that it doesn’t count this time. Nobody has to charge a card or file a claim. The consequence is just what happens next, and it happens whether or not you feel like it should. That’s a different flavor of certainty than a federal compensation schedule, but it clears the same two-axis bar, and a longer comparison of what different accountability structures actually cost people over repeated use goes deeper into why relational consequences resist the discounting that financial ones don’t.

Idle Threat: disclosed, but toothless

Move down to the lower-certainty half of the visible row and the picture changes without the cost itself getting any smaller on paper. A late fee that’s clearly printed in the contract but that the business waives every time someone calls and asks is a known cost with no real teeth. Chicago Public Library’s 2019 decision to eliminate late fines is instructive here in reverse: the fee had been publicized and understood for years, but librarians increasingly reported that it wasn’t changing return behavior — it was mostly falling on people who already couldn’t easily pay it, while habitual borrowers who could afford it simply treated it as a rounding error, or avoided the library altogether rather than reckon with an overdue balance. A cost that’s fully visible but only sporadically or inconsistently collected teaches people to discount the announcement, not to change the underlying behavior it was supposed to deter.

Most self-administered commitment penalties drift into this quadrant over time even when they didn’t start there. A person who sets themselves a rule — “if I skip my run I owe the jar five dollars” — knows the exact number from day one. But because they’re also the one who has to walk to the jar, the certainty half of the equation depends entirely on their own follow-through on the penalty, which is the same follow-through problem the penalty was meant to solve in the first place. It’s a small irony worth naming: a self-enforced consequence asks the very willpower that already failed once to now show up a second time and enforce its own punishment.

Ambush Fee: certain, but never pictured

The lower-left quadrant runs the opposite failure. An overdraft charge is about as certain as a bank fee gets — it fires automatically, with no discretion involved — but very few account holders are running a mental model of exactly when it’ll trigger at the moment they’re making the purchase that causes it. The consequence is real and reliable; it’s just disconnected from the decision that produced it, which blunts its power to actually change behavior in the moment that matters. Subscription cancellation penalties buried a few screens deep in a sign-up flow work the same way: certain once you hit them, invisible until you do.

This quadrant matters mostly as a warning to anyone building a penalty. A consequence that’s rock-solid on enforcement but poorly surfaced in advance can technically “work” — money changes hands, someone learns a lesson — but it teaches the lesson after the fact rather than shaping the choice beforehand, which is a much less useful thing for a penalty meant to prevent a specific action to be doing.

Vapor Penalty: the quadrant most habit tools default into

The bottom-right box is where a lot of well-intentioned commitment devices end up without anyone choosing it deliberately. A streak counter resetting to zero is a real consequence in the sense that it’s visible on screen, but it’s low-certainty in the way that counts, because the entire enforcement apparatus is an app you can close, mute, or delete the moment it stops being convenient. There’s no external party who notices if you never open it again. And it’s low-visibility in a subtler sense too: most people setting a streak goal aren’t picturing the actual moment of loss with any specificity — they’re picturing the habit succeeding, not the flame icon going gray, which means the cost isn’t really loaded into the decision at the moment temptation to skip actually shows up.

A mechanical walkthrough of how one popular commitment product tries to escape exactly this quadrant is worth reading alongside this framework, because an escalating financial pledge is a specific, deliberate attempt to drag a penalty up out of Vapor territory and toward Posted Price — making the number concrete, automating the charge so the person can’t simply skip paying themselves, and increasing the amount specifically so it can’t be quietly absorbed into a budget the way a flat fee eventually is. It’s one of a fairly small number of commitment devices that takes both axes seriously at once rather than optimizing severity alone.

What the grid actually predicts

Put the four quadrants side by side and the useful prediction has little to do with “bigger penalties work better.” A penalty’s quadrant, not its size, determines whether it keeps deterring anything after the first few times it’s paid. A $1,550 denied-boarding payment and a five-dollar jar fine are wildly different in magnitude, but the airline’s payment is the one that survives repeated use precisely because neither the traveler nor the airline gets to renegotiate it after the fact. The jar fine, despite being entirely under the person’s own control to set at any amount they like, degrades the moment its collection depends on the same discipline that already broke down once.

That reframes the actual design question for anyone building or choosing a commitment device. It isn’t “how do I make the consequence scarier.” It’s “can the person picture this cost before they act, and is there any point in the process where either party gets to quietly let it slide.” A penalty that answers yes to both is doing the same job denied-boarding compensation does for an oversold flight — not preventing every miss, but making the cost of a miss something concrete enough to actually weigh against the alternative, rather than an abstraction easy to wave off in the moment.

One example worth naming, since it sits squarely in the Posted Price quadrant for the same reason the airline case does: DontSnooze routes a missed alarm to friends the person chose ahead of time, so the cost is known in advance — specific people will see it — and there’s no self-administered step where the person gets to decide, after the fact, that this particular miss doesn’t count.

None of this argues that every commitment device needs to chase maximum severity, or that financial and social penalties are interchangeable tools for the same job — they aren’t, and which one fits depends on what kind of promise is actually at stake. What the airline case shows, more than anything, is that a penalty earns its keep by being both nameable and inescapable, and that a lot of thinking about penalties spends its energy on the wrong half of that pair, tuning severity on a consequence nobody can quite picture or nobody actually has to pay.