Reading/Strategy/Strategy Process/Possibilities


 * For every possibility, according to the process, we need to generate strategy cascades as follows:


 * Amazing mobile lookup experience (fast, accurate) for mass market in global north.
 * Optimize experience for users coming from specific referrers (eg. Google, etc)
 * Make a kick ass long form reading experience.
 * Restructure display to focus on media.
 * Strengthen dev advocacy to engage U/X + developer experts to improve reading UX.
 * Enable readers to share content to read inside and outside Wikis
 * Stop focusing on search and emphasize discovery/browsing in UI.
 * Leverage communities to organize related content to create deep-dive educational experience.
 * Create new reading experience tailored for users in the global south.

*Project agnostic:
 * Set of pre-built content for embedding existing Wikimedia content.
 * Grant rich/deep access to inform - platform/tools beyond scope of general reference.
 * WMF-as-a-service: spin WP into its own entity and all/any projects become customers of the service.
 * WMF encourages an ecosystem of frontend experimentation.
 * WMF supports 3rd party dev/design of WMF incubated projects.

1.Become THE broker of open access data, targeting specific channel partners.

2.Messaging apps/platforms.

3.Media companies

4.Platform companies

5.Specific verticals (eg. medical specific wikis)

6.Including the existing communities

7.The more data we broker, the more durable


 * For every possibility, according to the process, we need to generate strategy cascades.

For the possibility of Set of pre-built content for embedding existing Wikimedia content. cascades were as follows:

1.

2.