Micro-commitments are the floor, not the ceiling — exceed on good days, hit the minimum on bad days without guilt

Why This Is a Rule

Two opposite framings of a micro-commitment produce opposite behavioral patterns. Ceiling framing ("my commitment is 200 words"): on good days, you write 200 words and stop because the commitment is met. On bad days, you write 200 words with effort. The ceiling caps good-day output while producing the same bad-day output. Floor framing ("my minimum is 200 words"): on good days, you write 200, then 500, then 1,000 because the floor was met early and momentum carries you. On bad days, you write exactly 200 and stop — the floor is met, the chain is unbroken, no guilt.

Floor framing produces strictly better outcomes: same bad-day performance (minimum met) with uncapped good-day performance (momentum beyond minimum). It also eliminates the guilt spiral that kills commitments: hitting exactly the minimum on a bad day IS success, not partial failure. "I only wrote 200 words today" with floor framing means "I met my commitment." With ceiling framing, the same 200 words feels like "barely scraping by."

The "without guilt" qualifier addresses the psychological mechanism that kills micro-commitment systems: judging minimum-hitting days negatively, which produces the demoralization that leads to skipping, which produces the shame spiral that kills the commitment entirely. The minimum was designed for bad days (Micro-commitments must pass three tests: under 15 minutes, executable on your worst day, and binary-clear completion in 10 seconds). Hitting it on a bad day is the system working as designed.

When This Fires

• When operationalizing any micro-commitment designed via Micro-commitments must pass three tests: under 15 minutes, executable on your worst day, and binary-clear completion in 10 seconds
• When hitting the minimum feels like failure rather than success — reframe from ceiling to floor
• When guilt about "only" meeting the minimum threatens consistency
• Complements Design three operating modes for every important process: full, reduced, and minimal — degrade fidelity but never lose continuity (three operating modes) with the micro-commitment-specific framing

Common Failure Mode

Ceiling framing producing guilt-driven abandonment: "I 'only' wrote 200 words three days in a row — I'm not making real progress." Three consecutive minimum-floor days IS real progress: 600 words you wouldn't have written without the commitment. The alternative (no micro-commitment) produces 0 words, not more words. Judge against zero, not against aspirational output.

The Protocol

(1) After designing a micro-commitment (Micro-commitments must pass three tests: under 15 minutes, executable on your worst day, and binary-clear completion in 10 seconds), explicitly frame it as a floor: "The minimum is [amount]. Below this, I don't drop. Above this, I welcome." (2) On high-capacity days: exceed the minimum freely. Let momentum carry you past the floor. Don't cap yourself at the minimum. (3) On low-capacity days: hit exactly the minimum and stop. Celebrate the minimum as a success — the chain is unbroken, the system is working. No additional output is required or expected. (4) Never judge a minimum-meeting day negatively. The minimum was specifically designed (Micro-commitments must pass three tests: under 15 minutes, executable on your worst day, and binary-clear completion in 10 seconds) for your worst days. Hitting it on a bad day means the design is correct. (5) Track floor-meeting consistency, not average output. A month of daily minimums (30 days × minimum) outperforms a month of three heroic days and 27 zero days.