Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Usability survey first draft

From TYPO3Wiki
Jump to: navigation, search
This page belongs to the Human-Computer-Interaction - Team (category HCI)

notice - This information is outdated

It has been replaced by the Usability Survey page.


Introduction

The survey should help getting knowledge of those issues:

  • Learn which type of user (persona) is filling out this survey (for clustering them later on) and which characteristics he/she has.
  • Learn which tasks he/she is doing mainly with typo3
  • Ask him/her where he/she has major problems with typo3
  • Ask for improvements

Survey

1) Usage

Purpose: The first part has to be easy answering for getting into the survey. Asking the user about his usage is suitable here IMHO.

  • What role fits best to you if you think of your work with TYPO3?
    • [ ] I use TYPO3 as editor only
    • [ ] I am admin of one or more TYPO3-sites
    • [ ] I am both: admin and editor
    • [ ] I am a developer of extensions and/or core (possible option)
  • Which version of TYPO3 are you using?
    • () -3.6
    • () 3.8
    • () 4.0.*

The questions here are in a table with this frequency scale: ( ) most of the time | ( ) some of the time | ( ) Not very often | ( ) Never | ( ) I don't know what it is

  • Which parts of TYPO3 are you using and how often?
    • News
    • Task-Center
    • Workflow
    • TemplaVoila
    • Uploading files
    • Editing files online
    • Writing content online
    • Managing Users/User groups for backend usage
    • Managing Frontend Users/Frontend user groups
    • Managing Forums or similar entries
    • Viewing visitor statistics


I Think that you should consider that there are different type of end-users of TYPO3 and to the many who are just users who adds pages, for these this survey will be very difficult to fill in. if it is an online survey I will suggest that you divide the survey into two streams one for editors and one for admin/editors. The questions you ask are fine for admin/editors, but most editors will not understand the questions. See www.hci-cbs.dk/moodle log in as guest and look at current experiences at the interviews and user descriptions there. Lene Nielsen (usability researcher)

Comment: It might be good idea to have the question more taskbased than modulbased.

1b) Task Performance

Purpose: There should be a part, asking the user, how she or he usually solves a specific task.

  • How are you creating a new content element?
    • Via page>Create new record
    • Via List>Create new record
    • Via right click on the page element (comment: Is it left clicking?)
  • How do you edit page headers?
    • [ ] Via page > click on page icon (tree) > Edit page properties'
    • [ ] Via page > Icon upper right (edit record)
    • [ ] Other way
  • How are you uploading images (for content including)?
    • [ ] Upload them Filelist > select folder > Button 'upload files before editing content'
    • [ ] Upload them during editing content with "upload" button
    • [ ] Using the folder icon ("browse for files") and upload the images there
  • Where do you select the content-type for a newly created content-element?
    • [ ] In the content-type menu before the final content form
    • [ ] Via dropdown (Type:) in the final content form
  • How do you mainly get your content into the Rich-Text-Editor / Textfield?
    • [ ] I write content outside of TYPO3 (e.g. Word) and Copy&Paste it from there
    • [ ] I write texts directly into TYPO3.
    • [ ] I write news into TYPO3 directly, longer texts within an editor.
  • How do you mainly edit your content?
    • [ ] via frontend-editing
    • [ ] via backend > Web > Page
    • [ ] via backend > Web > List
  • How do you create new pages?
    • [ ] via Web > Page - select a page - then click symbol for adding new page
    • [ ] via Web > List - select parent page - then click symbol for adding new page
    • [ ] via Web > Functions
    • [ ] via pagetree context menu

2) Ease-of-use

Performance scale: ( ) Fast and without any problems | ( ) Takes some clicks but works fine | ( ) Works, but takes too long | ( ) Would like to use it, but its not easily operated | ( ) I don't know

  • How well can you perform the following tasks with TYPO3?
    • Getting HTML-Templates into TYPO3
    • Insert a new page
    • Rename a page
    • Insert a new Content-Element
    • Edit a Content-Element
    • Edit content through frontend-view
    • Upload files
    • Managing uploaded files
    • Editing files online
    • Writing / formating content in RTE
    • Copy&Paste content in RTE
    • Adding new BE-users
    • Adding new FE-users
    • Configure backend access rights
    • Configure frontend access rights
    • Install extensions
    • Set up a textmenu
    • Set up a graphical menu
    • Set up a multilanguage site
    • Set up a multidomain site

3) Extensions

