↩ ExploRational · A Catalogue of Divergent Rationality
explorational · a divergent move
The bed floods again. The function wants a fourth boolean. The class derails at the same slide, every term. Push-through reads friction as a toll to pay. There is a second reading, in which the situation is answering a question you did not know you had asked.
Donald Schön watched skilled practitioners — architects, therapists, engineers — and located their skill in a loop he called a reflective conversation with the situation. The practitioner makes a move; the material answers; the answer carries news. A sketch refuses the site's slope. A clay wall slumps at the shoulder. Schön's word for the reply is back talk: the situation "talks back," and the good practitioner treats the resistance as information about the frame the move came from — how the problem was set, which is the one thing no amount of effort inside the frame can check. Friction, on this reading, is the world reviewing your problem statement.
The reading is easy to miss because effort is always available. Schön set it against what he called technical rationality — the stance that takes the frame as given and spends all its skill inside it: optimizing, patching, persevering. Problem setting, choosing what to treat as the things of the situation, happens before solving starts and is invisible while solving lasts; back talk is the only feedback addressed to that layer. Success inside a frame barely tests the frame. Resistance tests it directly — which is why the practitioner who reads friction learns something the diligent pusher-through is never told.
Software is where many of us meet the loop daily, because a codebase answers everything you do to it. The instrument below is a phrasebook for that conversation: seven concrete frictions, each with its two readings side by side. Pick the ones you have lived through first.
the signature instrument
Click a friction. The left panel gives the push-through reading — try harder, add a special case, tighten discipline. The right panel gives the back-talk reading: what the resistance says about the frame, and the move it invites. No numbers here; these are worked examples of a judgment call, contestable the way phrasebook entries are.
Seven frictions, two readings each
four from software · one garden · one classroom · one workshop
——
—
—
the move it invites—
code smells as utterances
"The computer is a machine, but a codebase is an organism," Kevin Simler writes, and organisms answer back. A code smell breaks nothing at execution time; the resistance it offers is developmental — the change that should have been small and was not. Read that resistance as speech and the standard complaints acquire content. Matt Belcher's first sign of rot is software that "tends to break in many places whenever a change is made, often even in areas that are conceptually unrelated to the change being made" — coupling, announcing that your module boundaries and the change's boundaries disagree. His account of how rot arrives compresses the push-through reading into one sentence: "Complexity creeps in as 'easy' code changes are made instead of the more difficult design changes required to support a change." Every easy change ducked a design change the situation had asked for.
Hillel Wayne's edge case poisoning is the same conversation at the level of ontology. His recipe data model began as a list of ingredients with masses; the cookbook answered, page by page — inedible foil cups, optional cream of tartar, fondant that contains fondant — until a newcomer would "struggle much more to see the core idea in the forest of edge case handling." Patches accumulating around one concept are the domain rejecting the categories you offered it. And Will Larson supplies the endgame for practitioners who never listen: build a rich abstract model of a big ball of mud — Foote and Yoder's name for the pattern — and "you'll refine into rich sophistication, and still be wrong." His remedy, "Document what it does, not what it's intended to do," is listening adopted as method.
what to try
The third-patch rule. The first patch is a fix; the second, a coincidence. At the third patch around the same concept, stop and write down what the concept would have to become for the patches to stop arriving. You may keep patching afterward — but now it is a decision with a stated price, and the domain's counter-proposal is on record.
Transcribe the resistance in the situation's voice. Turn the friction into a first-person sentence spoken by the situation: "I flood because your bed sits where the water gathers." "I break over there because those two modules were never two." A friction that refuses first-person restatement is probably noise; one that snaps into a sentence has located an edge of your frame.
Reconstruct the question you asked. Each design move puts a question to the material, and the friction is an answer arriving. Recover the question your frame was implicitly asking — "this schedule assumes reviews take a day" — then check whether the resistance is a no to that question or to a different one. Resistance sorted by addressee is information; unsorted, it is weather.
the payoff
The move pays in timing. A postmortem hears the frame fail after the death; a review hears it secondhand and late. Back-talk arrives during the work, addressed to you, at the point of contact between frame and world — the cheapest frame-level evidence you will ever be offered. The practitioner who reads it gets to reframe while reframing is still an option. The one who pushes through receives the same sentence later, from the postmortem, at postmortem prices.
The coordinates matter, too. This move convenes nothing: it runs alone, mid-action, wherever hand meets material, with no premise to install and no room to design. And hearing is half of it — the reframe puts a changed question back to the situation, which answers with fresh back talk in turn. That is Schön's spiral: the situation comes to be understood through the attempts to change it, and changed through the attempts to understand it.
the instrument ↔ the move
| The instrument | The move |
|---|---|
| a friction card | an utterance: the situation replying to your previous move, in the only language it has. |
| the push-through reading | the default frame absorbing resistance as cost — effort, padding, patches, discipline. |
| the back-talk reading | reflection-in-action: the same resistance, read as evidence about how the problem was set. |
| the move it invites | the reframe — a changed question put back to the situation, which will answer with fresh back-talk in turn. |
| clicking all seven | the claim that the translation generalizes: the entries differ by craft; the grammar is one. |
how this opening fails
risk · token opposition
The catalogue's named risk for this move. You pause, transcribe the back-talk, nod at what it says about your frame — then push through unchanged, with the resistance now filed as "known." A back-talk reading that never alters the next action is the push-through reading with better manners. The test is behavioral: name the last time the material changed your frame, and say what the frame changed to.
risk · reading sentences into weather
A flaky test, a dull blade, one hard afternoon — plenty of friction says nothing about the frame, and treating every squeak as an ontological verdict makes work impossible. Schön's practitioners weigh the back talk against everything else they know about the situation. The utterances worth stopping for are patterned: the same failure, at the same spot, arriving by independent routes. Once is accident; the third arrival at the same spot is a sentence.
The material is answering a question you did not know you had asked. Listen before you push.
can you use it?
RECOGNITION — Which is listening for the back-talk? A: adding the fourth special case, carefully, with a test. B: pausing at the fourth special case to ask what the accumulation says about how the concept was framed. C: asking a colleague to review the patch.
B. A is push-through with good hygiene; C outsources the reading to someone farther from the contact point. The move treats the recurring resistance itself as evidence about the frame, while there is still time to change it.
THE NEAREST NEIGHBOR — Probing before committing is also Schön's conversation with the situation. What separates the two moves?
Direction. Probing speaks first: a small deliberate act sent out so the situation reveals what kind it is. Back-talk is the listening half: the reply arrives during work done for other reasons, answering a question you never knew you sent. One move poses the question; the other hears an answer to an unposed one.
PRODUCTION — Take a friction you are currently pushing through. Write its back-talk reading in one sentence: what does the resistance say about the frame?
A version: "The onboarding doc keeps growing because the product now has two products in it." Yours works if the situation is the speaker, the sentence is about the frame — boundaries, categories, assumptions — and it implies a reframe you could try. If it paraphrases as "try harder," it is still the push-through reading.