Readiness

Readiness is the operator’s perceived state of being prepared to act, and most operators wait for it longer than they should.

The system runs a readiness gauge. Some signal — confidence, comfort, the felt sense that the conditions are right — has to register before the operator commences action. The gauge is partly informative, partly misleading. When it is reading correctly, the operator does have the resources or the timing aligned and the action lands. When it is reading incorrectly — which is often — the operator delays action that was actually available, waiting for a state that doesn’t reliably arrive.

---

The mechanism that produces unreliable readings: the system tends to report not-ready when the action is unfamiliar, exposed, or unfamiliar in its outcome. The discomfort of these conditions feels like unreadiness, and the operator interprets it as data about whether to act. The data is usually about whether the action is comfortable, not whether it is feasible. The operator who waits for comfort before acting waits indefinitely on the actions that matter most, which are usually the uncomfortable ones.

The cultural narrative tends to celebrate readiness as a virtue. When you’re ready, you’ll know. This is partly true for some kinds of decisions and badly misleading for many others. Waiting for readiness on actions that require building capacity through doing produces the operator who never builds the capacity — because the readiness was supposed to come from the doing, and the doing was deferred until readiness arrived.

---

From the chair: distinguish the kind of readiness signal you’re receiving. Is the system reporting that the operator currently lacks resources or information that the action genuinely requires (legitimate not-ready), or is it reporting discomfort with the unfamiliarity of the action (manufactured not-ready)? The first warrants delay until the resources or information are acquired. The second warrants action despite the discomfort.

The diagnostic question: if the discomfort were not present, would I do this now. If yes, the not-ready signal is the discomfort, not actual unreadiness, and the operator’s job is to act despite the signal. The action will produce the readiness in retrospect — having done the thing once, the system updates and reports more readiness for the next instance. The operator who waits for the readiness without doing the thing does not get the readiness.

You become ready by doing the thing. Most of the time, waiting is what prevents the readiness from ever arriving.