If you missed the Super Bowl last night, no need to fear spoilers here. I don’t know who won or lost, and I don’t remember any particularly impressive football moments (I do enjoy the occasional intense almost-lost touchdown or crazy avoid-all-tackles run). But I did watch the commercials, and there’s one commercial every user experience professional should watch.
The next time your clients say “is user testing really necessary?” Just show them this video. The answer is yes. Yes, test. Test, for the love of all that is holy. Test, and help us prevent future puppymonkeybabies.
Editor’snote: Two weeks later, and people are still talking about it. Is it possible this was the goal after all? Tricky marketers…
I have a friend, a fellow UX professional, who once defined compromise to me. “Compromise is when nobody is happy with the end result,” she said.
It’s important to remember that this idea exists. It’s important to prove that idea wrong. Then the only unhappiness will be when the person who believed that compromise caused people to be happy realizes they were wrong and that they don’t like being wrong. But they’ll be happy about the compromise. And that’s what’s important.
What is a UX Unicorn? Though the details vary, most agree that a unicorn is a UX practitioner who does a little of everything – visual and interaction design, front-end development, content and IA. The term has been gaining traction over the past several years, as employers seek out designers with expansive skill sets, and designers seek out ways to become more valuable to employers. Continue Reading →
Travel always opens my eyes to new concepts and UX alternatives. In Warsaw last week, I found a sign on the bus that wowed me with its usability.
This bus sign has three levels:
The top level lists out all the stops, consistent with every other bus map I’ve encountered.
The middle level (in red) divides the stops by neighborhoods.
The bottom level divided the stops by street. As a tourist this was fantastic; I knew I wanted to get as far south on Ujazdowksie Street as possible. This map showed me when I was at the southernmost stop before the bus turned onto Armii Ludowej.
My first experience with the business world was joining my father in staff development workshops. As an education consultant – and a fierce opponent of lectures – he excelled at bringing together teachers and administrators and guiding them to new ideas. Back in the 60s, teaching in his own classroom, he had often been admonished by other teachers for not “controlling” the students, or having a “rowdy” classroom. But from my father’s perspective, it was that very noisiness that signaled to him that students were discussing, probing, asking questions, and in short, learning. Continue Reading →
One of my favorite principles of agile development is #8: Agile processes promote sustainable development. It’s one of those statements that is all at once completely obvious, and yet incredibly difficult to follow. For every business that promises a “work/life balance,” there is a project that begs the exception, and requires employees to work late “just this once.” I have no problem with the exception. What I see as problematic is that often “just this once” turns into “just once a week” and then evolves into “passionate, dedicated people.”
Here’s the big secret. “We’re looking for passionate, dedicated people” is code for “don’t expect to get home for dinner.” Continue Reading →
On a sunny May afternoon in 2010, I met Dorian. He was a web developer at a small agency, with a wife and two children at home. He spent an hour or two each day online, mostly visiting sites like Reddit and Delicious (remember back when Delicious was popular?) but rarely contributing to either site. He enjoyed snowboarding in the winter, and surfing in the summer, though he rarely found the time to do either these days. Dorian felt comfortable with his personal knowledge of internet security, and prized function over form on the sites he used most frequently.
As you may have guessed, Dorian (short for Dorian Developer) was my first user persona. We detailed his preferences, his wants and needs and fears, his online habits, and his personal life based off the user interviews we’d conducted with a dozen real developers for real small agencies. Every decision we made was subject to the Dorian test: would Dorian like this? Would Dorian use that?
“It’s taken me a lot of years, but I’ve come around to this: If you’re dumb, surround yourself with smart people. If you’re smart, surround yourself with smart people who disagree with you.” – Aaron Sorkin (Sports Night)
I used to think that the best way to learn new things was to research them. I know a fair amount of content strategy, but I can learn more by researching it.
“Brand is what people say about you when you’re not in the room.” -Jeff Bezos (Amazon)
The first interview at a new company is the only time, as a new (prospective) employee, that you get to make a first impression. But more importantly, it’s the only time the company has an opportunity to make a first impression on you. As a freelancer, I’ve had many “first impression” experiences, and they’ve nearly always served as precursors to my experience with the company itself.
The company that consistently called 2-3 days later than they said they would was just as thoughtless when employees were sick or needed to schedule a meeting around a doctor’s appointment.
The company that was ready to start my interview 5 minutes early (leaving me without the extra time I’d been banking on to get a quiet moment!) was shockingly punctual, but also cared more about timeliness than preparedness.
The team that made a point of asking thoughtful questions and discussing UX design in general during the interview kicked off my first day with productive, interesting meetings that both brought me up to speed on projects and made use of the time by giving the other team members a new set of eyes (mine) to run ideas by.