How a Failure Repeats Tells You What's Broken
Tennessee's Medicaid system mailed DiJuana Davis's notices to the wrong address and cut her family's coverage. Her appeal fixed her record; the rule kept running.
Recent essays
Institutions Act Fast and Take Back Slowly
One trial result reaches a regulator, a guideline panel, Medicare and the insurers, and each acts on its own clock. Someone pays for every day in between.
Read an Institution by Its Workarounds
The statute and the org chart describe what an institution intends to be. Its workarounds, grievance files and exception codes show what it is.
Name what went wrong
Describe what happened in your own words. The questions help you pin down the failure, the drafting tools write the message, and the note keeps a record of what failed.
Diagnose the situation
Optional: narrow it down
- Your questions will appear here.
Draft your next message
About the wait
Putting this in writing so the request is on record: I would like to know what the current review step is, and who holds it right now. A written answer is fine; I am not asking for a call.
Whose work it is
Putting this in writing so the request is on record: I would like to know which of these steps is my responsibility and which is yours. A written answer is fine; I am not asking for a call.
What evidence is enough
Putting this in writing so the request is on record: I would like to know the specific evidence that would be sufficient, in writing. A written answer is fine; I am not asking for a call.
Document the failure
- The date, the channel, and the name of the person who told you.
- What you were told would happen next, in their words.
- What actually happened, and when you noticed the difference.
- The step you were asked to repeat, and how many times.
- What it cost you to comply: hours, money, missed care, missed work.
- Who you escalated to, and what the escalation returned.
- The sentence you would need to quote if this went to review.
Capture a field note
Nothing saved yet. Notes stay in this browser and are never sent anywhere.
Run an instrument
Fourteen checks, each built from a claim in the essays. Each runs on this page: the link holds what you typed, and nothing is stored or sent anywhere.
- Find the leap in an institution's justificationPaste a sentence an institution used on you or a memo uses on its readers. The linter accepts the fact and marks the step it does not license.
- Is this option real? Five tests for a choice that exists on paperTest an option, an opt-out or an accommodation: can a person use it and stay safe, paid, intact, coherent and included?
- Find who decided: trace a default, delay or algorithm to a signatureWrite your objection, then trace the decision back hop by hop until someone could have signed it.
- It's legal, accurate, optional: what each defense leaves openPick the defense you were given. The instrument grants it, then names the question it leaves unanswered and what would answer it.
- Can a complaint change anything? A check for feedback channelsThree questions for any feedback form, ombuds office or survey: can the problem be stated, is it recorded, and does receipt change what happens next?
- After an appeal is won, does anything change? Nine checksName an error and check the nine stages that decide whether a validated finding changes the system or only the case.
- How long is the record about you wrong? Review cadence and who paysSet a review interval and count the days a record stays wrong between the event and the next look.
- Has a permission outgrown what it was granted for? A scope-creep checkHold a grant of authority, a consent or a data permission against how the power is now used: wider, longer or inferring more.
- A design-doc section for what your rule leaves outFive lines any rule, product spec or policy should declare: what it drops, how much, who reconciles it, who pays, and when the rule itself fails.
- Postmortem check: did the fix reach the level that failed?Mark which level failed (record, decision, rule, burden, question, jurisdiction) and what the correction reached. The gap is the cause you kept.
- How much of a shock reaches the person? Absorbed versus passed onStack institutions on one person and compare the account each gives with the load that actually arrives.
- Same budget, different burden: who does the work and who can correct itCompare two institutions with the same resources by who reconciles the rule with people's lives, and who may correct it.
- When a rule doesn't fit, who flexes? Rank and the remainderRun a clinic template against how visits actually went and choose who absorbs the minutes the rule cannot hold.
- Read an institution through its workarounds and complaintsName the abstraction, where it breaks, who absorbs the break and whether the institution changed. The read returns how deep the correction went.
Or run the checklist for a named mechanism: False Elasticity, Actuarial Medicine, Sanctiphagy, Procedural Erosion, Administrative Homelessness, Manufacturing Inevitability, Seemingly Neutral Systems, Temporal Capture, Hyperreal Labor, Charismatic Systems, The Heisenberg Subaltern, Load-Bearing Design, The Capture of Maintenance, Lucid Disorientation, The Subtext Economy Has Collapsed.
Continue reading
Related context
Version history
No prior versions in this archive snapshot.
Each version says how much changed from the one before it: wording (under 5% of the words), a revision, or a rewrite (more than a third). The measure counts words that moved; whether a claim changed takes reading.
New essays by email
One letter a week: that week’s new essays, and one tool to use.
Your address isn’t shared. Every email has a one-click unsubscribe.
New essays by email
One letter a week: that week’s new essays, and one tool to use.
Your address isn’t shared. Every email has a one-click unsubscribe.