This meta task involves the work of converging on a standard deployment 'path' for new Edit Checks and Suggestions that is at once:

1. Lightweight: it's important that the path from idea to feedback from volunteers be consistent with the speed and ease with which the Edit Check platform enables us to write and refine Suggestions
2. Measured: it's crucial that Suggestions support the consensus volunteers have aligned on and expressed through Wikipedia content policies and guidelines

Deployment path

Internal review

Step #1: Implement technical PoC

• Purpose
  • Align on viability of proposed user experience
    • Where "viability" here means the team is aligned in thinking the Check/Suggestion holds the potential to compel people (exact audience TBD) to reliably identify and address issues in ways that align with project policies and guidelines while not introducing high risk for disruption/destruction.
• Roles & Responsibilities
  • Product: Define scope
  • Editing Engineering: implement technical PoC
  • Design + MoveComms: review implementation and raise blocking issues (e.g. copy, calls to action, icon, detection heuristic, -- configuration values, etc.):
  • Team: Define risks
• Feedback mechanism(s)
  • Phabricator ticket(s)
  • Team discussion(s) (sync and async)
• Output
  • Patch demo

Step #2: Assess UX

• Purpose
  • Identify what – if any – issues (foundational and cosmetic) warrant being addressed before moving onto refinement
• Roles & Responsibilities
  • Everyone: try technical PoC; document feedback
  • Product: define what (if any) foundational issues warrant mitigation
  • Engineering: implement prioritized refinements
• Testing Environment
  • Patch demo
• Feedback mechanism(s)
  • Phabricator ticket(s)
  • Team discussion(s) (sync and async)
• Output
  • Prioritized tickets

Step #3: Finalize MVP

• Purpose
  • Implement all P0 fixes and refinements before inviting volunteer feedback
• Roles & Responsibilities
  • Editing Engineering: implement "further refinements"
  • Design + MoveComms + Product Ambassadors: review refinements + localize
  • Product: sign off
  • Editing QA + Product Analytics: verify UX and instrumentation
• Feedback mechanism(s)
  • Phabricator ticket(s)
  • Team discussion(s) (sync and async)
• Output
  • Fixes/refinements pushed to production mode and available in Suggestion Mode

External review

Step #4: Refine MVP in Production

• Purpose
  • Identify how (if at all) Suggestion is behaving in ways that could risk acting in ways that do not align with project policies and guidelines
• Roles & Responsibilities
  • MoveComms: make volunteers aware of availability of new suggestion
  • Volunteers:
    • Verify Suggestion is both functioning as expected, and promoting behavior that aligns with project policies, guidelines, and conventions
    • Propose improvements to bring Suggestion in closer alignment with volunteer/project expectations
  • Product: scope/prioritize improvements
  • Editing Engineering + Design: propose and implement improvements
• Testing Environment
  • Suggestion Mode via Beta Feature
• Feedback mechanism(s)
  • Phabricator ticket(s)
  • In-line feedback. See T401739.
  • Talk page discussion(s)
• Output
  • Fixes/refinements deployed

Step #5: Ship Suggestion to Newcomers

• Roles & Responsibilities
  • MoveComms:
    • Make volunteers aware of new suggestion deployment and where/how to monitor usage of it (e.g. edit tag)
    • Monitor feedback pages for issues/bug reports
  • Product:
    • Monitor Suggestion and editing funnel performance (via Superset dashboards)
    • Scope/prioritize improvements
• Testing Environment
  • Suggestion Mode (default-on)
• Feedback mechanism(s)
  • Quantitative data
  • In-line feedback. See T401739.

Done

• @ppelberg prepare initial proposal
  • See: Editing Scratch.
• Editing Team staff in the following roles review and offer feedback on the initial proposal:
  • Design
  • Engineering
  • MoveComms
  • Product ambassadors
  • Product analytics
• Product prioritizes and integrates feedback
• MoveComms publishes deployment path on-wiki and integrates stages into mw:Edit check/Deployment status
• @ldelench_wmf + @ppelberg figure out how to integrate process into phabricator