The Trojan Horse — Summary

The moment Sandra Purcell understood what her organization actually does, she was on the phone with a substitute volunteer who had just completed a Tuesday delivery to Mrs. Chen’s apartment. Successful delivery: correct meal, correct temperature, accepted at the door. Then Delores called from home. “Did anyone check on her? She sets out two cups on Tuesdays.”

Sandra called Mrs. Chen. She had been crying. Not about anything specific. About the accumulation of days.

The delivery manifest lists addresses, meal types, dietary restrictions, delivery windows. It does not list: “Sets out two cups on Tuesdays.” “Puts the orchid on the table when she’s having a good day.” “Answers the door slowly when her hands are bad.” Delores knew all of this. The manifest knew none of it. In four years, Delores flagged three concerns: a medication change Mrs. Chen had not understood, an unreported fall, and a behavioral shift caused by a new blood pressure medication that was making her foggy and flat. Each flag came from knowledge no intake form would generate and no remote monitoring system would detect.

The meal was a Trojan horse. What it carried was presence.

There is a category of service where the nominal function was never the real function. School transportation: Ray, twenty-three years on the same bus route, has called in three welfare checks, all warranted, because he had driven the same children long enough to know what their ordinary looked like. Library home delivery: the book was the reason for the visit, the visit was the reason for the program. Postal routes in rural communities: the letter carrier was, in some geographies, the only person who came to the door on a regular schedule. Community health worker visits: the clinical literature consistently finds that the most important variable is not the health information delivered but the relationship.

In every case, the metrics track the horse, not what was inside it. This is not an oversight. The relational function was invisible to the system before automation, because the system was designed around the nominal function. Nobody designed Meals on Wheels to provide social contact. The social contact happened because a human being was delivering the meal, and human beings who see the same person twice a week for four years start to know things. The knowing was a byproduct of logistics, and byproducts do not appear in cost-benefit analyses because they were never on the benefit side of the ledger.

If the relational function was the real function, should the system have been designed around it rather than the nominal one? The question sounds naive. Governments fund what can be counted, and presence cannot be counted. The Trojan horse architecture was the only design that could have survived the funding environment. When the logistics operation no longer requires human hands, the smuggling route closes. What was smuggled does not find an alternative route.

The pilot program’s six-month report shows improved delivery reliability, reduced cost, expanded coverage to 340 recipients previously on the waiting list. The system is working better by every measure the system tracks. Mrs. Chen has stopped setting out two cups.