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. Meeting Standard Operating Procedure.

Next Meeting
25 Aug 2015

To be triaged:

Last Meeting Action Items

 * Make sure there is a Phab ticket for each item on the list and that they are all tagged "#design_research_backlog"
 * Done

New Action Items

 * Nirzar to book review meetings for Upload Tool
 * Trevor to book Broad Concepts meeting
 * Abbey to publish report
 * James to do walkthroughs for VE Education and Link Inspector with Abbey et al

Projects

 * 1) Support unforeseen VE Launch issues
 * 2) No news 11 Aug
 * 3) Flow: Exploratory Workflows Research (T101331)
 * 4) Done 2015-08-11
 * 5) VE Mobile Research (independent from Demo effort) T101333 / report: T106422
 * 6) Research done; still need to complete analysis
 * 7) Create and execute a test plan for the VE mobile prototype phab:T88756:T88756
 * 8) VE team is publically committed to undertaking some user testing of mobile prototype by end of Q1 (end of Sep 2015)
 * 9) We have a design (based on design principles, not testing) that is the basis of current implementation tasks; may be able to use this for testing
 * 10) Flow: Exploratory Notifications Research Phab. (T100650)
 * 11) There was a change last week, priority is not notifications, but new priority not solidified and Danny going on vacation for a week
 * 12) Danny and Jonathan will figure out next week what the next step is
 * 13) VE Education Features – T108620
 * 14) Next step is walkthrough of work with James & Abbey
 * 15) VE Link Inspector (T101166)
 * 16) Next step is walkthrough with James & Abbey
 * 17) Content Translation Translation Dashboard
 * 18) Jonathan and Pau working on it, but no update for 2015-08-11
 * 19) ContentTranslation: Translation lists T104353
 * 20) User Research created a presentation on editing experience for new and casual editors – LINK
 * 21) Done, link to come.
 * 22) Change to the behavior of VisualEditor when cursor is near a link – T91285
 * 23) Changes the nature of typing around links so that entering into the text of a link becomes a positive action
 * 24) flagged for Nirzar
 * 25) had been avoiding this for various reasons but appears necessary due to language support issues
 * 26) probably a fairly constrained UI, but we can do some exploration around it
 * 27) Next Step: VE team make a clear design and shares with Abbey and Nirzar for review
 * 28) Amir would like to review as well
 * 29) Needs heuristic, maybe then a quick usability test for new and maybe experienced users.
 * 30) Amir: Mobile in CX parent task: T106396, DR task: T108700
 * 31) Identify user targets
 * 32) not starting immediately, but notification
 * 33) New Upload tool in VE and WikiText Editor – T40030
 * 34) Prateek working on the Multimedia part and Nirzar working on VE part; met last week to coordinate
 * 35) Nirzar to check in with Prateek again, and Trevor and James for design questions
 * 36) Abbey: DR is available to discussion
 * 37) Card sort for Info Arch in toolbar in VE: T97001
 * 38) Nirzar: not complete
 * 39) "Concepts in broad user interaction" project
 * 40) High level on the project: research question? / time lines? / persona this is for?
 * 41) where does this fit into priorities for the team?
 * 42) Next step: Trevor et al to meet with DR
 * 43) clarify conceptual questions
 * 44) start planning generative research
 * 45) Abbey: include Reading Department?
 * 46) Link recommendations in VisualEditor – LINK
 * 47) Project that Data Research are working on
 * 48) Nirzar working conceptual designs with them
 * 49) Needs a lot of work to integrate

Discussion

 * 1) Who will build mobile contribution functionality?
 * 2) "Mobile" team no longer exists; mobile responsibility is now dispersed into each department
 * 3) VE team are already doing a lot of mobile work, Collaboration have been good at this
 * 4) Most ex-mobile department people are now in Reading
 * 5) Amir: Don't currently have mobile skills in Language team
 * 6) Trevor: Everyone needs to take these on; may need to start sending out testing devices
 * 7) using our pragmatic personae and the future of personas
 * 8) DR iterating, approaching being done.
 * 9) Want to make sure they're used as part of the initiation of new work across the piece.