Your User's Computer Sucks

I often tell people that “you are not your user.” I’m an interaction designer. It’s part of my job description. What I should probably also be reminding people is that your computer is not your user’s computer. Nor is your internet connection, monitor, environment, or a lot of other things.

Why is this important? These things mean that, aside from making your product usable in a lab setting or in your office, it’s also got to work well in the standard environment of your user.

So, ok, if you build tools for lean startups, you can probably ignore most of this post. Your users all have dual core machines (probably more than one), fiber internet connections, 24 inch flat screen monitors, and a cubicle or office in which to use those things. They probably also have a smart phone that never leaves their hand and a comparable set up at home so that they are never more than a few inches from enough computer power to get them burned as witches in some parts of the world.

But the rest of you probably build products for teens or busy families or doctors or construction workers or business travelers or, you know, the vast majority of humanity that doesn’t use a computer for a living. And you need to not only understand your users; you need to understand your user’s computing environment.

I do a lot of in-home/office studies as well as remote usability testing. This means that, not only do I get to see real users with my products, I get to see them use them on their computers, and I’ve seen this over and over.

Here are a few examples of how your user’s environment really matters:

Your Computer is Faster than Your User’s

Interactions that take a split second on my machine sitting right next to the server may take two or three seconds on an old computer half way around the world. This doesn’t seem like much, but it has a pretty big impact.

When an interaction takes a split second, I don’t need to plan for any intermediate feedback (a spinner, a progress bar, a disabled button, etc.). When an interaction takes three seconds, I really, really do need one of those things, or else I’m going to get repeated button presses and confused users who don’t know whether anything is happening. Of course, interactions that are annoyingly slow on my computer are going to be completely intolerable to a lot of my users.

You Have More Computers than Your User Does

I have a laptop and a smartphone at home that are all my own, and I use them constantly.  The other day, I asked a user why she chose to use a product late at night. She explained that she had school aged kids who needed the computer in the afternoons, and during the day she was typically out of the house. Her only computer time was a few minutes after the family was all in bed.

Many products are used by multiple people during the day on the same computer, sometimes at the same time. Having limited time on a shared computer creates all sorts of design implications for things like privacy and the need to be able to interrupt and resume tasks.

Your Monitor is Bigger than Your User’s Monitor

Of course, then there’s monitor size. Many people have declared the death of “the fold” because people don’t mind scrolling a bit for interesting information, but I still see products with really important calls to action that don’t show up on screens smaller than a bay window.

Guess what? I’ll scroll to read the second half of a blog post, but I’m not going on a damn treasure hunt for your Buy button. If I don’t find it quickly, there are a whole lot of other sites that will sell me what I want. If your target audience accesses your site on laptops or smartphones or Etch A Sketches, figure it out and design accordingly.

Look, “getting out of the building” isn’t just another way of saying “chatting with customers.” It means understanding customers and how they use your product. A big part of how people use your product is dictated by the environment in which they use it. So make sure that you don’t only understand who is using your product and how they are using it. Learn WHERE they’re using it and on what sort of equipment. It can make a huge difference.

Like the post? Follow me on Twitter!

The Best Visual Design in the World

As I’ve mentioned before on this blog, I don’t do visual design. It’s not that I don’t think it’s important. I’m just not very good at it.

Even though I can’t produce gorgeous visual designs, like every other person on the planet, I know what sorts of visual design I prefer. I don’t have one particular style that I’m in love with, but I have pretty strong reactions, both positive and negative, to different “looks.”

Recently, I worked with a company that had a visual design I didn’t like. Now, since I’m not a visual designer, I’m not going to speculate on whether it was badly designed or just not to my taste, but I will tell you that when I showed it to many people in Silicon Valley, they didn’t like it either.  

In fact, enough people reacted negatively that I stopped showing it to people in the Valley. I even found myself apologizing for it, despite the fact that I didn’t design it, and I don’t love it.

And then I did some user testing on the site. And do you know what? The users love it. They LOVE it. It is absolutely fantastic for this particular demographic, which, by the way, has nothing to do with the Silicon Valley CEOs and designers who were horrified by it.

