Sometimes it can be very hard to distinguish what you know about your product or industry from what your user knows. But it’s important! Making assumptions about your user’s knowledge can lead to products that are impossible for normal people to use.
The Details of How Your Product WorksYou know all the technical and implementation details of your product. Your user doesn’t even know what those things mean.
One company I worked with had a feature that allowed users to mark off all the items they owned from a list. The engineers knew that, when a user made a selection, that selection was sent to the server in an AJAX request, so the account was kept constantly up to date.
The users didn’t know this. During testing, several users went through, marked off all their selections, and then searched in vain for a Save button. They assumed that they would have to save their work, since they had no idea about the AJAX request that was happening in the background.
The solutions to this were either to allow the users to explicitly save with a button or to give them a tiny amount of feedback while the item was being saved via a very brief wait spinner.
Once we implemented the latter solution, users immediately understood that each click was actually saving the item automatically, and they no longer looked for that Save button.
The take away: Don’t make any assumptions that your users understand what you’re doing for them unless you’re explicitly telling them in some way.
Every Single Feature and Its PurposeYou designed and built every feature in your product, so you know exactly what each of them does and where to find it in your product. Your user knows only what she finds during her time using your product.
One company I worked with had a very useful feature. When I interviewed users about new features they’d like to see, many of them requested the feature, even though it was already in the product! They simply had no idea that it even existed.
The take away: It’s not enough to create fabulous new features. You have to make sure that your features are discoverable by normal users.
Specialized Knowledge About the Product SpaceSometimes we build products to help people do hard things more easily.
Tax preparation software is a fantastic example of this. It is safe to say that most of us who use tax preparation software do not know nearly as much about tax preparation as the people who are building the software. At least, I hope they know more than I do!
The problem arises when we lose touch with exactly which parts of the space the users understand well. We can start to use jargon or terminology that makes perfect sense to us because we hear it all the time. We can design processes that seem completely reasonable if the user already knows the goal.
Unfortunately, this creates complicated, confusing products that assume a much higher level of understanding than the user has.
The take away: When you’re trying to help users accomplish a complicated goal, you need to work even harder to keep the interface simple.
Of course, your customer knows some stuff you don’t know...
How She’s Used to Doing ThingsIf you’re creating a product that is meant to help a users do something they already do (again, tax preparation or any business software), your goal is to create a generic experience that will satisfy as many people in your core demographic as possible.
But remember, each of those users already does things slightly differently. For example, if you’re helping people who sell things on eBay, you have to understand that each seller already has a process that she follows - from pricing to listing to shipping to dealing with customers.
Asking your users to change too many of their behaviors in order to use your product creates a huge barrier to acceptance.
If you only talk to a few potential customers (or, even worse, none at all), you run the risk of creating something that isn’t broadly usable by all sorts of different users.
The take away: Understanding the variations in user behavior will help you deliver something that is usable by a larger segment of your user base.
Imagine you’re creating an application for rating wines (or coffee or chocolate or movies or anything else). You may have very specialized knowledge of how wines are made or how the selling process works or how ratings systems are best implemented.
But your users will likely have very specialized knowledge about various types of wines. They may have quite different opinions about categorization or information display because of this specialized knowledge.
By taking advantage of your users’ knowledge, you can have them help you improve your product without your having to first learn everything there is to know about your product space.
The take away: You don’t need to know everything about your product space, but you should take advantage of the expertise of your users to improve the product and continue learning.
Why Is It Important to Know What Your User Knows?It’s important to learn what your customer knows so that you’re not creating unnecessary confusion. A product should work with a user’s expectations and understanding rather than demanding the user learn a complicated new way of doing things.
How Do You Learn What Your User Knows?By listening to them, of course. Having conversations with your users about your product and how they use it will help you to understand exactly what they know and don’t know.
You might even learn something about your own product space, and you’ll definitely learn how to make your product better.
Like the post? There are more like it. You should follow me on Twitter!