Document community outreach process for the mobile apps
Closed, ResolvedPublic
Actions

Description

What is the problem/what do you want to achieve?

Create a repeatable process for reaching out to community members for feedback, testing, etc

How can we help you?

Write up the steps for this process in a way that it can be applied to any apps project

What does success look like?

A page (probably on officewiki or mediawiki, whichever you think is best) that clearly lists the steps and includes links to related materials like the final version of this outreach template

What is your deadline?

This is important but not urgent, so sometime before the end of Q1 would be great

Event Timeline

LGoto created this task.May 18 2023, 10:08 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 18 2023, 10:08 PM

LGoto added projects: Wikipedia-iOS-App-Backlog, Wikipedia-Android-App-Backlog.May 18 2023, 10:09 PM

Aklapper renamed this task from Document community outreach process for the apps to Document community outreach process for the mobile apps.May 19 2023, 11:38 AM

@LGoto @JTannerWMF It sounds to me that some of what you are usually looking for is more on the user research side of things than on the community engagement one.
Can I have more details about what your processes re: the former look like?
I am convinced that at least part of what you want to achieve is actually better channeled through https://www.mediawiki.org/wiki/Wikimedia_Research/Design_Research#Support_for_WMF_teams .

• Elitre edited projects, added MoveComms-Support (Jul-Sep-2023); removed MoveComms-Support.May 22 2023, 5:00 PM

@Elitre Sorry this was unclear, this is specially for @ARamadan-WMF to write down what she has already been doing for the apps outreach, e.g. contacting users for testing. We would like to document the steps she has taken so that we can add or adjust steps in the future as needed.

Regarding Design Research, we checked in with Amal to let her know when outreach goes through design research vs her.

Example- Getting feedback on designs for usability testing (Design Research) vs. Telling the community we have new designs and welcome their feedback on our talk page (Amal) vs. Getting feedback about a prototype or occasionally a form in the app (Design/Product/Data)

This is absolutely great and TYSM for the above, truly helpful.

• Elitre assigned this task to ARamadan-WMF.May 23 2023, 9:34 AM

• Elitre triaged this task as Medium priority.

@JTannerWMF To clarify, if "Telling the community" means telling non-apps users/our desktop contributors, then I think that's uncontroversial. But Bethany's database, IIUC, should have the capability to target app users, which we don't have. Her team can set up micro surveys to ask or tell people things, which we can't. So I think for the Apps teams in particular, as opposed to maybe others, there's probably more margins for CRS and Design Research to actually do things together.

LGoto edited projects, added Wikipedia-Android-App-Backlog (Android Release - FY2023-24); removed Wikipedia-Android-App-Backlog.May 23 2023, 4:26 PM

LGoto moved this task from Epics in Progress to Ready for dev on the Wikipedia-Android-App-Backlog (Android Release - FY2023-24) board.

LGoto moved this task from Needs Triage to Product Backlog on the Wikipedia-iOS-App-Backlog board.May 23 2023, 6:28 PM

@JTannerWMF, A sheet was created with the full information about the process we can follow for the upcoming reaching out requests from here and also added to our 1:1 sheet.

ARamadan-WMF changed the task status from Open to In Progress.Jun 20 2023, 10:10 AM

Looks good to me

ARamadan-WMF closed this task as Resolved.Jul 18 2023, 2:08 PM

(Would these restricted sheets/docs benefit from being documented in some discoverable place outside of this Phabricator task?)

I will receive a confirmation on this sheet during the next week; then I will add it to a MediaWiki page and add the link here, too.

Document community outreach process for the mobile appsClosed, ResolvedPublicActions