I was showing some wireframes, with the usual disclaimers of “this isn’t how it will look; these are just black and white mockups of the final site; we’re not losing the other color scheme; blah blah blah.” Despite repeated statements to this effect, users would periodically interrupt the test to volunteer how much they love the visual design of the current site and how they really don’t want it to change.  

Why is this important? It’s a great example of the fact that your visual design should reflect the aesthetic of your target market and not necessarily you. Say it with me, “You are not your user.”

Designing a beautiful, elegant, slick site that will appeal to designers, Silicon Valley executives, and Apple users is fantastic…if you’re selling to people like designers, Silicon Valley executives, or Apple users. That’s not the market for this company, so they’re smart not to build a product that appeals aesthetically to that market.

Is there such a thing as bad visual design? Sure. I’ve certainly seen visual designs that interfered with usability. Buttons can be too small; calls to action can be de-emphasized; screens can be too cluttered; navigation can be hard to find. But just because something isn’t visually appealing to you, doesn’t make it a bad visual design. The only people who have to like it are your users.

In your next design meeting, remember this: the best visual design in the world is the one your users love. 

Love Thy User: 5 Tips for Dealing with Tough Customers

Sometimes we build products for ourselves, but most of the time our target market is somebody completely different. It can cause all sorts of problems when we’re asking questions and observing people completely different from ourselves. Sometimes, and this can be tough to admit, we don’t really like our users very much.

Maybe you’re not like this. Maybe you’ve never had a difficult set of users who constantly yell and scream about their needs and how they’re not being met regardless of what you do for them. Maybe you’ve never spent time building a brand new feature designed to make your users happy only to have them shrug and say, “oh, that’s not what we wanted at all.” Maybe you’ve never had a passionate community of early adopters all grumpy because their favorite suggestions aren’t being followed to the letter. But trust me, the rest of us have.

The problem is, because most of our users are so different from us, their behavior can be extremely hard to understand or predict. On many occasions, this has led people to ignore their customers or neglect to include them in the development process.

I understand this impulse. I really do. It can be tough to include somebody that you see as irrational or hard to deal with in your decision making process.

But here’s a news flash. That irrational, difficult, whiny, impossible to understand person who is always complaining? Suck it up, cupcake, and include them in the conversation. They’re paying your salary, and if you ignore them for long enough, they’re likely to stop doing it.

Here are a few ways to make it easier to get feedback from difficult groups of customers.

Keep it one on one

When you’ve got a group of people, all of whom seem hell bent on complaining about how your product is ruining their lives, don’t put them in a room together.

A lot of companies like to establish customer advisory panels or customer forums and the like, where they can get feedback from a lot of people at once. These are fine when the conversation can be kept civil, but they can quickly turn into an angry mob as the group forms a giant echo chamber of hate.

Keeping the conversation one on one allows you to spend more time with each person and understand what’s really upsetting him or her.

When To Get Help With User Research

I don't spend a lot of time on this blog telling you why you should hire me to talk to your customers. In fact, the vast majority of the posts are meant to make it more possible for you to talk to your customers without hiring somebody like me. It's not that I don't like working. It's just that I think that anybody who is responsible for making decisions about products should know how to learn from users on their own. It results in better products for all of us.

Product owners need to be involved in customer research for a lot reasons. Reasons like:

• You're more likely to believe the results if you participated in the research.
• You're more likely to understand the relative importance of customer problems if you observed the problems happening.
• You will come up with more comprehensive solutions to problems when you understand the context in which they're happening.
• It's far too easy to ignore a report written up by a usability consultant, it's incredibly easy to forget to watch the testing videos.
• If you do it yourself, all of the lessons you've learned will stay within the company, long after a consultant has gone on to other projects.

That said, I'm about to tell you why you may need to hire somebody like me. For a little while at least.

When I talk about customer research or customer development or learning from customers, I really mean quite a lot of different techniques. Sure, there are general best practices around talking to customers, tips for improving your research skills, and important things you should avoid, but there are also things like picking the right testing method or tool that you almost certainly have no experience with. You need to know what is the most important thing for you to do right now.

