The Absent Field: Building the Field on Purpose

A stable field is often inherited from time spent together. It does not have to be. Explicit criteria, reduced live performance, processing time, and repair can make stability a property of design.

The obvious objection to everything I have argued so far in this series is that a stable field takes time. Usually, it does. People learn one another slowly. They discover what a pause means, what directness means, what kinds of language signal strain, what kinds signal concentration, which misunderstandings recur, which forms of repair actually hold. Shared reference accumulates through repetition until the interaction no longer has to begin from zero, and the field becomes more stable because the people inside it have history.

But duration is one way of producing stability. It is not the definition of stability.

That distinction matters because otherwise the argument collapses into something unusable: autistic gestalt processors can only show their capacities inside long-standing relationships, therefore any first encounter will necessarily mismeasure them. I do not think that follows. A field can be young and still be structured well enough to support generativity. It can lack history whilst offering predictability, explicitness, room to process, and enough repair that uncertainty does not immediately become consequence.

The question therefore changes from how do we make strangers feel familiar? to something much more practical: what does the field need in order to stop making unfamiliarity carry so much weight? Some of the answers are almost embarrassingly ordinary. Tell people what is being assessed. Give questions in advance where surprise is not itself the competency being measured. Allow processing time without treating latency as evidence. Permit clarification. Offer written or asynchronous response when rapid live speech is irrelevant to the work. Use work samples. Let people demonstrate competence through the thing they will actually be doing rather than through an adjacent performance whose relationship to the job has never been examined particularly closely.

None of this requires intimacy. It requires design.

That is the turn institutions routinely miss because accommodation is still framed as something added after the normal process has already been defined. The interview exists in its standard form. The autistic candidate arrives. Something about her makes the standard form difficult. An adjustment is therefore offered so that she can participate more successfully in the thing everyone else is presumed to access naturally. The structure remains innocent. The person carries the difference.

The methodological argument from the previous piece makes that framing harder to sustain. If hidden criteria, rapid social response, unfamiliarity, power asymmetry, and limited repair alter access to the capacities being measured, then reducing those conditions is not simply kindness toward someone who struggles with the standard test. It is an attempt to stop the test contaminating its own result.

That is assessment design.

Nothing about explicit criteria requires lowering substantive expectations. If a job requires complex reasoning, assess complex reasoning. If it requires technical competence, assess technical competence. If it requires collaboration, assess collaboration. If rapid decisions under genuine time pressure are part of the work, then time pressure may belong in the assessment too. But make the relation visible. Do not require rapid verbal improvisation merely because interviews have traditionally required rapid verbal improvisation. Do not treat eye contact as evidence of confidence when the job does not require eye contact. Do not treat conversational ease with a stranger as evidence of collegiality when the actual workplace will involve relationships accumulated over months or years. Do not convert performative enthusiasm into evidence of motivation simply because enthusiasm in a familiar social register is easier to recognise than motivation organised differently.

The question is not whether a demand feels normal. The question is whether it belongs to the construct.

Consider the ordinary behavioural interview question: Tell me about a time you had a conflict with a colleague and how you handled it. The candidate has to identify an appropriate event, decide what level of conflict counts, reconstruct enough history to make the event intelligible, select which details matter, infer what the interviewer is actually trying to assess, build a coherent answer, monitor how long the answer is taking, preserve an acceptable degree of eye contact, sound reflective without sounding rehearsed, demonstrate enough ownership without accepting blame that was not hers, and end with a lesson sufficiently polished to resemble the expected form.

Perhaps the employer wants to know how she handles conflict. The interview is measuring much more than that.

Give the question in advance and some of that noise falls away. Make the criterion explicit—we are assessing how you identify disagreement, communicate during it, and adjust afterwards—and more falls away. Allow a written response or work sample and more falls away again. The substantive demand remains. What changes is the amount of irrelevant field instability wrapped around it.

That is the design target. Not comfort, not an interview without difficulty, not a guarantee that the autistic candidate will perform well, but a cleaner relation between what the institution says it wants to know and what the assessment actually requires in order to reveal it.

This is also where repair becomes more important than it first appears. Most assessment formats treat first interpretation as final interpretation. A candidate misunderstands a question and answers the wrong thing. An interviewer interprets the answer as evidence of poor judgement. The encounter moves on, and the error remains embedded in the evaluation. A more stable field allows some degree of correction: that was not quite what I was asking; let me phrase it differently, or I think I answered a different question; can I try that again?

