[Interview] Marathoner Jacob Kiplimo’s Journey Toward a World Record, Made Possible with the Galaxy Watch

Why Read This from an HCI Perspective

This article shows that wearables can be more than a ‘recording tool’—they can become an interface that changes users’ behavior. Running data may look like mere numbers such as heart rate, pace, and left-right asymmetry, but in practice it becomes the signal that helps decide when to push harder and when to stop. For HCI/UX practitioners, it’s meaningful because it lets you see data visualization, feedback timing, and how the needs of beginners and elite athletes differ—at the same time.

CIT's Commentary

An interesting point is that it’s not about ‘accurate measurement’ as such, but about ‘helping with decisions.’ Here, the watch becomes a shared language between coach and athlete. For this structure to work well, the system’s state must be trustworthy, and it must be clear when the user can intervene. In particular, the example of changing a 40 km plan to a 3 km run when pain occurs shows that good AI/sensor design should not only drive goal achievement—it should also reduce failures in advance. For beginners, guidance needs to be simpler and less pressuring; for elite athletes, it needs to be more fine-grained. That means you shouldn’t design just one ‘good coach’ experience, but different coaching experiences depending on the situation.

Questions to Consider While Reading

• Q.In running-coach-like features, what kinds of explanations and warnings are most effective to prevent users from blindly trusting the data?
• Q.When showing the same metrics to both beginner runners and elite athletes, which information should be minimized, and which should be made more visible?
• Q.When a wearable’s recommendation changes a real training plan, how should user autonomy and system intervention be balanced?