Experiences performing user tests with Drupal prototypes

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
zfactor's picture

I have been working on a project recently where we have been performing user tests against Drupal prototypes. The audience is a mix of people from regular users of Drupal to marketers who have never seen the platform.

We are seeing a trend where people are regularly distracted and/or confused by things within Drupal core's interface. One example is we designed a test where users would edit a node and change the workflow state. Users found it challenging to even find where to go to edit the node.

Has anyone else had challenges with users not being able to complete user tests because of usability issues in Drupal core? If so, what are some different approaches you have taken to testing to circumvent those issues.

Comments

Hi, No, not really. But our

simohell's picture

Hi, No, not really. But our answer is a bit too general to answer properly. Drupal has a huge number of possibilities and different uses can need different approaches. For a node based funding applications evaluation system for example I pretty much only left "submit" button visible to the end user. So no problems at all there. But for another kind of site that wouldn't do.

  • How was the test setting?
  • What kind of introduction or guide they had on how to use the system? - The edit tab is a bit hard to miss usually - how was the theme and layout?
  • What kind of configuration, user roles etc.?
  • Was everything unnecessary for the user role hidden from the user interface? - For thesite admin there is often so much information that I guess hiding some of it makes sense (hence the tabs at the bottom of the node edit form), as 1st user should have good knowledge of how the system works. For other users, hide as much as possible.
  • What kind of tasks? (what was the purpose of editing a node and workflow)

Can you provide a report or the data from your findings in regard to the perceived usability problems with the core?

Hey simohell - I can't

zfactor's picture

Hey simohell -

I can't provide details on the tests because we performed this for a client. I can say we performed the work remotely via GTM and that we used a pretty stock Drupal UI.

That's fine. Only your

simohell's picture

That's fine.

Only your question doesn't really make sense without any details about the tests. If you would like a more useful answer you must be more specific. You can't ask for a solution to a problem you're not willing to describe.

The test reports commonly available, I expect, might deal with a different user segment from yours, but they did test Drupal core (https://www.drupal.org/node/1162000). There are tons of different things one could test for and just as many things where one could go wrong running the test.

For sure there are many usability issues with Drupal. But without anyadditional information, it is as good guess as any, that the problems result from your test procedure, instead of the actual UI. Could be wrong also. No way to know, you see.

Btw. you say that you see problems in Drupal core UI but then you describe a use case testing a contrib module (Workflow).

Sorry I can't be of more help.

Usability

Group organizers

Group categories

UX topics

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: