Why I Google My Own Watch: A UX Critique of the Casio G-Shock

I was in an airport, flight boarding in 20 minutes, and I needed to change my watch to the local timezone. The watch on my wrist was a Casio G-Shock GA-700UC-8ACR - shock-resistant, 200-metre water resistance, built like something a military contractor would spec out. I pressed MODE. The display shifted. I pressed it again. Something changed. I pressed the top-right button. Nothing obvious happened. I gave up and Googled "GA-700 change time." That search took less time than the watch would have. That's the problem.

The G-Shock line has been around since 1983. The GA-700 specifically is a premium model - it has a World Time function covering 48 cities, a 5-alarm system, stopwatch, 24-hour format toggle, and DST switching. It's a sophisticated piece of hardware. The spec sheet is impressive. The interaction design is not. And that gap - between what the product promises and what the experience delivers - is exactly what a UX designer is supposed to notice.

Every physical interface depends on a mental model - your assumption of how the thing works before you touch it. The G-Shock's mental model breaks immediately. There are four physical buttons: top-left, bottom-left, top-right, bottom-right. The problem isn't which button does what in isolation. The problem is that the same button does different things depending on which of the watch's six modes you're in, with no consistent logic between them. There's no grammar to this interface - no rule you can learn once and apply everywhere. You have to memorize each mode's button behavior separately. That's not a learning curve. That's rote memorization dressed up as a feature set.

Changing the time isn't hard in absolute terms. The display does tell you which mode you're in - the mode name appears on screen. That's where the legibility ends. The hard part begins the moment you try to do anything. After pressing MODE to reach Timekeeping, you're confronted with four physical buttons and zero context for what any of them does right now. There is no label on the watch face describing button functions. No on-screen prompt. No affordance whatsoever suggesting you should hold ADJUST for two seconds to enter edit mode. That hold is the interface's first invisible wall - a hidden entry gesture with no signifier, documented nowhere on the product itself. And if you manage to get in, the problem restarts: the buttons change function in edit mode with no on-screen mapping to guide you. One cycles through fields (hours, minutes, seconds), another increments the value, another decrements. Which is which? Press and see. This is trial and error by design. The GA-700 has a World Time function specifically for travelers. But accessing it - let alone setting your home city - requires the exact same opaque ritual. For a feature built for frequent flyers, that's a significant miss.

The MODE button cycles you through six states: Timekeeping → Alarm → Stopwatch → Timer → World Time → back to Timekeeping. The watch does show which mode you've landed on - a genuine affordance, and worth acknowledging. But knowing your mode only gets you to the starting line. The deeper problem is what happens next. Each mode has its own button logic, and none of it is visible. In Timekeeping mode, pressing buttons at rest does nothing meaningful. To actually edit the time, you need to hold ADJUST - a gesture that carries no label, no prompt, no signifier anywhere on the physical product or the display. Once inside edit mode, one button steps through fields, others adjust values up and down. The watch never shows you which button does which. There are no soft-key labels updating on screen, no contextual hints, no legend. You press buttons to observe effects. You guess, observe, correct, repeat. Nielsen's sixth usability heuristic - Recognition Rather Than Recall - states that interfaces should minimize memory load by making actions and options visible (Nielsen Norman Group, 1994). The G-Shock demands the inverse: complete memorization of button semantics across six modes and two distinct states, normal and edit, with the product providing zero recognition support at any point. Norman's Gulf of Execution, from The Design of Everyday Things (2013), describes the gap between a user's intention and their understanding of what actions are available to achieve it. This watch has a structural Gulf of Execution: you know you want to change the time, but there is no bridge between that intent and any discoverable action. The result is that a task you might face once every few months becomes a guaranteed Google search - not because users aren't paying attention, but because the interface was never designed to be discovered without a manual.

“The manual isn't a safety net. It's an admission that the interface can't stand on its own.”

Donald Norman's concept of the Gulf of Evaluation describes what happens when a system gives users insufficient feedback to understand whether their action worked. The G-Shock sits squarely in this gulf. When you hold ADJUST to enter time-edit mode, the watch emits a beep - if button tone is enabled and you happen to hear it. But there is no visual confirmation: no cursor, no animation, no blinking field, nothing on the display changes in a way that clearly signals edit mode is now active. In a noisy environment - an airport, a subway platform, anywhere with ambient sound - that beep is gone. If you held too briefly and nothing entered edit mode, you won't know until you've already pressed two more buttons. The feedback loop is fragile, and that fragility is what turns a 10-second task into a 3-minute frustration - or a Google search.

This is where I want to be fair. Casio is working within real constraints: a monochrome LCD with limited pixel real estate, no touchscreen, a sub-$100 price point for most models, firmware that has to work across 50+ watch variants, and a global audience with no assumed language. These aren't excuses - they're legitimate design parameters. But the GA-700 launched in 2016. Budget smartwatches with app-configured settings had existed for years by then. Higher-end G-Shock models — the GB and GBD series — have had Bluetooth connectivity and app pairing since around 2013. The GA-700 has none. No Bluetooth, no companion app, no software escape valve. The physical interface is the only interface. That makes getting it right not a preference, but an obligation.

The hardware constraints are real, but they don't explain all of this. The highest-value fix would be contextual soft-key labels - small on-screen indicators per button zone showing the current function. Digital cameras have done this since the 1990s. Hardware synthesizers do it. Casio's own ProTrek solar-GPS watches do it. Within the G-Shock's existing LCD footprint, even single-character labels updating per state - something like ► for increment, ◄ for decrement, ↵ for step - would collapse the Gulf of Execution without adding cost or complexity. The ADJUST hold currently relies solely on a beep tone as confirmation - one that disappears in a noisy environment and is silenced entirely if button tone is off. Adding a visual confirmation - flash the active field, blink a cursor, do something on the display that signals edit mode was entered - would make the transition unmissable regardless of context. The MODE cycle could support reverse scrolling with a hold - overshooting a mode shouldn't require four additional presses to lap back around. And the strongest long-term fix would be adding Bluetooth connectivity - a standard feature on higher-end G-Shock models since 2013. App-based configuration is not a novel concept; Casio's own GB and GBD series have demonstrated it for over a decade. Adding app pairing to the GA-700 line would let users configure alarms, set timezones, and adjust settings in seconds from a clean mobile interface. At its price point, this is feasible. The question is whether Casio sees the interaction problem clearly enough to treat it as a reason to invest.