Those sentences are ordinary enough in real working relationships. People clarify. People revise. People discover that a first formulation did not carry what they meant. A workplace in which no one could ever repair a misunderstanding would be unbearable. Yet we often design interviews as though the capacity to avoid all misunderstanding during a first encounter is itself evidence of workplace competence.

If repair is part of competent adult communication, then an assessment that forbids repair may be removing evidence rather than preserving rigour.

The same applies to processing time. Latency is often treated as a problem because the social rhythm of an interview makes silence visible. The interviewer asks. The candidate pauses. The pause begins acquiring meaning before the answer arrives. But silence is not empty. For a gestalt processor, it may be precisely where the answer is being built. If the assessment is intended to measure the quality of that answer, there is no obvious methodological virtue in contaminating it with a second, unrelated question about whether the answer can be produced within a socially comfortable interval.

Sometimes speed matters. Often it does not. Design means knowing the difference.

This is where the argument about masking returns too. In The Manufactured Field, I described high masking as the private labour of carrying into the encounter some of the stability the encounter refuses to provide. The candidate prepares scripts, rehearses stories, calibrates expression, anticipates questions, monitors herself, and tries to construct enough predictability internally that the interaction remains traversable. Building the field on purpose changes who carries that burden. Instead of requiring the candidate to guess the criteria, disclose them. Instead of requiring her to predict every question, provide some in advance. Instead of requiring her to conceal processing latency, permit it. Instead of requiring her to manufacture a socially familiar version of confidence, specify what evidence of competence actually matters. Instead of making repair risky, design repair into the process.

The autistic person no longer has to privately subsidise the accessibility of the encounter.

That shift is larger than it sounds. So much disability accommodation is organised around individual exception. Someone identifies a need. Documentation may be required. A deviation from the standard process is approved. The system remains unchanged except where a particular person has successfully demonstrated entitlement to modification. Field design asks a different question: which features of the standard process are doing useful evaluative work, and which are simply inherited friction?

That question benefits more than autistic people. An explicit criterion helps anyone who has been excluded from the tacit cultural codes through which professional expectations are usually communicated. Advance questions can reduce irrelevant performance variance for people working in a second language, people with anxiety, people whose thinking benefits from preparation, people whose cultural norms around self-promotion differ from those embedded in the interview. Written options may reveal capacities that live badly inside rapid oral exchange. Universal benefit does not make the autistic argument less specific. It reveals how much of what we call accommodation may actually be better design.

And better design gives the field account something else it needs: a way to test itself. If I am right that field stability changes the dependable availability of generative language, then deliberately altering field conditions should change observable performance. We do not have to settle this by choosing which theoretical account feels more humane. We can compare the same substantive competency under different field conditions: conventional interview versus explicit criteria, surprise questions versus advance questions, immediate oral response versus processing time, one-shot answer versus clarification and repair, live verbal account versus work sample.

If nothing meaningful changes, the field account weakens. If performance changes substantially and systematically, then the design itself becomes part of the explanation.

That is why I resist describing these changes merely as accommodations. Accommodation asks whether the person can be helped to survive the assessment. Design asks whether the assessment deserves to survive in its current form.

The employer still evaluates. The university still assesses. The clinician still gathers evidence. The institution still has standards, obligations, thresholds, and legitimate reasons to distinguish one outcome from another. The field argument does not remove judgement. It asks judgement to become more accountable to the conditions under which its evidence was produced.

For most of my life, stability has been treated as something I am supposed to bring with me: prepare enough, regulate enough, script enough, predict enough, mask enough, become legible quickly enough that the people holding power do not have to experience uncertainty for very long. That is one way to manufacture a field. It is expensive, fragile, and extraordinarily convenient for the surrounding structure because the structure never has to change.

There is another possibility.

Build some of the stability into the encounter itself. Make expectations visible. Give language time to become. Let clarification count as communication rather than failure. Measure the thing you actually care about. Permit the field to learn, even if only a little, before interpretation becomes final.

A stable field does not have to be old. It has to be sufficiently coherent that the person inside it is not spending most of her available capacity constructing the conditions under which her capacity can appear.

That can be designed.

And once it can be designed, its absence stops looking inevitable.

It becomes a choice.