The same, but different, sign-in experience

Many of us who work in the business of designing interactive experiences would agree that most days we’re pretty savvy when it comes to identifying less than optimal designs and working through them to get to where we need to be. To be fair, we all have moments when maybe our synapses aren’t firing on all cylinders, or our situational awareness isn’t at 100% (aka: distracted).

But on those off days, we need better visual affordances to help us along.

Case in point. Pandora. I recently found myself trying to log into my Pandora account from the Pandora home/landing page (I’d obviously been logged in forever), and for the life of me couldn’t figure out what was happening (or not happening) to the sign in page.

Briefly, I was repeatedly clicking the “sign in” link in the upper right corner, expecting the page to refresh and do something sign-inny, like a refresh, alert or instructions, highlighting…something, anything.

Troubleshooting kicks in, and I switch browsers, believing that something must be wrong with the site in Chrome. Hey, it happens, right? But even switching browsers (to Safari) nothing changes on the Pandora home page.

Since I was focused on the page more than usual, I realized that the primary focus of the home page content (in a signed-out state) is to sign in. (How come I never noticed this before? Or overlooked it so easily?)  Studying the components more closely, it became apparent there was no large, bold type directing me to “Sign in below.” (That would have been super helpful in my case.) Instead, the copy on the page was introducing me, the account holder, to the concept of Pandora, “It’s a new kind of radio – stations that play only the music you like” followed by text fields for “Your email” and “Password” with a sign in button. At the bottom of the sign in module read tiny text, “Create an account for free.” with a contextual link, “Register.”

Pandora.com Home Page
Pandora.com Home page

Okay, I get that once you start dissecting and breaking down what the text says and the labels in the text fields with the corresponding Sign in button, it’s more obvious that the page is intended for existing members to sign in. (Though I do question the introductory nature of the copy and it’s close relationship to the sign in fields for existing members. Seems like Pandora could have done a better job of directing members to sign in while using the intro copy for creating new accounts. But I digress somewhat.)

pandora_2
Pandora “Register” page

Recall I was clicking the upper right corner “sign in” link, and there was no visual response on the page. Each time I clicked, the page appeared to remain “static” with no error message instructing me to enter my email and password while highlighting the required fields on the page. When I clicked the “register” link in the upper right had corner, the page refreshed to the Register experience. Same with clicking the “help” link. So naturally my expectation was, in my distracted limited attention state, that something should happen to the page.

(In fact, I figured out what I was overlooking when I clicked “Sign in” from the Register page, and was directed to the Pandora home page. Where I’d started from.)

pandora_3
Error messaging

What I needed to happen is what the page did when I clicked the “Sign in” button next to the sign in fields – I got red text directing me to specify my email address and password. As I would expect. (And now I know that I can sign in using the fields on the home page.)

Now granted the upper corner is navigation, and the button is for input. But even the other navigation items (register, help) have a distinct page change, so at minimum I’d expect the page to briefly refresh when clicking sign in. And maybe some language to the tune of, “You’re obviously having a stupid moment, clicking the same link expecting something different to happen.”

Lesson learned here. Language should go with the action. And, secondarily, despite the fact that both the sign in link and Sign in button are “relatively” identical calls to action, the post-click visual affordances are different. Small discrepancy, yes, but the inconsistency affecting the user from quickly and easily accessing her account is the larger issue.

 

Button Identity Crisis

Came across this beauty of a button in the upper right-corner of a lightbox overlay.

Image

 

The value of identity of course is that so often with it comes purpose.

– Richard R. Grant

Even UX for hoodies matters

Image

I am a hoodie fanatic. My husband can’t stand it and had literally phased me out of them several years ago but then they made a fashion resurgence.

However, I won’t just buy any old hoodie. The details are too important (I’m confident other hoodie freaks can relate). Too thin (as in weight)? Forget it. Not fuzzy enough? See ya. Sleeves not long enough? Buh-bye. It has to maintain the fuzzy, comfy appeal through repeated washings. I go so far as to hang dry to keep the fuzz factor from getting sucked away in the dryer (except to fluff). Even if the hoodie has a design or graphic that is the shizzzzz, if the sum of the parts don’t add up after repeated wear, fail. Honestly, I like my Lululemon Scuba Hoodie, but I don’t LOVE it.

Sounds like someone finally got hoodie design RIGHT. 

 

Dueling remote buttons

