Archive for June, 2008

¿Qué? Your users speak other languages?

translate your website
photo credit

It’s common for U.S. based startups to overlook the fact that English speaking internet users only comprise about 20% of all internet users. So if you’re not translated into other languages, you’re missing a very big piece of pie – and who doesn’t like pie? Even if you’re ad based revenue model doesn’t mold well into other countries, it’s rare that more exposure won’t help – A rising tide lifts all boats…

Realize early on you’ll want to support multiple languages for your website and make sure you support unicode. This way, before you even being translating into another language, you’ll start seeing profiles and pages on your site in other languages – and then you’ll know who to hit up for translations (^_^) The second thought to keep in mind is to use a framework that supports different language files for phrases you’ll be presenting to users.

Once you know who speaks another language, reach out to them. You don’t have to do it all at once, but incrementally overtime. Somebody sends you a question, and you check out their page or profile and notice another language? Ask them if they’d be interested in translating. More often they’ll be happy to help. Why? Because not only do they get the advantage of using your service in their preferred language, but they realize the benefit they are giving to other comrades in their country. It’s pretty motivating for many people, and a link thanking them somewhere in your credits doesn’t hurt.

And when you get users helping you, make sure they realize how much you appreciate it. Keep track of their progress, send them thank you’s from time to time along the process. Let them know they are not alone, but that there are other users translating as well. And when they process is finished, make sure to push out the changes quickly – it’s not fair to have people do all this work, then leave them hanging.

Anecdotal Corner
Interesting enough, the first site wide translation on our new site, was by a user reaching out to us. He was running a Brazilian soccer forum for his friends. The site was in english, but they posted in Portuguese. He asked if we had plans to translate into other langauges, I said we did, and would want the help of our community to translate. Cut to a few emails later, and I sent him a text file of about 1,000 phrases. Within 2 weeks we opened our doors to an entirely new audience.

p.s. Bonus points to you if you noticed I ‘translated’ my ’smiley’ up there to a Japanese style. (^_^)

Comments (1) »

Creating a community of Beta Testers at Meetro

At meetro, we created a small community of ‘beta testers’, about 40 users. These were a combination of users that were with us from the beginning, to new users that really loved our product, to friends willing to provide us with frequent feedback. What did we do to create a community of beta testers at meetro?

  • Maintained a list of users that were part of this community and useful specs on the hardware and OS they were running
  • Sent out private newsletters just to ‘beta testers’ letting them know they were a special group we valued deeply and give them frequent updates on what we were currently working.
  • Gave them early versions of our software days to weeks before the rest of our users saw it. (On a website, this could just be access to a ‘test’ or ‘development’ server.
  • With each private release we highlighted bugs we fixed, features we added, and specific parts of the software that could use their rigorous testing.
  • Kept an incredibly open line of communication with them, from personal emails to hours of IM chats walking through bugs and issues that came up

Each of these were valuable in the process, and there are even more things you can even do to build community and encourage your beta testers

  • Give them access to a bug tracker (like trac)
  • Create a forum for them so they can share questions and experiences
  • Give badges or props to the beta testers to other users on your product

Leave a comment »

Outsource your Testing & QA Departments

The other day, somebody asked me “Where’s a good place to hire beta testers for a new website?” My answer:  If you already have a few hundred users on your site, then you’ve already have found them (and they’ll work for free.)

I think the best people to ‘test’ your product and provide feedback are your most passionate users. The users you can reward by giving private access to upcoming feature releases. There are a few reasons for this:

  1. Testing – Passionate users will *throughly* test your product. You won’t believe how much they will navigate around a website or software looking to explore and find new features. You don’t even have to create test plans – they’ll naturally do that for you.
  2. Rewards – By granting a few ‘passionate’ users secret access to new features, you’re ultimately rewarding them by saying they are most important to you and you’ll spend time with them and listen to their feedback. They will be proud to have this ‘elite’ beta status – give them a badge (if they have profiles), so they can show it off to other users.
  3. Quality Assurance – if you’re a startup running a consumer web app, your users will be very forgiving, provided that you have an open line of communication. For beta testers, this should include personal emails, newsletters, a private blog or forum, and maybe even giving out your IM handle. For everybody else, this just means that you have a place for news on your site – blog or forum – that you can clearly communicate you’re fixing bugs as you find them, what was recently fixed, and a process for users to submit new bugs.

Our next post will follow-up on an anecdote on how we used these practices at meetro.

Leave a comment »