If you are using the following extensions, please comment on them: scale: ( ) totally agree| ( ) agree | ( ) Neither agree nor disagree | ( ) disagree | ( ) totally disagree

  • Extension: News
    • Configuring News is simple
    • Creating new news is easy
    • Editing existing news is easy
    • List-view is suitable for displaying news
    • News listing is clearly arranged (what does this mean? I don't understand the statement. Susanne Moog)
  • Extension: TemplaVoila
    • Creating new pages is easy
    • Selecting templates is comfortable
    • Creating new content-elements is solved well
    • Using different languages is hard
  • Extension: Kickstarter
    • Kickstarter is easy to use
    • Creating new extensions with Kickstarter is intuitive
    • Kickstarter is well documented
  • RealUrl
    • RealUrl is easy to setup
    • RealUrl is well documented

4) Documentation

Likert scale: ( ) strongly agree | ( ) agree | ( ) neither agree nor disagree | ( ) disagree | ( ) strongly disagree

  • What do you think about the following statements?
    • TypoScript (TS) is well documented.
    • Documentation for editors is easily to understand.
    • Documentation for installing and configuring extensions is well sorted.
    • Documentation for installing and configuring extensions is well helpful in most cases.
    • Documentation in extension's code is well done by the developers.
    • Generally speaking, I can easily find solutions for my questions and problems with TYPO3.
  • How would you suggest a novice editor to learn TYPO3 ?
    • () Read a TYPO3 book
    • () Read a web-tutorial
    • () Print out and read an editors guide as PDF
    • () Explore TYPO3 on him/herself
    • () Visit seminars to learn it
    • () Use forums (maillist, newsserver, irc)
    • () Look at official TYPO3-site
    • () I don't know
  • Can you link or name your favorite document according to your answer above?

[_________________________________________________] (link)

  • And now, how would you suggest a novice administrator to learn TYPO3 ?
    • () Read a TYPO3 book
    • () Read a web-tutorial
    • () Print out and read an editors guide as PDF
    • () Explore TYPO3 on him/herself
    • () Visit seminars to learn it
    • () Use forums (maillist, newsserver, irc)
    • () Look at official TYPO3-site
    • () I don't know
  • Can you link or name your favorite document according to your answer above?

[_________________________________________________] (link)

5) Personal usage

  • How often are you logging in into a TYPO3-System?
    • ( ) hourly
    • ( ) once a day
    • ( ) 2-3 days a week
    • ( ) once a week
    • ( ) once a month
  • How many different TYPO3-Systems (different websites) do you use?
    • ( ) 1
    • ( ) 2
    • ( ) 2-5
    • ( ) 6-10
    • ( ) more!
  • How experienced are you with the following?

(Likert-scale from "professional | experienced | I know it a bit | heard of it | don't know")

    • ( ) HTML
    • ( ) CSS
    • ( ) PHP
    • ( ) mySQL
    • ( ) JavaScript
    • ( ) TypoScript
    • ( ) creating webdesigns
    • ( ) usability testing
    • ( ) Other CMS (except TYPO3)
    • ( ) customer support for TYPO3
  • Which type of site-management are you using mainly with TYPO3?
    • ( ) Classic Sitemanagement (modern)
    • ( ) TemplaVoila (futuristic)

(Note: This question is important, because managing content is dependent on which type you use)

  • How long are you using TYPO3?
    • ( ) < 1 month
    • ( ) 1-6 month
    • ( ) 6-12 month
    • ( ) 1-2 years
    • ( ) >2 years

perhaps this scale above is a bit to "undergraduate"? Shure, at least >4 must be there, too. --Daniel Brüßler 21:50, 19 October 2006 (CEST)

  • Which role do you have most of the time if you are using TYPO3?
    • [ ] Editor
    • [ ] Administrator
    • [ ] Extension-Developer
    • [ ] Core-Developer
  • What would you say, how experienced are you with TYPO3 in general?
    • ( ) novice user
    • ( ) intermediate user
    • ( ) expert user
  • In which context are you using TYPO3?
    • [ ] private, non-commercial site
    • [ ] commercial (company publishing)
    • [ ] commercial ("I / we sell typo3-services")
    • [ ] organisatorial (university, NGO, etc.)

good questions!!!

6) Template mangement via Modern Template Building

Some questions is probably needed around this. This will probably say a lot about userfriendlies.

7) Template mangement via TemplaViola

The same as for Modern Template Building.

8) Configuration page/user/ext

