Many self-regulation instructions are underspecified.
"Focus."
"Calm down."
"Stop worrying."
Each describes a desired state without defining the transition. Software engineers would reject an API that says only, "Make the system healthy." A usable interface needs observable input, permitted actions and a next state.
Mindfulness games can be understood as small state machines for human learning. The metaphor is imperfect, because people are not deterministic systems, but it reveals why concrete activities are easier to use than vague commands.
Example 1: Attention return
Focus Flashlight can be represented as:
text READY -> TARGET_SELECTED -> ATTENDING ATTENDING -> DISTRACTED -> NOTICED -> RETURNING -> ATTENDING
The important transition is not ATTENDING -> PERFECT_FOCUS. It is DISTRACTED -> NOTICED -> RETURNING.
That model transfers to reading code, reviewing logs or studying. Distraction is not an exception that crashes the session. It is a normal state with a defined recovery path.
Example 2: Worry sorting
Worry Tree distinguishes a concern from its available response:
text WORRY_DETECTED -> INFLUENCE_AVAILABLE -> CHOOSE_SMALL_STEP -> SUPPORT_NEEDED -> ASK_FOR_HELP -> NO_ACTION_NOW -> SET_DOWN_TEMPORARILY
Real worries may be partly influenceable, so the branches are not strict booleans. The value of the model is separating an outcome from a next action.
A safety concern should bypass the reflective loop and escalate to an appropriate adult or professional.
Example 3: Emotional naming
Feeling Weather Station uses weather as a user-defined representation:
text EXPERIENCE_PRESENT -> METAPHOR_SELECTED -> MEANING_ASSIGNED -> NEED_CONSIDERED
The interface must not assume SUNNY == SUCCESS or STORMY == FAILURE. The same icon may carry different meanings for different users. The player owns the interpretation.
This is a useful product lesson: labels should support communication without claiming more certainty than the data provides.
Example 4: Waiting and impulse
Wait for It isolates the transition between urge and action:
text URGE -> PAUSE -> NOTICE -> CHOOSE -> ACT
The pause does not guarantee that the chosen action will be correct. It creates an additional decision point.
Example 5: Bedtime closure
Sleepy Stars introduces an ordered wind-down and an explicit exit:
text DAY_ACTIVE -> BODY_NOTICED -> WORRY_ACKNOWLEDGED -> INTENTION_SET -> SCREEN_OFF
There is intentionally no ASLEEP state controlled by the game. Sleep is not a button outcome or a completion badge.
Design principles behind the model
Across The Holistic Care's collection of twenty mindfulness games, several principles recur:
- Isolate one learnable transition.
- Make an invisible process visible through metaphor or feedback.
- Keep the player able to pause, adapt or exit.
- Do not convert game telemetry into psychological assessment.
- End with reflection or a real-world next step.
What the model must not imply
Humans are not finite-state machines. Emotions can coexist. A person may move backward, skip a step or need another person. Context changes the meaning of the same signal.
The analogy is valuable only when it makes a response more understandable. It becomes harmful when it suggests that distress is a bug or that a learner failed to reach the expected state.
For a larger conceptual progression, progressive mindfulness courses connect individual transitions with emotions, thoughts, identity, body awareness and purpose.
The product insight
Good self-regulation design does not command an outcome. It exposes a manageable transition.
Instead of "focus," define how to return.
Instead of "stop worrying," distinguish action, support and uncertainty.
Instead of "be calm," help the user recognise what is present and choose what comes next.
That is what a useful state machine does: it makes the next transition visible without pretending that the whole human system is under programmatic control.
