Design System Team/OKRs/FY22-23/Q4

Motivation

Our assumption is that Codex in its current state, even with its limitations and workarounds, is in many cases so much better than the alternative (from a design and development perspective) that there will still be a desire to adopt. Growth and Abstract Wikipedia represent this well, and we want to bring more teams like them onboard. Our hypothesis this quarter is that we can drive adoption through increasing awareness. We need to move quickly to test this, while also working towards unblocking known barriers preventing certain teams from leveraging the benefits of Codex today.

Format

Objective: One-sentence goal we want to achieve in the quarter (not a metric).

Key Results: Measurable metrics we believe accurately reflect progress against the objective.

Activities: The things we believe we can do to try to achieve the key results. These will more or less translate into “roadmap” items.

OKRs

Objective	Key Results	Activities
Increase WMF + WMDE awareness of DST and Codex*.	80% of product designers and tech leads report feeling confident in their ability to evaluate whether or not Codex is a good fit for their next feature. 80% of product designers and tech leads report they understand how to engage with and get support from DST. 80% of product designers and tech leads report they have the skills and resources needed to develop a feature using Figma, Vue, and Codex. 80% of product managers report that they understand why and how they should make room for Codex adoption in their roadmaps.	Set up surveys to measure progress towards awareness KRs. Driving Codex awareness in department meetings, mailing lists, blogs, and presence at the Wikimedia Hackathon and Wishathon. Establishing the first step in making Codex the design system for Wikimedia. Preparing good examples of Codex usage and adoption paths. Outline a clear collaboration process and level(s) of support DST can provide. Create a process for triaging requests from other teams. Establish and make public a product strategy and roadmap. Map out the requirements for a “1.0” release of Codex. Set up DST “Office Hours”.
Support increased WMF + WMDE adoption of Codex.	2 net-new teams have committed to or have built a feature using Codex. 4 new features have been committed to be or have been built using Codex.	Core component development (prioritized by requests from customer teams). Design explorations, design and code audits, pair programming, etc. Enable use of CSS-only components in MediaWiki.
Make progress against known hurdles to future adoption.	We have identified and validated one solution that would enable teams to use Codex when there are requirements (e.g. performance, equity, SEO) that are not currently served by client-side only implementations.	Leverage Codex CSS-only components in a production feature. Consult with the Architecture team on a technical strategy to address the KR.

* KRs Measured through surveys to select WMF + WMDE teams at the beginning, midpoint, and end of the quarter.