Is it your opinion that installing Typo3 is (easy ..impossible)

Is the size of the install packages and it contents (to large .. to small)

Is enough extensions installed with the installation packages (to much, about right, to little, always has to download a lot)

Is it your opinion that TypoScript usage is (easy ..impossible)

Is it your opinion that user mangement? (easy ..impossible)

Is it your opinion that setting up extensions in general is? (easy .. impossible)

last) Personal information

  • How old are you?
    • Age: _____
  • Your gender?
    • ( ) Female
    • ( ) Male
  • What is the first thing you would improve with TYPO3?

[______________________________________] (textfield)

  • Where are you from?

[Drop-Down list of countries]

  • Are you...
    • [ ] publishing a weblog constantly?
    • [ ] reading typo3 forums regularly?
    • [ ] writing TYPO3 extensions?
    • [ ] attend to customers related to TYPO3?
  • Would you take part in "remote-usability-testing"?
    • ( ) yes: feel free to contact me via email: ___________________
    • ( ) no: thank you
    • ( ) there is no need for improving TYPO3's usability

"remote usability testing" has to be explained ofc

  • Please select one or more fitting statements which describe your attitude to TYPO3 best
    • [ ] I use it and I already help to make even more of TYPO3 (write code, documentation,...)
    • [ ] TYPO3 is great! I use it but don't want to contribute in development.
    • [ ] I would like to contribute, but I don't know how.
    • [ ] I would like to contribute, but I have too less time.
    • [ ] There are enough people who develop TYPO3, my help is not needed.
    • [ ] There is enough good documentation out there.
    • [ ] I would share my TYPO3-experience with others if it wouldn't cost much time.
    • [ ] I am persuing the development of TYPO3.

Thank you very much for your participation!

Example:

2.1.3 What about the taskcenter?

  • [ ] Never used it - just kick it!
  • [ ] Used it very often - please keep it!
  • [ ] Would really love to use it - doesn't work properly!
  • [ ] Please improve it!

Describe the reasons for your decision here:[ ]

Comment: This looks like a really bad example of a question.

Wishlist

  • I'd like to have some questions about sharing/ contribution. People may think that they cannot contribute something - but the Glossary for example can be developed by many people. To write a definition for a new word doesn't need much skills.
    • Glossary - new word or better definition, A documentation-document - check if ther're dead links or thinks what should be better, A documentation-document - improve it with the content what others contributed, An extension - solve one ore more problems what it has, The core - solve one ore more problems what it has

--Daniel Brüßler 15:01, 19 October 2006 (CEST)

Thanks for putting this in your questionare!


One more point would be good:

  • To ask what the personal motivation is to share

=> So people think about it. To think about it can prevent a burn-out -- for me it was very important. --Daniel Brüßler 21:44, 19 October 2006 (CEST)


To get more people answering it I have this idea: If there's a lite-version and a full-version we get many details from the full-answers, and a good base-statistic based mainly by the lite-version. Because many people are lazy. --Daniel Brüßler 15:23, 17 November 2006 (CET)

I personally don't see the point of the items from Daniel. This is a survey about HCI, not the community.

  • Try to discover what is the most common workflow for different tasks and modules in the backend. How do people add content. What do they like and dislike about the workflow
  • What do users want what they already know from other applications, like drag and drop, things like that.
  • TIP for the languages: don't ask them the language they want the survey in, but the language they use in the backend of TYPO3. This sounds awfully silly, but otherwise they are asked about definitions they don't know. I'm Dutch, but use an English backend. My opinion is that if users use the backend in English, they are familiar in English and know how to read the questions.
  • Use easy to read questions and answers. Don't get technical if a user stated he/she is just a simple editor.

--Patrick 15:07, 21 November 2006 (CET)

Just an input to make the survey more precise: What do you get when you make a survey? - Numbers. Therefore you have to consider the questions in relation to the feedback you get 1) you can ask about demographics: age, gender, job role, years of use of typo3 2) how often the system is used. 3) tasks, but only in a very non-descriptive way, as you as survey designer has to define the tasks 4) what part of the system is used, but as above only in a very non-descriptive way, as you as survey designer has to define and name the parts

You can correlate 1 with 2,3,4. The answers will provide rough insight into how many do what tasks, how many uses which parts of the system, and how many uses the system at an "often" scale.

The advice is: consider what you can use the answers for and what insight it will provide. And test it with friends and don't let it take more than 5-7 minutes to answer.

Lene [ln.inf@cbs.dk]