ImageThis remote has two buttons, in shades of red, in key positions at the top of the remote.  The one on the left is labeled “POWER” while the one on the right is labeled “ON/OFF.” To a remote novice like myself, my first instinct was to press the “ON/OFF” button to turn the television “on.”  Makes some manner of sense, right? After several failed attempts, I was forced to turn to a fellow co-worker and ask WTH? Turns out, the “ON/OFF” button is to turn the button lights “on” so they’re visible in the dark. (!?!?!?!) Lesson learned, but I still question the: 1) size 2) relative position and placement 3) use of color 4) and labeling applied to the Power and the On/Off buttons. It seems the On/Off button could be given a little less prominence, a different color, and don’t we have technology to make them glow in the dark or react accordingly with sensors?

 

Join Together, Be Moved

Quick break from the action to mention a recent commercial created by Wieden + Kennedy (Portland, OR) for the folks at Sony, “Join Together.” I love the concept: bringing together the engineer and the artist because, well, it’s the world I live prefer work in.

They usually live in different worlds, but when they work together, that’s when you can get something really new.

And the soundtrack, a sick remix of “Join Together,” by the Izzie Twins, is superb.

Check out the commercial (you may end up watching several times, like me) and read on: AdWeek.

UX Mobile Immersion Conference 2014 – Day 3

