-
135 Words
We're big believers at ZURB that we need to test any assumptions we might have before implementing a change or adding a new feature to a product. We don't just want to assume we know what users may be thinking. That's why we conduct user testing and concept testing. In fact, we built Verify to help ourselves and others make decisions based on data, not intuition.
Almost as soon as we launched Verify in 2010, we got so much feedback that it could fill a mailbag, and we noticed that one question kept popping up — "When can I get test results?" But we couldn't immediately jump on it because we were still working out the features of Verify.
We had to iron out a couple of things before the folks using Verify could get test results. On one side, we had to have a tool that you could upload your concepts onto, attach a question, and test out those assumptions. The other side was having an experienced set of passionate people that can give you great feedback about the changes and updates you're thinking of implementing. These are the types of people that have had enough of sucky sites on the web and want to make the web a better place.

So when we finally got around last November to putting together our own testing service called Enroll, we started slowly gathering a fellowship of testers. We wanted to build the community of testers first before we started offering them up to our Verify users. And it was a good way to also test the stuff we were working on.
With Enroll, every tester can keep track of the test they've taken throughout their own dashboard. There are several tests that Enroll testers are asked to take.
Click tests — Test takers are asked what gets their attention or where they would click on a site.
Memory tests — Testers are asked to list what they remember after seeing a site for 5 seconds. Why 5 seconds? What visitors to your site remember in those 5 seconds lets you know if you're actually communicating your value or intent to users.
Mood tests — Testers see a site for 5 seconds, then are asked to select 3 moods to show how they feel about the page. They can select whether the page makes them happy or sad.
Preference tests — Testers are shown 2 designs and have to choose which one they prefer.
Annotate tests — Testers can give detailed feedback on specific questions, leaving notes like in Bounce and Notable.
Label tests — Testers are asked to fill out labels and answer specific questions, such as "what would you expect to see if you clicked this tab?".
Multi-page click tests — Testers are asked to click through a sequence or workflow.
Linked tests — These suped-up, specialized tests can contain a number of individual tests that are shown to testers back to back.
We didn't want Enroll tests to be as boring as the ones you took in school with a number 2 pencil and a scantron. We actually wanted to put a little fun into the tests. So besides tracking their tests, testers can earn different badges as rewards for tasks they've completed. Like everything else we do, the badges started out life as a bunch of sketches:
An early pass at the badges.
Getting close ...
As Chris, our designer, got close to finalizing the designs of the badges, he used Influence to get feedback from the team on the designs. We were able to give Chris quick feedback by either giving the designs a "thumbs up" or a "thumbs down." With feedback in hand, Chris was able to whip up the final iteration:

While Verify users can now get test results when they create their concept tests, we're always on the lookout for testers who are passionate about improving the web.
Sign Up To Help Improve the Web