Skip to main content

Evaluating Your User's English-as-a-Second-Language Ability

At my company we've been dreaming of being able to localize our UIs since I started working there. While we have localized here and there for the most part it just doesn't happen. There simply aren't the resources or knowledge.

Instead our employees in all branches are required to speak English. I have no idea how branches determine whether a person's ability is up to standard to be hired. I've never seen any guidelines for branch management to follow and admittedly our industry is one where you have to learn a lot of jargon, too.

I imagine that may other global enterprises are the same way. This means that your users may struggle to understand your UI, especially those newly hired employees. So part of your user research should be pointed at determining at what level your users can understand written English.

Here are guidelines you can use based on the European Framework of Reference for Languages. (See Chapter 9 for more information.) I assigned the reading levels based on this chart at Benchmark Education. This will allow you to use tools like WebpageFX's Readability Test Tool when writing your labels and messaging.

Language Level Reading Level Ability Description
Beginner - A1 K-1
  • Uses familiar everyday phrases and basic phrases to fulfill concrete needs.
  • Can introduce themselves and others.
  • Can ask and answer questions about basic personal details such as where they live, the things they have and people they know.
  • Their interactions are simple and they have to rely on the other person/people to speak slowly and to help with their language.
Beginner - A2 2-3
  • Can understand short sentences and frequently used expressions of immediate relevance such as basic personal information and family information, shopping, local geography and employment.
  • Can communicate while completing simple, familiar routine tasks requiring simple and direct exchange of information.
  • Can simply describe their background, their immediate environment and matters of immediate need.
Intermediate - B1 3-4
  • Can understand the main points of clear and standard language on familiar matters regularly encountered in school, at work or in leisure pursuits.
  • Can deal with most situations most likely to occur while traveling in English speaking countries.
  • Can produce simple connected text on topics which are familiar or of personal interest.
  • Can describe events and experiences, dreams, hopes and ambitions.
  • Can briefly give reasons and explanations for their opinions and plans.
Intermediate - B2 5-6
  • Can understand the main ideas of complex text on both concrete and abstract topics including technical discussions in their field of specialization.
  • Can interact with a level of fluency and spontaneity  with native speakers without strain for either party.
  • Can produce clear and detailed text on a wide range of subjects.
  • Can explain their viewpoint on a topical issue giving the advantage and disadvantages of various options.
Advanced - C1 6-7
  • Can understand a wide range of demanding longer texts and recognize their implicit meaning.
  • Can express themselves fluently and spontaneity without much obvious searching for expressions.
  • Can flexibly and effectively use language for social, academic and professional purposes.
  • Can produce clear, well-structured and detailed text on complex topics while showing controlled use of organizational patterns, connectors and cohesive devices.
Advanced - C2 8-9+
  • Can understand virtually everything heard or read with ease.
  • Can summarize information from different written and spoken sources.
  • Can reconstruct arguments and accounts in a coherent presentation.
  • Can express themselves spontaneously, very fluently and precisely, differentiating finer shades of meaning even in more complex situations.


Popular posts from this blog

Doing User Research When You Have No Access to Your Users

For the 12+ years that I have worked at my company I have had extremely limited access to users. I’ve only made 3 branch visits over that time and what little access I have had, has been reserved for usability testing the applications I was working on. And, when branch visits are set up UX is usually the last person considered as a candidate to go. But when you are starting a project you need to know who you are designing for. What do you do? Covert user research! Believe it or not there are a lot of ways for you to find out about people without talking to them directly. Find User Representatives User representatives are people who are not the user, but may have been the user at some point in their career. Sometimes your business representatives can be user representatives if they did the job. I would give a word of caution here. While your business representative may have worked “in operations”, they are also heavily invested in the business goals of the company. So, you really don…

Don't Fall in Love with Your Product

I don’t know what your calendar is like, but at my company at the beginning of the year business and upper level IT managers will prioritize their needs and I’m assigned to different projects depending on priority. Sometimes at this time of the year the air feels electric. It's almost like going on a first date. Will the project be exciting? Will it match my skills? It may sound silly to compare working on a new project to a first date. But, it's far more relevant than you might guess. While we want our users to fall in love with our products, it's wrong for us as technologists to fall in love with them. If we do, we lose the objectivity we need to keep our biases out of our work and we lose the ability to clearly see and measure the results of our work. Psychology of Attraction First, let's learn a little about how falling in love works. There are three stages: Craving or lust - is used to filter all our options into a group of what we desire in some way. Attraction …

Stop Using the Word Delight in Enterprise UX

Last week I participated in on UXPin’s Enterprise Summit (2017). On the last day there was a panel discussion by UX gurus on the state of enterprise UX with Jeff Veen of True Ventures, Lou Rosenfeld, and Marcin Treder of UXPin and Sunita Redd of UXPin. Over and over and over I kept hearing them use the word delight. So here’s what I want to say:

Dear Enterprise UX Gurus:
STOP! Please stop using the word “delight” in the context of enterprise UX. Just stop. I’m not the only one who wants this.

Delight is creating an emotional bond with a user through pleasurable experiences IN ORDER TO SELL THEM SOMETHING. This is wholly a consumer-side idea. Enterprise users have absolutely no choice in whether they get to use our product. It’s already been decided by management.

I’m up for a replacement. I personally say I want to give the user a good day, but more importantly I’m trying to make users more efficient. I’m trying to create human capacity for the company. Yeah, it’s still using people …