Do you know when it would be helpful to do a card sort? A journal study? A contextual inquiry? Do you know when it's fine to do a remote usability study vs when you should really run one in person? How about when your product will benefit from using an online tool like usertesting.com or fivesecondtest, and when something like that isn't useful? Do you know what sort of testing to do in order to find out why specific metrics are lower than you'd like? Do you know when you should start your visual design and when you need to concentrate on usability? Do you know how many people to talk to in order to answer a specific question? Do you know at what points in the development cycle talking to users is critical and when it's a waste of time? Do you know how to take several hours of free form user conversations and turn it into a small number of features or bug fixes that can be communicated to your engineering team?

If you answered, "of course I know that" to all of those questions, then move along. You almost certainly have no use for somebody like me to come in and help you out. If you answered, "I'm going to learn the answer to all of those questions," then I wish you good luck on your journey of discovery. I'll warn you though. There are more questions just like those.

If, on the other hand, you said, "I don't know the answer to a lot of those questions, but I wish somebody could help me understand the small subset of them that matter to me, as a product owner, so that I could get on with the business of building a great product," then you might want to give me (or somebody like me) a call.

Because it's true that there is a huge amount to know about talking to your users. But it's also true that, at any given stage in your product development, you probably only need to be concerned with only a little bit of it. And, it's also true that figuring out which bit of it you need to know can be really hard to do without help. That's where people like me come in handy. We can help you figure out what to do next, and then we can help you learn how to do what you need to do next.

But be careful. If you're a lean startup, you probably don't want to pay us to actually do what you need to do next. For all the reasons I mentioned above, that's still your job.

Interested in this sort of service? Learn more about Users Know here.

Want to read more posts on how to do this stuff yourself? Follow me on Twitter!

Shut up, and Show Me Something

I admit it. Quite often on this blog I give you long lists of fairly hard things to do. I ask you to change your whole approach to design or product management or customer interviewing or analyzing data. But not today. Today, I share with you one simple thing that is easy to remember and will transform your entire approach to customer research.

Ok, maybe it's not quite that cool, but it really will help you communicate with your customers better. Are you ready? Here it is:

Never have a conversation with a user (or potential user) where you don't show them something.

That seems simple enough, right? But why on earth should you do it, and what could you possibly show them?

Reasons for Communicating with Customers

Let's back up for just a moment. The main reasons that people generally talk with a user are:

• To get information from them - what they like, what they don't like, what's confusing, why they're not buying things, etc.
• To give them information - here are the features of the product, here's how to fix your problem, we swear it's a feature and not a bug, etc.
• To sell them something - whatever it is that sales people do...besides drinking heavily

All of these things are much easier to do when you're looking at visual aids.

Getting Information from Users

Let's perform a thought experience. Without thinking about it, name three things you hate about doing your taxes. Were you able to do it? Of course you were. If you can't think of three things you hate about doing your taxes, either you're not paying attention, or your hiding all of your money in an offshore account in the Caymans. But are they really the three worst things?

Probably not. They're just the three things that you happen to think about when put on the spot. Next tax season, you'll be doing your taxes and think to yourself, "Oh right, THAT thing! I hate that thing! I wish I'd thought of that when I was asked for three things I hate." And you most likely would have thought of it if you'd been going through your tax preparation software when I asked.

Sure, you can just ask users what they like and dislike about your product, but you will get much better information if you're both looking at the product together. Even better, ask them to perform some tasks or just use the product while you watch. This not only jogs the user's memory about all the little annoying things that they're sort of used to, but you can also observe all the things that they don't even notice or are too embarrassed to mention they're having trouble with.

Nobody is Thinking About Your Product

When you're working at a startup it can be all-consuming. You can forget everything else in your life pretty easily when you're neck deep in valuations and minimum viable products and customer acquisition and a million other things that need your attention. You tend think about your product every waking minute.

