I recently watched this quick video on the Immutable Rules of UX, 39min. Curious about what they are? Check out the video, or my notes below.
These are my notes from the video.
Even in early tech, people like using a little picture of themselves; customization.
Use the 3 principles of UX: design, test, measure. Test with real users. Test before you launch. Use prototypes. Remember your first design will be wrong.
Don’t invent new terms to get respect for UX. Producing results will get you respect.
People have limited brain capacity. Design accordingly.
Usefulness = Utility + Usefulness. Without both, people will not use your product. AI/Voice Interfaces don’t have much usefulness to increase adoption, yet. They must improve if they will succeed in the future.
Remember that the web is really big and most people spend their time on other people’s sites. This means that user expectations keep changing and improving based on other people’s sites. Always keep improving. Satisfaction is a matter of the relationship between what you get relative to what you expect.
Remember that UX is about people.
From the presentation
In his presentation, he put the following list, which you can find at this part of the video. https://youtu.be/OtBeg5eyEHU?t=783
I hope this short, 2:36 video is just the start of a more public conversation about hiring practices within the UX community. I hope it helps to define UX titles and terms, and I hope it helps UX teams break past unspoken practices in team dynamics and hiring. A video like this is a long time coming and covers one aspect of a topic I have been thinking about for the past few years.
The UX Unicorn Myth (Jakob Nielsen)
Summary: UX constitutes many different specialties such as researcher, interaction designer, and Information architect. Forcing one person to do it all is a prescription for mediocrity.
First post of 2018 is all about new resources and tools I learned in January, even though I’m writing in February.
Well, it’s a new year and it’s time to get back into writing. I had hoped to be a little more rigorous this year, as well as posting at least once a month, but I’d started writing this post way back in January and I’m just now getting to it in Feb.
So far, there are two subjects I definitely want to write about this year. The first is my experience learning front-end web development. The second is a critical commentary on UX hiring practices. I’ve started writing the second, but I just haven’t gotten the formatting quite right. I also have a few other topics waiting to the side, and I’m excited to get to those, too.
In the meantime, here are a few interesting things I learned this week (back in January).
Now that I am working in e-commerce, I’m really interested in learning more about e-commerce experiences. The goals are a little different from web applications and digital products, but actually more straightforward. The goal is, essentially, getting out of the way of people making purchases. Although the results found on this site are hidden unless you pay, it’s still helpful to just have the names of the sites to review.
A site that goes over many psychological principles of user experience. Some of these are also similar to fallacies or biases, such as the recency bias. One of them is not actually a “law”, and is just a renaming of Gestalt. I’m not a fan of renaming terms that have perfectly good names. But I am a fan of this concept and the site itself. It gives me ideas for the design of another site – maybe a site about goats.
As I explored the laws of UX site, I found that it had been built on a templating language that I was not aware existed. Nunjucks seems a lot like Pug (or Jade), in that you have a template with content chunks that get written independently and ported in via extend calls. I’m not explaining it well, but templating is amazing.
It is called “IBM Plex”. I like it, but it kind of looks like it would be the favorite font of Lt Commander Data.
Zappos Mobile App: Search with emojis
Presumably I downloaded this app because I was looking for shoes. Rain boots, really. Anyway, I was pretty (ahem) delighted to discover that you can search via emoji on the Zappos app. Here are some screen captures from my iPhone, where I’m searching for women’s dress boots.
Version Control Tools for Designers
This week I also came across some version control tools for designers. These are all for Mac computers, and specifically Sketch files. (Sketch is OK, but not great, IMO.) Abstract made the most sense to me; it seemed the closest to git. But here is the list for all 3. I haven’t used any of them.
It’s cute and friendly, using sketchy animation to demonstrate the poses. I think I might send this to my mom.
You can read more about the production process over at Product Hunt. Looks like he used a product called “Hype” which is the first I’m hearing of it. It’s only $50(!), but doesn’t sound like it’s for production, unless you have a small project like this.
In my last post, I discussed a project I had been completing as part of a Skillshare class. This is the second post in that series.
As I left off in my last post, I skipped over the persona portion of the course. I did return, in part, to personas but not until the visual design.
I ended up doing about 3 pages of sketches. My documentation shows how I worked out smaller interaction elements, like navigation elements.
This is the part of the workflow is where the interaction design and user experience start to come together. The instructor chose to update the Southwest app. The visual design looked great and I liked her workflow overall. But there was a piece of this workflow that was missing – and that was competitive research. There was little in the way of looking at related apps to get an idea of what people might experience from something similar.
It’s easier to become efficient with a new interface if it contains familiar elements. This is one reason why I research competitors. I’ve also found that using real life examples helps convince others on the team that the product is actually feasible and can implemented as designed.
I did some looking around on my own, finding screenshots from different library websites. The Audible, the Apple Music and Podcast apps, and SoundCloud were helpful. It may be confirmation bias, but this competitive research was far more useful than the personas I didn’t create.
The difference in the wireframes for this project, and projects I’ve done at work, is how she used a vertical layout to present her work. I thought that was pretty smart. And, though it wasn’t specified in the course, I included annotations because I wanted to include ambiguity. (Normally I’d include more.)
For the actual wireframes, I created 2 layouts. I noticed when reviewing the other apps that there’s often a large image in the center of the screen. I felt that this was unnecessary, especially on the playback screen. My solution was to reduce it and focus on the controls.
The next and final post in this series will be about the visual design work I did for this project.