Check-in with evidence ('did/didn''t on these days'), not narratives ('tried hard but...') — evidence prevents rationalization at the reporting layer

Why This Is a Rule

Narrative check-ins invite rationalization. "I tried really hard this week but work was crazy and I couldn't find the time" tells a story where you're the hero of an impossible situation — struggling valiantly against forces beyond your control. The narrative format makes non-compliance feel reasonable. The accountability partner, hearing a compelling story, sympathizes rather than enforces.

Evidence-based check-ins eliminate the rationalization surface. "Monday: did it. Tuesday: didn't. Wednesday: did it. Thursday: didn't. Friday: didn't. 2 out of 5." There's no story to sympathize with — just data. The data either meets the commitment threshold or doesn't. The accountability conversation shifts from "tell me why" (narrative, rationalizable) to "what needs to change to improve the ratio" (structural, actionable).

This is Accountability reporting must be near-zero effort — a checkbox or emoji, not a paragraph — because reporting friction kills the whole system (near-zero effort reporting) meets Ask 'Did you write for 30 minutes?' not 'Did you finish the chapter?' — process accountability triggers action, outcome accountability triggers anxiety (process accountability): the evidence format is both easier to produce (a list is faster than a narrative) and harder to rationalize through (a number can't be story-ed away).

When This Fires

• When designing check-in formats for any accountability relationship
• When check-ins have devolved into supportive conversations that don't drive behavioral change
• When the accountability partner consistently accepts rationalizations — the format is enabling it
• Complements Ask 'Did you write for 30 minutes?' not 'Did you finish the chapter?' — process accountability triggers action, outcome accountability triggers anxiety (process questions) and Accountability reporting must be near-zero effort — a checkbox or emoji, not a paragraph — because reporting friction kills the whole system (minimal effort reporting) with the evidence format

Common Failure Mode

Narrative check-ins: "This week was brutal — had three client emergencies, barely slept Monday night, and the kids were sick. I managed to exercise twice though, so I'm proud of that." The accountability partner says "Great job managing so much!" and the 2-out-of-5 performance gets framed as heroic rather than below-target. Evidence format: "2 of 5 sessions completed. Below 80% target." Now the conversation is about structural fixes, not about celebrating struggle.

The Protocol

(1) Define the check-in format as evidence-based: Binary compliance list: for each scheduled instance, report did/didn't. Summary metric: total compliance divided by target. (2) Report first, discuss second. The evidence comes before any explanation. (3) If compliance is below target → the conversation is about structural diagnosis (After commitment failure, diagnose within 48 hours: identify trigger, locate decision point, match structural support — not more willpower), not about why this week was hard. Every week is hard; the commitment was designed knowing that. (4) If compliance is at or above target → brief acknowledgment, then move on. Don't over-discuss success; reinforce the norm that meeting commitments is expected, not exceptional. (5) The accountability partner's role: compare evidence to target, ask structural questions about misses, and refuse to accept narrative rationalizations as substitutes for structural fixes.