Loading...
Answers
MenuIf you launch a product to a few different countries, does it make sense to do usability testing in all those different countries?
This question has no further details.
Answers
Perhaps. You have to consider how your product is used and how the users will sensorially interact with it. If you have a website, for example, you could probably assume similar US and UK usability -- but now consider layout for Semitic languages which are read right-to-left -- or consider ideographic languages where the ideographs could interact with other graphical elements in a way wholly irrelevant with the languages you're familiar with.
If you have a physical product, the question is conceptually the same, but the actions are different. You have to consider how users in a given culture use and interact with products of that sort. Different cultural memes, ways of learning and expectations can effect usability.
There are some simple ways to do these things if you have a small budget. You could easily go to craigslist and recruit 10-15 natives of a given country or region. Give them the product or have them use the website (for 60-90 minutes), video it (with their permission of course and for reasonable compensation), and you'll get a potentially useful indicator of usability. If you're P&G or Microsoft, you've got the budget to test against statistically valid sample sizes pretty much everywhere in the world. You don't have that, so you need to use some heuristics.
Good luck to you. Should you have any questions, I'd be happy to discuss.
The quick answer is yes, it always makes sense to do usability testing where there are variations in cultural preconceptions, market maturity, language proficiency (you don't mention if it will be available in many different languages) and the like.
Whether or not you do usability testing in all countries of course also comes down to what resources you have and how you intend to make use of the findings. Many times I find it appropriate to launch and test iteratively along the way, making sure you have the budget to make continuous small improvements, making sure to have feedback mechanisms in place and placing more effort in testing and managing areas which clearly are more critical for the end-user satisfaction. But you'd never want to launch before you have something that you yourself are satsified with. My recommendation would be to do quick online tests to make sure you are not entirely off-base, and then make sure to set the iterative launch-measure-analyze-prioritize-fix process in motion.
It can be safely assumed that people from different cultures will behave differently with the same product. They have different aspirations, motivations, circumstances in which they use a product, use cases, and social meanings.
If you are launching the product in countries that are very different culturally, it makes sense to conduct usability testing in different countries.
Related Questions
-
How do I run a closed beta test for my mobile application? Development will be finished in 3 weeks.
You should try to engage people using social networks, it is easier to spread than email. The conversion rate on emails are low but is still a valid tool for that. Send and email with a simple and objective message that will make people want to try. The best way to have feedback from users is to watch them use the app. You should put them on the hands of everybody that you can and without any instrucions and just watch, don´t even say that the app is yours. Try to do it a lot. If you want feedback from others, you can include the feedback form inside the app and suggest users to answer occasionally. I would also strongly recommend to use a tool as Flurry Analytics. Is the best way to get data from how is the use of the application. Pay attention to those data and be open to change your app a lot, you may need more features or cut some off to make it easier to use. If you need more help please contact me.BS
-
I work for a web design agency. We are trying to make decisions based on data. How do I know which user tests to run and when?
Sorry to be a bit blunt in my answer, but the client hired your "e-commerce web agency" to do e-commerce conversion optimization, yet your company doesn't know how to do e-commerce conversion optimization? Perhaps have a conversation with someone in your company or talk to your manager or the agency principal and encourage them to hire for e-commerce conversion optimization expertise. It's an entire discipline requiring years of experience and track record in driving higher conversions for e-commerce sites (in my opinion). In lieu of that, how many marketing dollars are going to be spent to drive traffic to the site and who is managing that part? Often new start-ups will spend so much of their dollars BUILDING the site, they don't leave much money to spend on AdWords or other methods to drive traffic to it. The amount of traffic will help determine how many tests to run and how often. Usually we start with two very different landing pages (do you have landing pages?), then fine-tune the split testing down to things like headlines and photos. The checkout pages, especially any pricing pages, are also critical in the testing. Is it a brand new concept or established product/service? If brand new, it will take very well-crafted pages to get visitors to pay money for something (vs. a trial). If established, why is your product best and why should I buy now? You should map out the conversion flows to the confirmation page (success page) and measure the drop-off or conversion rates at each step. Test different elements/pages at each step. Also measure things like average cart size (if more than one product), revenue per transaction and long-term customer value. Hope that helps. Best wishes to you!BC
-
What are some low-cost platforms for User Interface mockups?
Are you talking about actual design mockups (PSD files etc) or just directional sketches that will help illustrate ideas you're having about how to improve the pages? If leaning more towards the former, I'd put yourself in a position to not need anyone else necessarily and just focus on creating wireframe mockups of the pages (no typography or finalization of icons/the skin of the page) and start with the blocking and tackling of each page. wireframing it also let's you more easily bifurcate between the web and mobile UX (if that is a part of what you've identified as an area that can be improved upon) - plus in my experience wireframes give you more of a blank canvas to start with while not narrowing your possible ideation phase with already in-place icons or imagery - basically it lets you work from the feet up each page. Taking this step (with wireframes first) allows you to revise and iterate on your ideas and THEN go find someone to produce mockups/design files in a more streamlined fashion (you dont want to be creating and constantly editing full design iterations as that would be a heavier, cumbersome and most costly process.) I've also found the narration process around wireframes much smoother and easier for inviting other contributors and capturing the commentary of the "why" to go with your "what". Good luck, feel free to reach out if you need any other suggestions or walk to talk through options!JG
-
How do I run a successful closed beta for my web application that is almost done with development?
Create an ideal customer profile. Create some questions that will allow to you survey a potential tester to determine if they fit your profile. Design simple landing page with very clear value proposition that speaks to your ideal customer. Ask for a minimum of information up-front (email), but ask for more info after they commit by submitting the first piece of info. (KISSmetrics does a good job of this on their current website trial signup). Use the their answers to these profiling questions to put the applicants into buckets. Let in the most ideal bucket first, or split them into groups if they're big enough. Try and measure engagement the best you can. Measure qualitative and quantitative data. Schedule calls with your beta testers to find out more, especially with the ones who's user behavior seemed to indicate that they didn't get value from your product. Find out why. Make sure they are indeed your ideal customer. Pick up the phone and get to know your customers inside and out. Meet them in person if possible. Incorporate their feedback quickly and get more feedback. Rinse repeat.DH
-
What's your opinion on using something like usertesting.com vs. real time usability testing (online and offline)?
UserTesting can be instructive in terms of understanding whether people understand your copy, CTAs, and intended flows but generally, I've found the quality of their panels to be pretty low. You're almost always getting people who are not your actual users, so the feedback can only be generally applied as above. I find whatever web analytics package or packages you're using are generally able to provide much better insights. I also really do believe in *real* user panels. Buying pizza or offering small financial incentives to real users to click through new flows where they are talking out loud or answering specific questions is going to give far more actionable insights than anything else. What I like to do is take my best guesses as to what's not working or what I'm looking to improve and then discover/validate via real in-person customer panels. Happy to talk through this in more detail with you in a call.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.