usability test

Answering the Drupal Why

Roy — Thu, 01 Sep 2016 21:47:41 +0000

Sub title

Something something usability testing

/sites/default/files/styles/large/public/uxtasks.png?itok=U0Q-7DUp

The basis for knowing what to focus on for evolving Drupal core is learning about what people want to do with it.
Testing the initial experience of core as a whole has had our main attention so far. Now with focussed initiatives (content workflow, media handling, outside in, layouts,…), we’re adding experimental features with the assumed requirement that we validate and improve them trough feedback from usability testing.
So, we could (should!) create a more regular schedule of more smaller instead of few bigger usability test sessions. What’s our version of getting out of the building and increasing our exposure?
What would it look like if we did test every 6 weeks?
Produce testing scripts for each initiative. These can be reused, eventually updated where needed. Every 6 weeks we run those tests for each initiative. We learn what works, what needs to be improved. Initiative teams can prioritize fixing UX bugs. All things are connected anyway so we’ll learn about overall issues as well.
Feedback from the test participants can feed into ongoing persona work: what are people trying to achieve? Voilà, we’re learning about the Why.
Of course this requires planning, recruiting participants, having a setup for remote testing, getting access to a usability testing lab once in a while, observation, analysis, designing possible solutions, reporting back to the community, creating actionable issues to work on etc. But wow, we’d learn so much about where to focus our efforts.
Who wants to help make this happen? Mail, Slack (get invite) or lets talk at Drupalcon Dublin.

Drupal usability test illustration

Roy — Thu, 19 Jun 2014 06:21:26 +0000

Coming up: the big usability lab test of Drupal 7

Roy — Wed, 11 May 2011 21:25:43 +0000

Coming up: the big usability lab test of Drupal 7 Roy 11-05-2011

The University of Minnesota has graciously offered us another opportunity to gather data and insights from observing smart people using Drupal for the first time.

The two lab tests we did with Drupal 6 really brought home the fact that Drupal can be hard to wrap your head around. The community has responded with a drastically reworked Drupal 7 and next week will give us fresh insights on what we improved, what has become worse and which new problems are out there.

The plan

On May 17 and 18, eight participants will each spend 75 minutes working through tasks around building an event site, touching the essential basics of creating content, menu links, blocks and modules.

This test will be attended by community members including Drupal 7 co-maintainer, Angie Byron (webchick) and key members of the Drupal UX Team: Bojhan Somers (Bojhan), Brad Bowman (beeradb), Dharmesh Mistry (dcmistry), Jen Lampton (jenlampton), David Rothstein (David_Rothstein), Chad Fennell (cfennell) and Erika Stenrick (estenrick).

Initial results will be shared at Drupalcamp Twin Cities which happens right after testing on May 20 and 21, on drupal.org and at Drupalcon London in august.

The results from this test will be invaluable in helping the community make better design decisions while building yet another best version of Drupal ever.

Make it happen

Improving the Drupal user experience is crucial to the long term succes of Drupal. Sponsoring this test is a great opportunity to express your support. Many individuals and corporate sponsors Acquia and Krimson already chipped in.

Will you?

Thank you!

Drupal

usability test

drupalplanet