Change Details

This task involves the work with inviting relevant WMF Product Teams to review the proposed UX (mobile) for the "Edit Check" the Editing Team is proposing to introduce. NOTE: we will be inviting Senior Contributors to share input in T327330 === Learning Objectives //The consultations we are using this ticket to plan are in service of learning the following:// 1. What – if any – thinking embedded within the initial reference check user experience the Editing Team is proposing (T325711) defies/runs counter to what WMF staff know to be true? 2. What – if any – work that other teams have done/are doing/are planning might the Editing Team be able to integrate into the work Edit Check they are doing/have planned and vice versa? === Consultation Plan |Team|Prompts|Method|Point of Contact|Notes |---|---|---|---|--- |Growth| **1.** What do these designs lead you to wonder about? **2.** What about these designs is unclear to you? **3.** What about these designs runs counter to what you think to be true about newcomers? **4.** What – if any – opportunities do you see for ways in which Growth Team functionality/code could be extended for use in Edit Check| Async feedback + synchronous discussion (scheduled for 7 Feb)|@KStoller-WMF| |Moderator Tools| //@ppelberg to document once clear//| | @Samwalton9| |SSA working group | //@ppelberg to document once clear// | | @MaryMunyoki| |Structured Data| | | | |Machine Learning| | | | |Platform| | | | |Apps| | | | === Findings //This section will contain a summary of what surfaced through these conversations/this consultation.// === Done

This task involves the work with inviting relevant WMF Product Teams to review the proposed UX (mobile) for the "Edit Check" the Editing Team is proposing to introduce. NOTE: we will be inviting Senior Contributors to share input in T327330 === Learning Objectives //The consultations we are using this ticket to plan are in service of learning the following:// 1. What – if any – thinking embedded within the initial reference check user experience the Editing Team is proposing (T325711) defies/runs counter to what WMF staff know to be true? 2. What – if any – work that other teams have done/are doing/are planning might the Editing Team be able to integrate into the work Edit Check they are doing/have planned and vice versa? === Consultation Plan |Team|Prompts|Method|Point of Contact|Notes|Next Steps |---|---|---|---|---|--- |Growth| **1.** What do these designs lead you to wonder about? **2.** What about these designs is unclear to you? **3.** What about these designs runs counter to what you think to be true about newcomers? **4.** What – if any – opportunities do you see for ways in which Growth Team functionality/code could be extended for use in Edit Check| Async feedback + synchronous discussion (scheduled for 7 Feb)|@KStoller-WMF| | |Moderator Tools| //@ppelberg to document once clear//| | @Samwalton9| | |SSA working group | //@ppelberg to document once clear// | | @MaryMunyoki| | |Structured Data| | | | | |Machine Learning| **1.** How – if at all – might the Edit Check MVP depend on Machine Learning? //and// **2.** In what ways might future iterations of Edit Check be able to benefit from ML?|Meeting: 28 Feb 2023 |@calbon | | |Platform| **1.** How – if at all – might the Edit Check MVP depend on the Platform teams? //and// **2.** In what ways might future iterations of Edit Check be able to benefit from services/capabilities the Platform Team offers?|Meeting: 1 March 2023|@DAbad |[Meeting/Platform Engineering + Editing](https://docs.google.com/document/d/1Rh5utQWXkI0o6HAWPpXJRA-Auz8s6B4P07eWfX2-Vf0/edit#heading=h.cvovobu75mkt) | T330959, T330807#8659090 |Apps| | | | | === Findings //This section will contain a summary of what surfaced through these conversations/this consultation.// === Done

This task involves the work with inviting relevant WMF Product Teams to review the proposed UX (mobile) for the "Edit Check" the Editing Team is proposing to introduce. NOTE: we will be inviting Senior Contributors to share input in T327330 === Learning Objectives //The consultations we are using this ticket to plan are in service of learning the following:// 1. What – if any – thinking embedded within the initial reference check user experience the Editing Team is proposing (T325711) defies/runs counter to what WMF staff know to be true? 2. What – if any – work that other teams have done/are doing/are planning might the Editing Team be able to integrate into the work Edit Check they are doing/have planned and vice versa? === Consultation Plan |Team|Prompts|Method|Point of Contact|Notes|Next Steps |---|---|---|---|---|--- |Growth| **1.** What do these designs lead you to wonder about? **2.** What about these designs is unclear to you? **3.** What about these designs runs counter to what you think to be true about newcomers? **4.** What – if any – opportunities do you see for ways in which Growth Team functionality/code could be extended for use in Edit Check| Async feedback + synchronous discussion (scheduled for 7 Feb)|@KStoller-WMF| | |Moderator Tools| //@ppelberg to document once clear//| | @Samwalton9| | |SSA working group | //@ppelberg to document once clear// | | @MaryMunyoki| | |Structured Data| | | | | |Machine Learning| |**1.** How – if at all – might the Edit Check MVP depend on Machine Learning? //and// **2.** In what ways might future iterations of Edit Check be able to benefit from ML?|Meeting: 28 Feb 2023 |@calbon | | |Platform| | | | |Apps**1.** How – if at all – might the Edit Check MVP depend on the Platform teams? //and// **2.** In what ways might future iterations of Edit Check be able to benefit from services/capabilities the Platform Team offers?|Meeting: 1 March 2023|@DAbad |[Meeting/Platform Engineering + Editing](https://docs.google.com/document/d/1Rh5utQWXkI0o6HAWPpXJRA-Auz8s6B4P07eWfX2-Vf0/edit#heading=h.cvovobu75mkt) | T330959, T330807#8659090 |Apps| | | | | === Findings //This section will contain a summary of what surfaced through these conversations/this consultation.// === Done