A federal childcare benefit
The timing rule nobody wrote down
What was going on.A federal benefit helps military families pay for child care. It’s the thing that decides whether a parent keeps a job through a move or a deployment. Most applications came back for more documents. The organization running it had brought in an engineering firm to rebuild the system. I came in through that firm to write down how the service actually ran. The organization later contracted me directly.
What I found.Everyone assumed families were careless. Then look at one. A family applies in April for care that starts in September. The pay statement they send is valid the day they send it. By the time anyone opens it, it’s expired. They’re asked for a new one. That’s not a careless family. That’s a timing rule nobody wrote down, sitting between the contract, the coordinators and the software. Once you’ve seen one of those, you see them everywhere. Signatures assumed to need ink where the rules allowed electronic. A generic upload form while the coordinators worked from a detailed checklist that no family had ever seen.
What I did.One operations lead at a time. Each session refined what the last one validated. Working prototypes, not presentations. The moment that changed the room: the coordinators saw their own checklist turned into a document list for each family. They stopped reviewing my designs. They were looking at their own expertise, made visible. I also talked to families directly. One spouse described sending documents into “the abyss” with no confirmation. That line shaped the status design.
What came out of it.A complete first submission became the norm in pilot, measured in production, not claimed. Every design decision traces to a person, a quote and a result, in a record the team still uses. Then, in 2026, the same discipline for the team’s AI: each agent gets a short list of what it’s allowed to read, a capped set of tools and standing rules. Acceptance criteria become plain-English test cases, then automated tests, scored per criterion. And there’s a written line on what the model isn’t trusted to decide. That stays with a person.
What I took from it.The gap between the rules, the staff and the software is where the problems live, and nobody can see it because each layer has a different owner who assumes the other two agree. Reading the three against each other is the whole method. The AI part is the same method applied to the machine: say what it may read, test what it produces, keep a person on the hook.