Preconditions: Why Check What Must Be True Before Effort Can Work?

A precondition is not merely something that would be helpful to have. It is a condition that must already hold before a particular step can become possible. Its practical importance is simple: when an action has not entered a workable process at all, more effort usually just repeats the same failure.

Suppose you have forgotten a password and request a reset. You can press the button repeatedly and carefully enter your name, but if the system requires access to the registered email address or a recovery key, that access is a precondition. When it is missing, the answer is not to try harder at the reset screen; it is to restore an identity-verification channel. Only then can the later steps do useful work.

A precondition differs from a goal, a cause and a dependency. A goal is the state you hope to reach. A cause explains how an outcome is produced. A dependency is something the activity continues to rely on after it has begun. A precondition answers an earlier question: do you currently have the entry point or standing needed to take this path? The same condition can change its role when the path changes. Email access may be required for one reset process but not for an in-person identity check.

Identifying preconditions is not an excuse for delay. The useful distinction is between “cannot yet begin” and “began but performed poorly”. The first calls for satisfying the missing condition or choosing another path; the second calls for better capability and execution. Much wasted effort comes not from weak will, but from treating a door that has not yet opened as one that can be forced by pushing harder.