3 ms·
The goal of these instructions is to guide the user on how to use Mailchimp, the e-mail system, not the UI. The plane cockpit won't show you by itself how to st
by ricardobeat 13y ago
The goal of these instructions is to guide the user on how to use Mailchimp, the e-mail system, not the UI. The plane cockpit won't show you by itself how to start the engine, that's in the manual/training.
- jamestnz 13y agoThat's a fair point. And just to clarify (since you mentioned "instructions"), my references to MC above were referring just to the colored circular non-buttons discussed in the OP, and not to the "A quick primer" and "Need help with your first campaign?" instructions (which I'm assuming are always there, and are unrelated to the non-buttons… I guess it would be nice if users could dismiss these newbie instructions once they've become experienced with the site). But if these large circular non-buttons are to remain a permanent fixture on the MC Dashboard (rather than just a temporary "look, here are our new features" exercise), I still wonder why I'd want it to jiggle the blue pointer as if to say "Oh there's the place you SHOULD have clicked just now", when it could actually just take me to my obviously-desired destination immediately. That destination page would then become active on the navbar, presumably with some kind of visual indication that it is now the active one ("presumably" because I'm just speaking extemporaneously here, I haven't used MC in ages)... so the attentive user will have learned a second way to reach their desired feature (as in, "I clicked the big round button and it took me straight to the place I was expecting, and the 'Lists' item on the navbar has become active"). Then you've provided two different ways to get to the desired feature in a single click (each method reasonable in and of itself), rather than providing one direct method (the navbar), plus an indirect method that attempts to retrain the user to click somewhere else instead.
- pwg 13y ago> The plane cockpit won't show you by itself how to start the engine, that's in the manual/training. The plane cockpit is also _not_ intended to be used by first-time users having to discover everything themselves as they go along. It is assumed the new user of the plane cockpit will be given detailed training on how to use the cockpit. UI's, and esp. web UI's, don't tend to come accompanied with _detailed training on how to use_ them. Which is why UI's _need_ discoverability and plane cockpits do not.
- jamestnz 13y ago>UI's _need_ discoverability and plane cockpits do not Interestingly enough, Boeing has a world-class ergonomics research/implementation department focusing on solving problems just like this within the cockpit. You see, it turns out that pilots were occasionally activating the switch for Undercarriage when they meant to activate the Flaps switch, because the switches were near each other on the console and they looked identical. This despite the switches being clearly labeled, and despite the intensive training that pilots undergo. Apparently this was enough of a problem that a habit developed amongst some pilots, of sticking a tiny paper cup over the Undercarrige switch shortly after each takeoff (the kind of tiny paper cup that they serve you your tiny cup of water in). The Boeing folks were tasked with this issue, researched likely causes and tested potential solutions, and (IIRC) came up with the idea of physically/visually distinguishing the switches, and furthermore to actually design each switch to be visually reminiscent of the feature it controls. (Hopefully I related this story correctly, it comes from a textbook-level source I read ages ago).
- deafbybeheading 13y agoGeneral usability is important in pretty much all interfaces, but discoverability isn't. There's a big difference between designing an interface a user will be instantly familiar with, and one that's optimally suited to the task at hand.