Tag Archives: How-tos

With Usabilla you can collect feedback on any digital interface, be it the scan of a sketch, a wireframe, mockup, or webpage. Just set up a test, invite participants, and analyze your results. Check out the video below to see how you can create a test in no time, or read on and we will guide you through setting up a test with Usabilla step-by-step.

With Usabilla it is easy to add additional information to your participants by adjusting the URL to your test. Adding this additional information just got a lot more useful, because we added filter options directly in the sidebar when you analyze your test.

Before I show you the filter options, I will quickly recap how you can alter URLs.

Do you want to power-up your Usabilla test results? You can easily do so by hooking up a Wufoo survey to your test. Set up a form in Wufoo and redirect users to the URL of your test. You can include their answers in the URL and store these with your Usabilla test results.

Let’s have a look at a brief example case to see how simple it is to exchange data between Wufoo and Usabilla.

Why would I take the effort to write a user scenario? I know my target group—is that not enough to design for them? Knowing your target group is important and working with personas definitely helps to ‘get to know’ your users. What personas do not tell you is why users come to your site, what exactly they are looking for and how they go about it. A good user scenario helps you grasp your users goals and design your product to perfectly match them. Get to know your users, understand their motivation for visiting your site and then start designing. Let’s have a look at how working with user scenarios can help us to achieve a high user experience.

You created a Usabilla test, and you want to get as many participants as possible. Here is a tip that will help you create a default twitter message that your participants can spread. In this way you’ll encode your tweet into a URL that you can embed to the “Redirect URL” in your Test.*

Usability testing has been a fundamental tool in the UX arsenal for decades now. The value of actually meeting your customers and letting them experience your product makes a significant impact to the shape of that product. In it’s most formal version, testing can be a multi-day, multi-thousand $/€ process that delivers final analysis days if not weeks later. With many organizations moving to an Agile philosophy and methodology, UX practitioners are finding it difficult to integrate formal usability testing into this faster-paced, iterative approach to software development.

See? Lions and zebras can get along. So, too, can Agile and Usability Testing.

Automated remote usability testing is a very simple and efficient way to gather feedback on digital interfaces – if done correctly. When you do usability testing automated AND remotely, it’s good to keep in mind that the participant is missing some common communication channels. You ask participants for feedback, but you can’t see their faces, while your participants can’t ask any questions to express discomfort or uncertainty. When you’re aware of these limitations you’re able to compensate for it by carefully designing your test questions.

We’ve just updated the standard widget you can use to promote your visual surveys. If you embed this widget (optional) on your website it will be visible in the bottom right corner and looks like this:

Read the rest of this entry to see a live example and learn how to customize this widget.

Not so long ago we’ve added ‘custom variables’ to our tests. We store every variable you specify in the URL of your test and include these variables and an unique participant id (pid) in your redirect URL. That might sound a bit complicated, but enables you to store additional data for individual participants in Usabilla and to pass through data to other services as well. Let me try to explain with a simple example using a web form to submit data to a Usabilla test:

A simple web form

You can submit a simple web form to a Usabilla test. If you use ‘GET’ as method, the fields in your form are submitted as URL encoded variables. Example:

This example form submits two variables (name and group) to a Usabilla test. The form input is stored together with the test data of your participant. At the end of the test the variables will also be attached to the redirect URL. This redirect URL could be another survey as well: read about combining Usabilla with a PollDaddy survey.

A/B testing is a popular method to optimize conversion on a website. Basically you set up two or more variants, measure the differences in conversion rates between these variants, and select a winner based on your test results. The winning variant is the one with the highest conversion rates. A/B testing is a great way to improve your webpages one step a time. Unfortunately implementing tests is not always as simple as it sounds, even if you use for example the nifty interface of Google Website Optimizer. To set up a test, you need to have access to the source code and someone who’s able to adapt it, a live website with visitors or a working prototype, etc.. We’ll show you an example of how Usabilla’s One-Click-Tasks can be used as an interesting and low-budget alternative for A/B testing.