Problem - we do not have much (if any) writings about how the Community Liaison (CL) team has advised and worked with product teams and communities under different scenarios. A lack of documentation means there is nothing solid we can point others to in for reference when helping teams without CL support, to back up our higher-level documents like the Technical Collaboration Guidance (TCG).

Solution - We document cases of collaboration between WMF product teams and communities. These documents would have value as reference for Technical Collaboration projects, and would potentially inform future decision-making. With enough collected wisdom, it might be possible to generate some general strategy documents for community engagement around product development, which do not formally exist at this time.

The format should be a form-format wikipage. Elements could include:

• listing stakeholders
• timeframes (goal and actual)
• the vision for the purpose of collaboration
• the expected tangible outcome
• the strategy
• the actual outcome
• lessons learning/things that could have been done differently
• what did work

The /Case page will index the cases with a light summary, with cases being a subpage. The project can live under the CLs' main page, the TC team main page, or the TCG main page. Bikeshedding can occur later.

The project will start with ORES and go forward from there. The CL team may choose to retrospectively write up cases from the past four years, but there is no consideration for that built into this project. If it happens organically, that will be great.

This task can be closed once the /Case page is up and running with the initial ORES TCG review.