Begin with the activity that matters to the user
A health function should be framed as participation, safety, or self-management rather than a higher abstract score.
An older adult may want to plan an unfamiliar bus trip, manage a multistep recipe, or follow a rehabilitation schedule. Choosing “better cognition” as the endpoint makes almost any result look relevant. Naming the activity exposes whether the selected training domain shares demands with the real goal.
- Ask what daily change would matter
- Describe the activity concretely
- Identify the cognitive demands involved
- Include the user’s own priorities
Meaningful function precedes product selection.
Map the exercise to a plausible supporting skill
The relationship between a game and daily activity should be explicit, limited, and testable.
Route-planning puzzles may practice some visuospatial and sequencing operations used in travel, but actual transit also involves reading signs, mobility, judgment, stress, and changing environments. The exercise can support one component without representing the full activity. This map prevents a narrow task gain from becoming a sweeping promise.
- List shared demands
- List important demands the game omits
- Avoid one-score explanations
- Preserve other supports
A plausible link is a hypothesis, not proof of benefit.
Distinguish training from treatment and prevention
Commercial practice can coexist with health care, but the categories should not be conflated.
A game may provide structured activity and document trained performance. It does not by itself diagnose impairment, reverse neurologic disease, or prevent dementia. New decline, safety failures, medication concerns, or changes affecting independence deserve appropriate professional assessment regardless of streaks or scores.
- Keep product claims task-specific
- Do not delay evaluation of decline
- Maintain prescribed care and accommodations
- Reject disease-prevention shortcuts
The absence of a treatment claim does not erase a modest functional benefit.
Require persistence and everyday relevance
A short-term score gain becomes more useful when it survives a delay and appears in a valued activity.
First test retention on the trained or equivalent task. Then observe the real outcome—perhaps completing a travel-planning exercise with fewer external corrections. Improvement should be weighed against practice effects, changes in assistance, sleep, and concurrent rehabilitation. Everyday evidence is demanding because everyday life changes.
- Schedule a delayed task retest
- Measure the daily activity independently
- Document concurrent support changes
- Look for both benefit and burden
Transfer needs evidence at the level where the benefit is claimed.
Judge net value, not cognitive prestige
A program is worthwhile only when its usable benefit exceeds time, cost, fatigue, frustration, privacy burden, and displaced activities.
Thirty minutes spent training may replace exercise, sleep, social contact, or a task with clearer benefit. Conversely, an enjoyable brief program may support engagement even when transfer is limited. Reassess whether the user values the activity, understands the evidence boundary, and can stop without guilt or penalty.
- Count time and recurring cost
- Track fatigue and frustration
- Notice displaced beneficial activities
- Respect the user’s preference to stop
Health value is personal and functional, not a leaderboard rank.