Design Research-Editing Department KIT

This is a bi-weekly meeting between the Design Research team and the leads of the Editing Vertical teams (Collaboration (Flow), Wikitext, VisualEditor, mobile editors, Multimedia, Content Translation, Upload Wizard) to coordinate and plan Design Research work. This meeting is intended to clarify priorities, define work, schedule work, manage conflicts, share findings, and ensure Design Research and Editing stay aligned in their work. See the Meeting Standard Operating Procedure.

Last meeting 12 Apr 2016. Next Meeting 21 Apr 2016.

=New Items for next meeting=

= Project Status =
 * 1) Usability Testing for Education Features T108620 (and Single Edit Tab)
 * 2) Education Features done and deck shared
 * 3) Still blocked on getting experienced editor testers for Single Edit Tab.
 * 4) Many possible testers have seen it and aren't fresh
 * 5) TODO: JMo to forward fresh emails to Samantha
 * 6) UX Testing Notifications
 * 7) Surveyed en.wiki users about notification usage
 * 8) Now surveying fr.wiki users
 * 9) Have done two user studies (e.g. UX test, aka "direct testing") on notifications page.
 * 10) Move "Compact Language Links" from Beta to non-Beta
 * 11) Amir: Have a plan to move this to non-Beta this quarter
 * 12) Pau: tested that people can see that there are more languages
 * 13) Amir: will affect site appearance in a small but significant way
 * 14) Joel: Suggest Amir to work with CL to coordinate with community
 * 15) Paying for testers
 * 16) JMo: success. We are giving people (participants, not those taking notes ;-) t-shirts and editing is paying.
 * 17) "Learnability of our Content" project
 * 18) Survey is out, 150 UW (University of Washington) students responded, two more weeks to go.
 * 19) WP, Khan Academy, and Stack Exchange are top 3 in the responses
 * 20) New Upload tool in VE and WikiText Editor – T40030
 * 21) NO UPDATE since 16 Feb.
 * 22) A/B test (T120867) inconclusive.
 * 23) check for further action
 * 24) Present Mobile research from Wikimania (T106422, T101333)
 * 25) NO UPDATE since 16 Feb
 * 26) Fix Feedback Tool UI Problems [T100011], T86956
 * 27) NO UPDATE since 16 Feb
 * 28) Make plan to deal with known usability issues in VE Mobile
 * 29) NO UPDATE since 16 Feb
 * 30) Collab Team planning
 * 31) Pau: Collaboration Team to figure out what to do next fiscal year.
 * 32) Will need to do some research during this quarter, need some help from Design Research.
 * 33) Amir: things like Review Article for Creation will be very different in different languages, I will be happy to help with that, have experience

Discussion:
 * 1) Meeting has been less useful since [Trevor and then James stopped attending regularly]
 * 2) what was useful before?
 * 3) JMo: having more people on the editing team, especially Project Managers, even Trevor.
 * 4) Easier to help projects when they need help
 * 5) have been working with Collab and CT and it's not coincidental that their POs are in this meeting regularly.
 * 6) Neil, VE, so I can know what they are doing and can support them when they need it.
 * 7) Pau: I understand and share concerns. Research needs to clearly understand the big questions and how many resources they have.
 * 8) For me in particular, it's a useful meeting because I know regularly Jonathan will be there, will have an update on the work
 * 9) If this meeting didn't exist, we could send information, but in general for the organization it would be better if the meeting it's supposed to represent has more representation from editing teams
 * 10) Joel: what gap is this meeting serving, is it serving that gap, how else would we serve it if the meeting didn't exist, is the meeting the best way?
 * 11) JMo: for me and Pau, this is good for coordination between us. (better than email or 1:1?) Yes, although we also do that.  I work with Pau a lot; when it comes to VE, this is the only way I find out what the VE team is working on, I don't understand the Phab structure, I don't know what wiki pages to go to.  Unless James F is in this meeting, I don't know what's going on with VE team.  maybe that's not important right now, but there is going to be some time when it's important for DR to know what's coming in VE.
 * 12) Pau: A key question is why people in the invite (who were relevant at one point) are not coming?
 * 13) Amir: Agree with Jonathan

on track next Thursday
 * 1) Joel: what needs to change?
 * 2) Joel to check in with James/Trevor.
 * 3) Joel to refresh the invitee list.
 * 4) JMo: we want product managers and people in design roles.
 * 5) Daisy: Replace Nirzar with Volcker.
 * 6) JMo: having Neil could be really useful, he's doing research that complements.
 * 7) next meeting

=Discussion= none this week