After I meet with Claudia today, we'll wait until the request comes from the RDS process.
After that, Management will decide how to proceed.

This project was moved to the freezer and further conversations on how it will be followed up will be held this week (May 13 - 17)

Second week of conversations. (May 6 - 10)
a) We had conversations for KRs WE5.1, 5.2, 6.1, 6.2) with Tyler, Moriel, Matthew and Mateus about potential DR projects. The big takeaway is the first 6 months will be mainly focused on technical decisions and definition so we will be back with them at the beginning of Q2 for potential Q3 projects.
b) We still have a pending meeting with Slavina for WE6.3 (this is one with the most potential of Q1 contribution on this team.
c) We also had a second meeting with Jack Wheeler, and a potential project for the remainder of the quarter was suggested: evaluate how people understand & perceive the new intake form. This could be a quick test project and could strengthen the relation between both teams. It also allows the researcher to start onboarding on this new stage of the wishlist which is fairly new for everyone in the DR team.
d) We also met with Pau and picked, besides the projects already shared by Eli, we picked a second potential initiative for Q2, we will revisit at the beginning of Q1.
e) For next week, we have the after mentioned meeting with Slavina (WE6.3), Ilana and Masana (WE 1), a suggested by Rita meeting with Kirsten (WE 1. 2.3) and with Olga V. (WE3). This last 2 were not prioritized in the first iteration but might represent a good opportunity for impactful work.

Thanks so much for the feedback and suggestions.
As I mentioned at our meeting
a. We'll communicate this with the general Design Team on Tuesday so everyone is aware of the work we are doing and set the expectations.
b. After that, while I'm organizing the syllabus considering points A & B of your comment, we will open the call out to enlist and build a calendar of activities so everyone knows when and where the only live version of the training will happen.
c. For the factors in determining the need for a design researcher, let's evaluate this case by case but consider the classification we did for the User testing for Design Systems tool
In that sense, if it's a low-complexity project, we can support it through Research ops and consulting, but if it's middle or high, we might have a bigger participation.

After different conversations, this project will be pushed for Q1 or Q2 in FY2025.

First week of conversations. (April 29 - May 3)
a) We had conversations around the Wishlist with Sam Walton, Jack Wheeler and Joydeep Sengupta
b) On the MediaWiki side, we are waiting for the prioritization to the ideas presented.
c) Trust & Safety has yet to answer our invitation.
d) Contributor Experience already answered and we are going to review ideas and get back with comments and proposals.
e) Language exploratory conversation will happen Wednesday May 8.

Action plan.
For feedback and approval before April 29th.

For April 24th meeting, we have the following questions:
What does it means "being in charge of the narrative"? Also, how does this looks when talking about tasks and activities for this person in charge? What of the DR experience could be taken as good practice?
We might need to officialize the process that already exists or make it more straightforward.

A meeting set for the 24th, questions specific to this task:
What's the specific problem we are observing that needs to be addressed?
What's a realistic number of actions that could be done for Q4 FY 22324?

@cwylo Please add a provisional calendar for activities no later than Monday Apr 15th.
Thanks!

Meeting Nico after April 18th when he gets back from PTO.

Adding Claudia as a subscriber for context.
We are having a meeting on Monday, April 15th to define support steps.

The project has been closed and finished on our side.

Moving this project to staged as it was de-prioritized, but we might need to retake it in the future.

Extending the date to receive feedback until April 29th.

[Note for the research team]

[Note for the research team]

[Note for the Research team]

The new date to fully adopt this process is Feb, 28th, at the Research meeting.
That means the first collection of feedback from the Research team will start on the 14th, and will last a week.
Before the 14th we need observations from this group.
The process is divided in 2 main documents, please leave all the comments in one or both of those:

• Front Office, which will be the one we share with the team.
• Back Office, which we use as referential for management.

@leila & @XiaoXiao-WMF Please feel free to leave any comments or suggestions in there, I will be monitoring it regularly as the date gets closer.
Thanks for all the contributions in this process!

Merged and resolved task https://phabricator.wikimedia.org/T351745 to this one.

This is a carryover project from the Q2 objectives.
What was achieved:

• Usability Tests in Arabic and English Wikipedias

Collecting all consultancy done as of this week.

This is a carryover project from the Q2 objectives.
What was achieved:

• List Item

This is a carryover project from the Q2 objectives.
What was achieved:

• Usability Tests in Arabic and English Wikipedias

What's left to do:

• Analysis and Synthesis

Claudia, here you'll find a little more information about the project. I already set a 30-minute conversation with Constanza and Kat on Thursday.

Are you referring to the sample slide deck?

Let's go through the second option.

Great to hear we are closer to making it stable.
(On the questions left) The big missing question is: What Criteria do we want to communicate? In our meeting we talked about Impact and how it connects with our Mission and resources, are there any other elements we should consider? (note: in this case, criteria includes things they should develop to propose the projects, such as methodology and expected impact, but also, things that we might need to review, such as clarity, connection to our mission, to our audiences)
We might also need to define a cycle, do we want this process to be applied every year (to match the App) or do we want it to happen every six months? My understanding from the conversations is we are going to keep it as a year-round effort.

Hey, @Katherine.gatewood I'm setting a meeting with you next week to talk a little bit more about the scope and the expectations on this work, specifically:
a) What type of deliverable you need
b) Some clarification on concepts on the docs shared.

@Bethany When done, please let me know, thanks!