process feedback from Camille B

[gratipay]

process feedback from Camille B

[bmann]

Camille B is a designer and helps run a non-profit dedicated to preventing animal abuse. She might consider using Gittip to help support her non-profit. Currently they are looking for one-time "big" sponsorships, and don't have an easy way for individuals to support the effort.

Design

• Too impersonal = untrustworthy
• Would like to see more colour and dimension
• More negative space on the listing of participants
• I like displaying stats up in the header
• Not crazy about how the navigation items are displayed in the About section
• Not a fan of the logo, it’s a bit too simple of a shape to really stand out and be recognized as ‘Gittip’ without the word beside the icon

Functionality & Placement

• Communities should be able to keep adding once you’ve selected one that you want to belong to
  • Feel like there should be a save button under Account
  • The Members tab wasn’t stupid obvious enough about what happens here
  • Profile: it was odd that adding a website url and Facebook wasn’t an option under Social Profiles
  • Having the most popular groups listed at the top of the Communities drop-down was nice at first, but if I was looking for something specific, alphabetical would have saved some time instead of having to read every option in the list
  • Would like the option to give funds through a bank account as well (I know that you can set that up with some banks, maybe not all)
  • As a funder, it would be nice to see any updates on what the person I’ve funded are doing. I would be more likely to continue using the service, or giving more money if I liked what the people I were funding were doing.

Overall

• It would be nice to see the progress of a recipient if they are working on a specific project.
• Most people’s description of how they are making the world are really broad, (IE. ‘I am making the world a better place by coding awesomeness’) not sure what the solution to that is. Perhaps listing a specific project or goal could be a requirement?
• Would like to see more variety overall with potential recipients. In example, I may be interested in funding a Paralympic athlete, streamer, med student, care giver etc.

[bmann]

[reticketed as #61—whit537]

[chadwhitacre]

@bmann Awesome interviews, thanks! The way we usually handle this kind of feedback is with a GitHub issue like "process feedback from so-and-so," which we use to further understand the feedback and then reticket new issues and/or add +1s to existing issues. The goal is to drive towards actionable issues. See here, here and here for examples.

I've retitled this ticket to "process feedback from Camille B" and I've reticketed "process feedback from Alex M" as #61.

[bmann]

OK. I really don't think everything can be boiled down to an issue, but I guess we'll roll with what we have for now.

I don't think feedback can be "processed" individually. In fact, it's highly dangerous in overfocusing on one person, vs. looking for themes and finding 10 or 20 or 30 people that all want the same thing / react the same way.

So perhaps just list it as feedback / interview / whatever and leave it at that.

[chadwhitacre]

looking for themes and finding 10 or 20 or 30 people that all want the same thing / react the same way.

That's exactly what ends up happening with this method. So, for example, Camille mentions that she "would like the option to give funds through a bank account." I've added a +1 for her to gratipay/gratipay.com#777. Some things she mentions are old tickets, some should be new tickets, some aren't things we're going to worry about ("not a fan of the logo").

I really don't think everything can be boiled down to an issue.

Boiling everything down to an issue means we only care about action items. If we can't act on something, then ... what are we supposed to do about it?

[patcon]

👍 to the overall gathering of the surveys. Awesome stuff.

I'm inclined to agree with @whit537 that the "processing" approach has worked well for us, with +1's, new issues, etc. Just because an issue is created doesn't necessarily mean it's any sort of high priority, but it's nice to get the "ask" down in one place. Many feedback items relate to outstanding issues that have history, and issues work great for cross-referencing by those contributors with more historical context, for the later benefit of those with less. I found issue cross-referencing so useful when I first started :)

[chadwhitacre]

Closing as outdated. A lot has happened since we collected this feedback.