I begged the powers-that-be to send me to the UX Mobile Immersion Conference (#UXIM) in Denver, Colorado this year. I started submitting requests and rationale in November 2013. Since I got a passive aggressive “nope,” I’m living vicariously through Twitter right now, following #UXIM. There are some amazingly fun and informative tweets coming from the conference right now, my favorites listed below.

Creating apps that are ‘usable’ are the equivalent to food being ‘edible’ ” – Jared Spool

Jason Grigsby: When Responsive Design Meets the Real World

  • Jason Grisgby has led us all down a responsive workflow, now he is going to tell us how wrong we all are.
  • “I now use progressive JPEGs, the algorithms have gotten better”
  • “Answer to responsive tables: “What are you using the table for?” Then plan #RWD around that.”
  • To do responsive web design correctly, you are probably going to need more than responsive web design”

Nate Schutta: Coding Prototypes, Even if You’ve Never Tried

  • “If a picture is worth a thousand words, how many meetings is a prototype worth?”
  • “Friends don’t let friends use IE 6.”
  • jQuery Mobile is a HTML5-based user interface system designed to make responsive web sites and apps that are accessible on all smartphone, tablet and desktop devices.”

Karen McGrane: Adapting Your content for Mobile

  • “Print is awesome. You put the words on the paper and they stay there!”
  • “Whatever the next big thing is going to be, we are going to have to get our content onto it.”
  • “Thinking about where content will ‘live’ on a ‘web page’ is pretty 1999.” – Lisa Welchman via Karen McGrane
  • “Imitating paper on a computer screen is like tearing the wings off a 737 & using it as a bus on the highway” Ted Nelson via Karen McGrane
  • “We need systems that allow us to create content hierarchy programmatically to better translate into other platforms.”
  • “Truncation is not a content strata…”
  • We have to treat content management as UX. Content creators often want to crawl back to Word & a simple WYSIWYG.”
  • The purpose of doing the inventory is not so you have an inventory, it is so you can make decisions about the content.”
  • The user’s goal is not to look at a table. It is to give them the info they need in order to complete a task.”

UX Mobile Immersion Conference 2014 – Day 2

I begged the powers-that-be to send me to the UX Mobile Immersion Conference (#UXIM) in Denver, Colorado this year. I started submitting requests and rationale in November 2013. Since I got a passive aggressive “nope,” I’m living vicariously through Twitter right now, following #UXIM. There are some amazingly fun and informative tweets coming from the conference right now, my favorites listed below.

Luke W:

  • Hotel Tonight – 4 taps/swipes and 8 seconds to book a room. So easy babies and cats were booking rooms…
  • Hotels.com – 40 taps/109sec b/c they couldn’t let go of desktop method…

Bkuva7KCAAEXoJ_

  • “If it’s important, it should be visible.”
  • “The evil lord fold, who is a tyrant… Controls the scroll.”
  • “The problem isn’t is it visible above the fold, it’s about having it visible when the user needs it.”
  • “When the hamburger icon is paired with the word ‘menu’, it’s 7.2% better. When made to look like a button it’s 22.4%” (Facebook)
  • “Long pages, in mobile, create a flat hierarchy, heavy download and lack context generally.”
  • “We’ve been at it for 30 years designing for personal computers and ~6 years designing for mobile.”

Karen McGrane:

  • “You don’t get to decide which device people use to go on the internet. They do.”
  • “Responsive design won’t fix your content problem.”
  • “It’s not a strategy if you can’t maintain it.”
  • “Theres no such thing as how to write for mobile, there’s just good writing.”
  • “88% of Americans without a high school diploma don’t have internet access at home.”

Jason Grigsby:

  • “Resolution does not define the optimal experience.”
  • “We can no longer make assumptions about input based on screen size or form factor…and we probably never should have.”
  • “The web never had a fixed canvas.”
  • “Any attempt to draw a line around a device class has as much permanence as a literal line in the sand.”
  • “Phone, tablet and desktop interfaces are fundamentally different platforms with different usability considerations.”
  • Design for a user need not for a specific form factor or input.

Jared Spool:

  • We are not creating designers fast enough to meet the demand for user experience. Big companies are building out an army of user experience designers.
  • Experience designer (also known as a design unicorn) → information architecture, user research practices, visual design, interaction design, editing and curating, copywriting, design process management, information design.
  • Specialist → having more expertise in one area over others (really good designers, having specialization in an area outside of design)
  • Generalist→ having equal expertise in most areas
  • Compartmentalist → having expertise in only one area (a career-limit decision)
  • How to become a design unicorn:

1. Train yourself (absorb everything)

2. Practice your new skills

3. Deconstruct as many designs as you can (learn from others)

4. Seek out feedback (and listen to it)

5. Teach others

UX Mobile Immersion Conference 2014 – Day 1

I begged the powers-that-be to send me to the UX Mobile Immersion Conference (#UXIM) in Denver, Colorado this year. I started submitting requests and rationale in November 2013. Since I got a passive aggressive “nope,” I’m living vicariously through Twitter right now, following #UXIM. There are some amazingly fun and informative tweets coming from the conference right now, my favorites listed below.

  • People swap devices 21 times an hour… continuity matters.
  • #1 goal is to achieve content parity.
  • Start with a small screen first, then expand until it looks like shit. Time to insert a breakpoint. (Stephen Hay via Brad Frost)
  • Navigation (especially complex), should be scannable. There are lots of design patterns that are becoming de-facto standards.

From Brad Frost: Using Atomic Design to Create Responsive Interfaces

  • 5 Principles of Adaptive Design: Ubiquity, Content Parity, Performance, Enhancement, and Future Friendly
  • “Vocab word of the day: Interdigitate
  • “If you need to convince someone to care about the mobile web, all you need to say is ‘social.'”
  • “We’re not designing pages anymore; we’re designing systems of components.”
  • “Respect their users and their time. Road blocks and interstitials are bullshit.”
  • “Phablets – dirtiest word in technology.”
  • “More iPhones are sold every day than babies are born.”
  • “Responsive design is not expensive. The dynamic web is expensive, responsive design is not to blame.”
  • “Mobile First Design forces you to take a hard, cold, look at the priorities of your site’s navigation.”
  • ‘Don’t just do a content inventory… it’s just as important to do an interface inventory.”
  • “Carousels on home pages exist to keep people from beating the shit out of each other in meetings” #shouldiuseacarousel
  • “If you are hiding something for mobile, you are doing it wrong.”
  • If your content doesn’t make sense on mobile, you need to ask yourself if it makes sense at all.”
  • “We sell websites like paintings. Instead, we should be selling beautiful and easy access to content.”
  • “Atoms (HTML Tags) -> Molecules (functionality) -> Organisms (modules) -> Templates (content structure) -> Pages (content presentation)”

BkoT0NCCYAACs5D

 

From Ben Callahan: Workflow on Responsive Design (RWD) Projects

  • “You best solve problems using tools you are fluent with.”
  • “Do the dishes and people will follow.”
  • “The amount of process required is inversely proportional to the skill, humility, and empathy of your team.”
  • “If you don’t have the authority to say “no”, it’s not a collaborative process.”
  • “Constraints–you need them to create.”
  • “Our specializations of expertise are fragmenting the experiences we build.”
  • “Create guidelines instead of rigid process. “
Bko2bG2CMAAkHU8
Meeting Notes by James Matchett, Careerbuilder