So this Wiki page should be the right content type to collaborate on the survey. I'm willing to go to the bitter end... ;) Comments and explications here and there could be good, I suggested formatting you'll see
Personal Experience
- What do you think is the top issue keeping new users from continuing to use Drupal after installation (if they manage to do that)?
- Do you have any practical Experience or Feedback on this Question?
- What annoys you most about Drupal?
Naming the biggest flaws or strenghts
- What do you like about the Drupal Usability? not focusing too much on the negative
- Admin Interface
- Easy Installation
- Nice Themes
- Everything is easy to find
- What do you think sucks most?
- Lack of structure
- Installation is hard
- Server requirements are too high
- Hard to create my first Articles
- The many Content types are confusing
- Too many options
Suggestions
- Here are some suggestions for Improvement, vote
- Do you have other suggestions
Comparison to other CMS's / Blogs / Forums etc.
- What CMS is the best to use in your opinion (including smaller solutions like Blogs, Forums etc.)
- Wordpress
- PHPBB
- Joomla
- Typo3
- Mediawiki
- modx
- PHPNuke
- Movable Type
- What do you like especially about it
- General Look and Feel
- Editing is Quick
- Didn't take long to learn
- Lots of options
Personal Experience
- What do you think is the top issue keeping new users from continuing to use Drupal after installation (if they manage to do that)
- Do you have any practical Experience or Feedback on this Question
- What does annoy you most personally
Suggestions
- Here are some suggestions for Improvement, vote
- Do you have other suggestions
Comparison to other CMS's / Blogs / Forums etc.
- What CMS is the best to use in your opinion (including smaller solutions like Blogs, Forums etc.)?
Other
- Do you think it would impair or contradict the spirit of drupal to be "too easy"?
Personal Information
- What is your level of knowledge
- After your actual experience: Will you continue to use Drupal?
Win a Prize
- Do you want to participate in the lottery? There are great prizes: ( Dinner with Angelina Jolie )
For serious: we prizes are in the works (Trip to Barcelona? Computer Hardware? Free Hosting?) - If so: Enter your email and Address
Comments from ximo
Some good ideas! But I think we should build on the interview script drumm has made with some usability people. See http://groups.drupal.org/node/6273#comment-18082
Comments from rszrama
I don't have time to add to this at the moment, but I think the real value we're going to get from this survey is in people specifically evaluating common tasks... like setting up a menu, creating content, editing a user account, etc. CMS comparisons aren't very helpful, imo, because it will lend more toward general problems or total differences in purpose/architecture. (Not to mention I've never even touched any other CMS. ; ) I can try to contribute more to this individual topic listing and even form-by-form evaluation later on if need be.
Comments from drumm
You can not cover everything in one survey, you only have so much attention span to use. What I wrote up at http://drupal.org/node/127285 was intended to be a high-level investigation, leading to being able to write well-informed personas.
A pattern we have used in the past, which I recommend with my little usability knowledge, is doing a round of free-form interviews first, to inform the writing of survey questions. Interviews can help discover how to phrase questions in the users' language, instead of ours, and point to questions we might have forgotten or unneeded questions. The interviews are best done with the highest bandwidth, face to face, but instant message or chat can give valuable feedback for less time investment.
We have a general idea of common tasks already, from Dries's research and presentation, and the past survey. I don't think we should spend much more time on figuring out what to do, but more on how to do it. Improving any existing page design is great. Improvements informed by knowledge of users, user testing, and other research is even better.
Comments from eigentor
You make some good points. Especially the mentioning of not being able to cover too much in one survey makes me think. The main objective I've got in mind is identifying the really important areas of improvement. And only new users can really tell, we ourselves are already too biased.
So how about this:
- Keeping the idea of a survey, but narrowing it a bit
- Collecting the areas here we already know and try to set up teams to work on specific tasks