CiviCRM Community Forums (archive)

Hey people,

I've made a survey at http://civicrm.org/user-survey.

The ideas behind the survey are to:

* provide a/another way that we can measure how well we are doing as a project/product
* be reasonably quantitative so we can ask the same survey at regular intervals and see if we are getting better/worse
* be linked to specific people, not anonymous since it is good for us to be able to contact people who gave specific feedback and I didn't see any reason that it should be anonymous
* encourage people to log in to reduce duplicates and so they don't have to fill in already known info (or we send it via CiviMail with a checksum)
* be short enough for people to fill in without getting bored
* not collect information that we can / are collecting other ways (e.g. pingback stats and site registration)

Some of feeback I've had so far includes:

An additional question - I use CiviCRM for (checkboxes):
·         general contact management (CRM)
·         donations
·         memberships
·         events
·         bulk email
·         grants
·         case management
·         campaigns/advocacy
·         peer-to-peer fundraising

and maybe some questions that dig into existing use of functionality? which component area do you use the most? what component area would you like to see further developed? what areas of CiviCRM do you feel are weakest?

Might be nice to know, generally, which existing features are most relied upon and which future features would be most helpful. So let them see to lists and indicate which is most useful (rather than having them fill in the blanks...)

* There can still be value to asking what's good/bad/best/worst/love/hate on a survey -- a survey captures different quantitative info than the forums. e.g. "60% of respondents mentioned X as one of Civi's best features" seems like a broader perspective than "10 people replied to a forum post about X"

Re: the above comments, I agree that it is important to collect this info.  I think we can get a good indication on component usage/popularity from the pingback stats (admittedly, someone could have a module turned out without using it, but on average, it would give a relative comparison). We also get some similar data on organisational sector and focus etc. from the site registration form.

One thing that we don't do is ask whether they love/hate each module.  What component is best worst, so it might be worth adding that.

One question is what do we do about features that aren't considered components, e.g. SMS, import, export, profiles, etc.  Might be worth compiling a list of these things as well (we could use the book for that).

* It seems a little weird to ask for a specific date that one started with CiviCRM. Year -- OK. Month -- maybe. Day of month -- hmm?

Agree - I think there is a way round this - we have done it before - simple way round would be to let people know they don't have to be accurate to the day

* It's not possible to do the agree/disagree with a tabular layout, is it?

Not sure.

under "in your opinion" -- may want to add: improving ease of upgrades

It sounds a bit more specific than the other three.  It also sounds a bit more like a system administration task, similar to hosting, installing, which I hadn't covered in the survey.  Agree that it would be interesting to collect this info.  Makes me think that one thing we don't have a handle on is how people are using and hosting Civi, e.g. are they hosting it with internal expertise only, with a third party, etc.

The survey is 'live' now but there is no reason why we can't add additional questions as we go...

I'd like to aim to collect a lot of responses over the next four weeks.

Michael