Leila - since this is a new significant Essential work project - would like to get your approval and input on it.

I propose that we have Bethany share a draft proposal with you, once she has drafted goals & project outline to give this project some further definition. Here's what I've said so far: (1) we should define success criteria for the knowledge repo, and that "number of visits" to it should likely be part of that. (2) Taking a Jobs-To-Be-Done approach could be useful to guide our work in improving it: to define both the jobs to be done that the current knowledge repo supports and assess where the gaps are in those jobs being easy to do, as well as what are the jobs that it could support, that would be useful to support. E.g. "as a new project manager working on a new topic for which a synthesis does not already exist, I want to know what research we've done on this topic before, and what they key insights are".

Thinking about whether it'd be more useful for the knowledge repo to also include research from Applied Science, and external research, is something to consider.

We want to also think about the role that AI can play, since there are many AI-powered research repository tools out there now - and want to experiment with some of these tools as part of broader team experimentation with AI tools for research, this quarter.

Reviewing a draft proposal by Bethany sounds good to me. Thank you.

Some considerations on my end:

• I need to see the proposal for making the call on prioritization. My suggestion is that this task be scoped for preparing the proposal and having scoping completed in Q3 for the purpose of prioritization. If the work is prioritized, you can always add a task to start work in Q3.

• This idea has overlap with another idea we have talked about "state of research for (a subset of) readers" and a similar document for "(one or more subsets of) editors" so there is opportunity for synergy.

• It is important to have a strong reason for focusing the work on Design Research findings only. The majority of the questions I hear PMs or group PMs ask needs response rooted in research (independent of whether that research is done inside WMF or outside, and independent of the methods but focused on rigorous hypothesis building or findings).

Looking forward to seeing the proposal.

Ideating and researching ideas this week.

Thanks Leila - updated the task and due date to scope it to preparing the proposal.

Week of Jan 12:

• reading on best practices within the industry, knowledge management systems, tooling options, management options, etc
• conversations with Daisy, Sonja, and arranged conversations with Justin and UX at Mozilla

Week of Jan 19:

• More reading, learning, experimentation with software we already have access to
• Conversation with UX Research at Mozilla

Week of Jan 26:

• Conversations with UXR from Khan Academy, Justin, and Leila
• Wrote draft proposal

Finished proposal (private link) and shared with Debra for feedback. Revised based on feedback

• Discussed proposal with Debra
• Set up meeting to discuss with Leila
• Researched software solutions

Presented proposal to Leila and Debra. Decided on 10% of essential work over 3 months to improve the design research knowledge repo. LZ decided against pursuing a larger knowledge management system or knowledge services at this time given the current priorities.

Closing out this task.