Table Before Prose

When long prose keeps repeating the same fields, pull the entities into rows and the attributes into columns, keeping narrative only for exceptions.

Choosing next summer's family trip, you've accumulated three long paragraphs of notes per destination: Portugal has this airfare and that weather, Costa Rica has this flight time and that lodging cost, and so on through five candidates. Reading them back, you realize each paragraph repeats the same fields in different words, and comparing anything requires rereading everything.

Table Before Prose is a 30-second restructuring for exactly this cue: long prose that keeps repeating the same fields. The procedure: pull the entities out as rows, five destinations, and the shared attributes out as columns: airfare, flight time, lodging cost per night, weather in July, kid-friendliness. Fill the grid from your notes. Then keep narrative only for the exceptions, the things that don't fit a cell: "Portugal requires the connecting flight Grandma hates." What took three rereads per comparison now takes one glance down a column, and patterns invisible in prose appear immediately, like the fact that the two cheapest options are also the two longest flights. It works when a repetitive document becomes a scannable grid plus a short list of genuine exceptions. The spec's warning: tables are poor for causal sequence and rich context. Don't tabulate a story or a mechanism; the move is for repeated fields, not for everything.