That's why it can be such a shock to realize that nobody else is thinking about your product. Well, ok, unless you're Apple, but there's clearly some kind of weird mind control thing going on there. In general, when you have a new product, you're incredibly lucky if you're getting more than a few minutes of attention from anybody but your most passionate early adopters.

Why is it important to realize this? It's important, because it has a really big impact on how you design your product and connect with your users.

Make Everything More Discoverable

You know exactly where in the user interface to go to do every task that can be completed with your product (I hope!). Other people, especially new users, don't even know that most of your features exist. This means that it's just as important to design for discoverability as it is to design for usability. But how are they different?

Let's do a quick thought exercise. Imagine somebody hands you a featureless metal box. You might look at it for a minute or two. If it's particularly attractive, you might admire it, but you're probably not going to spend a lot of time with it. Now imagine that the box has $10,000 dollars inside of it. You will probably spend a lot more time figuring out to get it open, yes?

Your product is like that box that is hiding money. If people don't discover very quickly that it provides something valuable to them, they're not going to spend much time figuring out how to use it. You need to help people understand immediately that your product has features they really, really want. That's discoverability.
You also need to make it pretty easy to actual learn how to use those features, once they've decided to dig into the product a bit. That's usability. For bonus points, you can make the whole process interesting and engaging so that people actually enjoy discovering features and using your product. That's fun. 

Key Take Away: Users are not going to spend any time learning to use your product if they don't immediately understand what's in it for them. Make it easy for them to figure out what features exist and why they're useful.

Some Surprising Problems Caused By Using Your Own Product

We've all heard the stories of huge companies that started because the founder wanted to do something specific but didn't have the proper tools. He or she built the proper tools and quickly realized that he or she wasn't the only one who wanted those tools. Paul Graham wrote a very interesting blog post about what he calls organic startup ideas a couple of months back and why building something you need is often the best way to start a company.

There are a lot of benefits to being your own product's first and biggest user:

• You will always have at least one person who likes and uses your product
• Even if nobody buys it, you'll still be happy you built it, since you get to use it
• You always have a user available to consult on which feature to build next
• It should be easy to initially identify a target persona (hint: you may need a mirror)
• You probably have a network of similar people who may also want the product
• You can find a lot of bugs and corner cases by using your product on a regular basis

But there may be a few problems that you weren't expecting.

Understanding the New User Experience

Frankly, there is nobody worse at figuring out how confusing the new user experience can be than an expert. And, if anybody is an expert at the product you've built for yourself, it's YOU.

Have you ever tried to explain something "simple" to somebody and realized that it isn't, in fact, simple at all? It is extremely complicted with lots of steps. The only reason you think it's simple is because you've done it a million times. Unfortunately, it can be very difficult to assess how hard it is to learn something once we know too much about it.

For example, if you already know that a feature exists somewhere in the product, it's much easier to figure out where it is than if you're brand new to the product and have no idea that the feature even exists. It's also easier to understand the logic of how different features work together if you're the one who put them together in the first place. 

The fix: Luckily, there's an easy fix for this. Watch new users with your product. Select people in your target market and just observe their struggles. Use products like usertesting.com to observe the first 15 minutes of their usage. Get in touch with people who have only used your product a few times and ask if you can watch them (not in a creepy way), in order to understand what slightly more experienced people are doing with your product. Whatever you do, when you see somebody making a mistake, don't correct them! It's important to see how people who aren't you are using the product.

Asking for Feedback

Remember all that stuff I recommended you do for new users? You should also be doing it for much more experienced users too. The problem is, you probably won't.

In my experience, people who are big users of their own product are less likely to think that they need to observe customers because they have one right there in the building! It's hard to admit that you don't know everything about a product that you're both building and using extensively.

The issue here is that you're not the only type of user. You may not even be the main type of user. When Twitter was first developed as an internal communications tool, do you think that the creators thought that Ashton Kutcher would one day be using it to tell his fans what he had for lunch? People are out there doing really surprising things with your product. You need to learn what they are, and you can only do that by talking to them and observing them.

The fix: This one's easy. Just make sure to keep getting feedback from other users. Preferably, search out people who are different from you or who are using your product in very different ways.