Target state

A specified future condition you intend to reach and recognize by a deadline.

You want to "get conversational in Spanish," and eight months of app streaks have produced exactly zero conversations. The wish has no finish line you could recognize, so nothing you do ever clearly counts, and nothing ever clearly fails either. Vague aspirations are unfalsifiable, which is comfortable and useless.

A target state is the most familiar destination form: a specified future condition you intend to reach and recognize by a deadline. Use it when the desired state is knowable, causally reachable, and stable enough to justify aiming at an endpoint. To build one properly, the spec requires five elements: the beneficiary and an observable state (by June, hold a 15-minute Spanish conversation about daily life with a new speaker, asking for clarification instead of switching to English); a baseline; a horizon with some tolerance; protected floors or anti-goals (don't sacrifice the joy that keeps you studying); and an evidence-and-review rule. What changes when it works: every week either moves you toward a checkable condition or visibly doesn't, and drift becomes detectable. When not to use it: when the endpoint is unknowable or the terrain is still dark, reaching for a crisp target too early is how you march efficiently to the wrong place. The classic error: confusing a vivid endpoint with a controllable one.