 Hello, everyone. I am Carol Dunn. I am vice president of product management here at the Wikimedia Foundation, and I'm really happy to be with you all at Wikimedia today. I'm going to be presenting the product platform strategy with a few of my colleagues. To start off with, I'll go ahead and review the agenda with you so you know what we're going to cover today. The first one, the first item is why we have a product platform strategy. The second is a little bit of context around it. We'll go through the strategic plans and rationale and then pilots and pilot examples, and then we'll have a little bit of time for Q&A at the end. So as we go through the presentation, if you have questions, go ahead and write them down and we will cover as many as we can at the end of the presentation. First of all, why do we have a product platform at the Wikimedia Foundation? It also creates alignment with the communities through the movement strategy. So some people like to know where we're going, get to the point at the beginning so they're not sitting here waiting for the punchline and then walk through the rationale. Other people often want to just take a step by step rush through the story and hear the end at the end. I'm actually sharing a little bit of the end here at the beginning so you know where we're headed. The core of our strategy is systems of empowerment, working with communities around the world to understand their needs, how to support growth at the local level. We will have movement growth through systems of empowerment. The vision asks us of this, but I don't think we've ever been really explicit about it. We don't want to just chase numbers. We want to grow in an equitable way, a way that lives up to our vision and truly supports the sum of all knowledge. It means bringing our values to bear in our strategy and working with global communities to grow. So what does systems of empowerment mean? It means we're focused on contributors in emerging markets. By contributors, we mean content creators, curators, functionaries, developers, community organizers. We will build with them, not for them. So let me give you a little bit of background and context for how we arrived at the strategy. There are two main things I want to review here in context. The first is the product flywheel and the second is global population growth and engagement with our movement. So let's go through the flywheel first. This is the product flywheel. It's essentially our business model. It's our engagement model. It's how people engage on the platform. It's a virtuous cycle where editors and contributors create content. Content brings in readers, readers create editors, and the cycle of life, the cycle of free knowledge on the Wikimedia projects continues. We need to generate awareness to bring people into the flywheel and employ advocacy to make sure the conditions for free knowledge exist globally. So keep this flywheel in mind. This is the essence of how engagement across all of our projects work. We believe the flywheel is working. This chart shows growth from the fiscal year 2021 numbers, pandemic notwithstanding are at all time highs. The first row shows our current monthly health numbers and the second shows the increase over the last five years. I'll let you look through this for a minute and just absorb how much we've grown just over the last five years. So now I want to talk through some high level data and let's talk about people, the population numbers and engagement numbers across our Wikimedia projects. So this is a combination of data from the World Bank and internal research and statistics. It's actually from the previous fiscal year so the numbers are even greater right now so they're not exactly true to the current numbers. So it's not totally literally at this point, it's meant to illustrate a point. So reading the chart from left to right, there's slightly over 7 billion people in the world about half are connected to the internet. Based on movement strategy research, we believe that 1.5 billion know about Wikimedia and about a billion use the product. It's a little bit over that now and that's based on a unique device counts. Right now we reach about one in seven people on the planet with a much smaller percentage of editors. So let's take these high level numbers and break them down by regions. So this is where we are by regions. You could see our impact is not consistent around the world. So we've broken out the data from the last slide into two different categories. There are established regions and emerging regions. Let me give you the definition of these so you know exactly where we're talking about. For the established regions, we're talking about the United States, Canada, Europe and Japan. The emerging regions are where Wikimedia projects in the movement is less well known and we don't have as much engagement across all of the other countries in the world. I won't name them all obviously. So those are the two rows that you see here, the established regions and the emerging regions. Countries that are in this emerging region bucket constitute about 85% of the world, but you can see it's a much smaller percentage of Wikimedia readers and editors. Our current focus is people with internet access who aren't using Wikimedia properties. In 2018 we decided to focus on online readers and partner on offline due to the large number of online readers in emerging markets that didn't use Wikipedia. The offline segment is important, but we've partnered with Qwix for providing free knowledge to the offline segments. So let's take these numbers and think about what this might look like today. If we had the same percentage of use in emerging markets as we do in established markets, we would have hundreds of millions more readers and double the number of editors. So let's look at 2030. We know that by 2030 we want to become the essential infrastructure of free knowledge. In the future, this opportunity is even more compelling. So in 2030, according to the World Bank, the population in emerging regions will grow while established regions will shrink. If people around the world used Wikipedia at the same rate that people in established markets do today, we could have more than 4 billion readers and a million editors. Now, before we get too excited, this is probably an upper bound and we in the product department like our numbers, but there are other reasons to look towards emerging regions for the future growth of Wikimedia projects. If we are truly going to represent the sum of all knowledge, everybody on the planet needs to be able to participate. But I would like us to take a second and imagine how much good we could do in the world with a platform that reaches 4 billion people who believe in free knowledge. So you can see that the numbers are there for focusing on emerging markets, as well as the values alignments with our mission for free knowledge. So let's talk through strategic plans and rationale. What are the plans? How are we going to get there? I'm showing you this. I know you're all very familiar with this sentence. By 2030, Wikimedia will become the essential infrastructure of free knowledge. And anyone who shares our vision will be able to join us with knowledge equity and knowledge of service being two pillars. Any product platform strategy that we create must sit under the umbrella of the movement strategy. This is inspirational and aspirational direction in movement strategy. It's still a little abstract, though. So we took the liberty of describing the in-state. We wanted to tell you a story of what the world could look like in 2030. The year is 2030. Our movement is thriving. We have more women and people from all languages and cultures sharing knowledge throughout the ecosystem. Wikimedia is synonymous with free knowledge everywhere. Free knowledge connects people around the world. On the right-hand side, you see different sentences for different groups of people. And this is once again the in-state. Imagine a world in which people all over the world think of Wikipedia when they need information. Volunteers around the world can find areas of interest where they want to contribute and can. Movement organizers can connect with the community and activate campaigns. Teachers use Wikipedia in their classroom to teach subject matter and digital literacy. Affiliate organizations can build new futures and experiences that map to their needs and align with the mission and technical systems. Cultural and scientific institutes can share their content with us and it's flowing through the Internet. Third-party content re-users depend on us for high-quality content. Sounds like a great world to live in, right? This is our vision for how people can participate in free knowledge on a movement and on our platform. So how are we going to get there? Let's move into specifics. This is a three-step plan to meet the opportunity that we've described. This is how we get to that in-state. Step one is to make our creation and curation experiences more usable and welcoming for new contributors in emerging markets and provide movement organizers with the tools to recruit new community members. This is systems of empowerment. We will build with communities to create systems that they need and that will promote local growth. Step two, we collaborate with these new contributors around the planet and existing contributors to create innovative, diverse experiences that better serve the needs of new knowledge consumers. And step three, remember the product flywheel we talked about? We globalize this product flywheel. We ensure our content is accessible on all digital platforms and knowledge creators and institutions can utilize our ecosystem. Now we're going to look at the plan from a couple of different angles to add a little bit more detail and perspective. The first angle we're going to look at it from is participants, the who. Who are we really talking about with each of these steps? So we see the focus on different participants change over time. In the first step, build systems of empowerment, you see the focus is on contributors, both existing and new. The second step, amplify the impact of our content, the focus is more on the consumers. So what net new content experiences do we need to support in order to reach a more global market, more global population, more global movement, more people out there in the world, both youth and people in emerging markets. Step three, we're really focused on bringing in and expanding that flywheel, more institutions, universities, et cetera, can participate in the movement as part of the flywheel. And you can find our content on other platforms as well as on our own platform. The next angle we're going to look at this from is, sorry, wrong slide, is, nope, there we go. So another way to examine the three step plan is an implementation, how we would execute the plan. So we foresee implementation of the plan in three stages, roughly corresponding to three year time periods. Note that there is some overlap where appropriate. Well, we will find it necessary to pull forward some investments in the future stages in order to prime the pump for their success. This can be done without impacting the strategic focus of each stage. So in the first stage, we focus on communities through systems of empowerment, but we're pulling forward a little bit of the amplify the impact of our content. So experimenting with net new form factors, new ways to experience content. And we're also pulling forward a little bit of globalize the flywheel. You've seen this through Wikimedia Enterprise. So let's get into some specifics. It's always good for me to see examples of what we're talking about in each stage. So stage one, as we focus on working with communities to create systems of empowerment, you can see a couple of examples here. New editor experiences make the projects well more welcoming to newcomers campaigns. This is really supporting movement organizers and creating the tools and systems they need in order to grow locally. And we'll talk about that later on in the presentation. There's research on moderator tools. There's research on templates and gadgets, which I'm sure many of you are excited to hear about. I will pull we are pulling forward a little bit of amplify the content. So examples of that are wiki stories and research on video. I won't read all of these example projects to you but all of these this is not a roadmap. This is meant to illustrate what types of projects might fall under each of these stages, as well as how we might pull some forward and how you can see here and you know this green line systems of empowerment. It continues throughout the cycle of this strategic plan. So let's talk about operationalizing the strategy. I'm going to hand the talking stick over to my colleague Amanda Bittaker and thank you for your time. Amanda. Hi everyone. My name is Amanda Bittaker lead program manager in the product department at the foundation. So how do we begin implementing the strategy. If the strategy is a map with directions to get to the essential infrastructure. We need to get the car started. We need to make the turns we want. We need to make sure we're heading in the right direction. In other words, we need to operationalize the strategy, make it reality. I'm helping our team teams across the foundation do that and want to tell you a little bit about it. So in starting to implement the strategy, we are guided by the following principles. We want to ensure our products have the highest impact possible across the movement. Learn as quickly as possible what most empowers contributors and be flexible if new opportunities arise. So in order to do this, our new work for this fiscal year will start with four pilot programs. We want a handful of teams to test out a series of hypotheses working with multiple communities to try multiple growth vectors and see which will be most successful in which places. These are experimental meant to learn quickly and adapt quickly to the things we learn. They're techno social and that we're aligning technical and non technical stakeholders, including Wikimedia foundation teams volunteers movement partners. To work together towards the same deliverables. And each of them focuses on our strategic impact to empower our community members to grow participation in our movement. Each of the pilot projects are in a different stage of maturity and understanding of their problem sets. So newcomer experience is building on solid foundation of hypotheses tested over the last two years on how to support folks making their first edits. Research on moderator tools is just starting. We know we want to support moderators and growing Wikis, especially when they have an influx of new editors and new content, but we don't know how yet what the best method might be. We're just starting to explore how to do that. To tell you more about our pilot work for this fiscal year, I am delighted to introduce Alana, the product manager for the campaigns pilot. Alana, welcome. Please take it away. Hello, everyone. My name is Alana freed, and I'm very excited to tell you about the new campaigns team at the Wikimedia foundation. Since I only have a few minutes today, I'll share some basic information. But to learn more, you can check out our project page on Meadowiki. Visit our help desk at Wikimedia on Tuesday or join our team office hours on September 2 at 15 UTC. So first, who are we? We're a product development team focused on building and improving tools for campaign organizers and participants. So in other words, we'll be supporting Wikimedia campaigns like wiki loves monuments wiki wiki gap wikipedia Asian month one live one breath and more. Our goal is to make it easier to be an effective and impactful campaign organizer, whether someone is very experienced or a brand new organizer. So you may be thinking, aren't there already teams at the foundation that support campaigns? Yes, there are teams that provide training and grant funding to organizers. Our team is different because we're a software development team. This means we'll be building features and tools for campaign organizers. And the organizers will be able to use these features in whatever way they think will deliver the biggest impact. Next slide please. So now I want to take a step back and talk about why we're focusing on campaigns. As a team, we believe that campaigns play an incredibly important role in the movement. They recruit organizers and new editors, help fill knowledge gaps and produce new content. They also bring communities together. Campaigns are collaborative and fun, and people can come together around topics or contribution types they care about. The driving engine behind campaigns is the campaign organizer. They work within their communities and contexts to develop meaningful events. And they build communities from the ground up, both in person and on wiki. For this reason, we believe that if we empower campaign organizers, we empower the movement as a whole. Next slide please. As our first project, we'll be building a registration solution. Right now, there is no easy way on wiki to join campaign events. This means that organizers often turn to manually created solutions on wiki, which can be difficult for newcomers to access and understand, or off wiki registration solutions, which may be in conflict with wikimedia values and are not integrated with existing wikimedia workflows. In the image on this slide, you can see the screenshot of some of the registration systems that are currently used. It's a bit of a mess at the moment. Overall, the situation makes it hard for organizers to do their job. It's difficult to track who is coming to events and what participants need to be supported. It also adds unnecessary complexity for organizers and to subpar user experience for participants. So we want to fix this problem. Next slide please. So what's our vision for this new registration solution? Our vision is to merge the best of both worlds from on wiki and off wiki solutions. So much like this cat and dog playing together, which is a photo added to Commons through the wiki loves Africa campaign, we'll get an improved experience through merging two different approaches. From the on wiki system, we want to keep the fact that registration is on wiki and that everyone can see who joined the event. From the off wiki systems, we want to take the ease of use. So it's simple to configure and fill out forms. And then we want to add a new level of support integration with tracking tools. This way, when someone registers for an event, their username can be automatically pushed to the organizers tracking tool of choice, such as event metrics or the programs and events dashboard. In total, this all goes back to our big vision. We want to empower organizers so it's easier for them to run impactful and effective campaigns. Next slide please. We're really excited about registration, but that's not all. We see registration as the first step in a much larger effort to support organizers through our team's work. So after we build a registration solution, there are many more projects we may choose to do next, such as creating an organizer center. So all organizers can easily learn about the resources and tools available to them, improve tools to build article lists or work lists, making it easier to promote events and communicate with participants, new ways to onboard and support newcomers and campaigns, better tools for tracking and analytics, and easier ways to report impact to campaign stakeholders. Overall, we have a lot of plans and registration is just the first step in making it possible. Next slide please. The last point I would like to make is that we want our work to be deeply collaborative. Before launching our project, we talked to about 50 campaign organizers to learn about their experiences and needs. These conversations from the backbone of our team's vision and the direction of our first project. So I would like to thank them for their support. We've already learned so much from all of you. Now I would like to invite everyone to share their feedback on our project talk page, whether you're a campaign organizer or participant, or if you're a passionate Wikimedia and whose ideas and how to improve campaigns we want to hear from you. So please check out our project page. You can join your email list as well, where we'll be providing status updates. And finally, you can chat with us in real time. We'll be hosting a help desk table on Tuesday, August 17th from 1430 to 16 UTC. And we'll also be hosting team office hours on September 2nd at 15 UTC. So please reach out, share your opinions and join us in the journey to improve the campaign experience. Thank you all so much for listening to me. And now we'll open up the session to questions, which Margie will lead and we'll all come back on stage. So now Margie and everyone. Hi everyone. Thank you for joining us on the session. Now it's your turn to talk and we'd like to hear from you. I'm going to be pulling questions and comments from the remote feed. But I'd like to just give you a couple of questions to think about as we begin the interactive part of this session. So after hearing this presentation, what advantages or disadvantages do you feel the strategy has? What could be improved? What do you see as its strengths or weaknesses? What needs in the movement does this strategy address? And what obstacles will it face in the movement or in the free knowledge ecosystem? Give those questions some thought and please chime in on Rimo and we will see your questions and I will field them to the panel here. We're going to start with a couple of questions that have already come in and Carol, the first question is for you. From Jan Einali. If we want to become the infrastructure for free knowledge, what outreachs to our friends and ecosystem that we have to do, for example, to open street map? Will we offer to run the servers for them, for example? Yeah, that's a great question. That question sounds to me like it's directed towards the globalized the flywheel step kind of in that 10-year plan. It's the focus towards the end of that. But as we talked about in the slide where we're pulling things forward, we already participate in partnerships with a lot of different institutions. We have really strong Glam partnerships across the globe, as well as other types of platform partnerships. So I would not speak to specifics around running servers for different institutions. It might be a possibility, but we don't have specific plans for how to address that at this point because that is further along in the plan. That step three is globalizing the flywheel. Thanks, Carol. Question two is also for you. There was a comment that said a video in four years. I guess I'll take it, but that seems very late. Do you have thoughts about that? Yeah, I do. I agree. There's a Chinese proverb that my family often quotes, which says, when is the best time to plant a tree 40 years ago? When's the second best time right now? If you don't already have the tree from the past, we have to get started now. So video is a really complex type of content for us. And I'll just bring up a couple of reasons. We could talk about video for hours and hours. I've no doubt. But a couple of thoughts I will leave you with. One is we do know that video is a very common way for people around the world of all ages in all regions to consume content. It is becoming more and more popular, short form video. I personally have two 18-year-olds. Short form video, I think is how they learn everything now. So it's a really interesting phenomenon globally. So yes, it is important. When you think about the values of our communities and our collaboration on content, imagine that with video. It is a complex problem set, right? How do you actually collaborate in a Wikimedia way on video content? There are other questions around hosting video, delivering video. What are the technical capabilities that we will need to be able to do to serve our customers, users, people in the community, people who consume the content, people of the world? What capabilities do we need to have from a technical perspective? So those are all questions we are working on figuring out right now. Great. Thank you. Let's see. This is from Dumasani. Are there specific indicators developed for this? Are there indicators developed for this strategy? And where can I find these? And it's okay if these are still being developed. Yeah, it's a great question. And thank you for that question. So currently, we don't have kind of overarching global metrics. The approach we are taking here is, you know, Amanda went through the four different pilot projects with you all. And each of those projects is working with different communities to figure out how do we measure and understand equitable growth across all of those projects. So from project to project, it might look a little bit different. I do want us to get to a place where we can have some common metrics and understand globally how we're growing and what that looks like. But I wanted to come from the work with the communities. And I don't want it to come sort of from top down, so to speak. So that is our approach. Each of those pilots has their metrics that they are working with the communities. Okay. I think the next question is for Alana. The question is, what is the join our notifications list link? So I initially called an email list link and then I realized that wasn't totally accurate because it's mass message. So it's a mass message list. But that is the list that if you sign up, we'll be sending you along with the other people in the list a mass message about status updates for our project or other projects to be working on in the future. Great. Thank you. Okay. So the next question is either for Carol or Amanda. I don't know who wants to take it. Let's see. The question is, we in DR Congo would be happy to test this. What to do? I'm not sure which this is. My strategy or assume I mean engagement with the being one of the communities to engage with. Yes. We would love that. Please reach out. Hit me up on my user page. Send me an email. Our email addresses are in the slides. Yeah. Those sorts of connections are one of the best parts of the convenience of things. Definitely. Alana, did you want to chime in on that? Sure. And if it's regarding the registration solution, we're a new team. So we are no planning to build it out. But when it is available, we want as many people as possible to be able to use it. So we'll be sharing status updates on things like early buyer frames so we can get feedback on what people think. And then we'll have a testable version that people can try out. And then when it's live, it's not going to be the be all end all we'll want to iterate and prove over time. So we'll want feedback. So yes, please join us. The best way to find out about how you can get involved is going on a meta talk page or the meta project page. Thank you. Kind of a related question maybe for Alana. Do you plan to develop new campaign tools? Aren't there tons of campaign tools available out there? Yes. So there already are a lot of tools out there. So that's why one of the requests we heard that I also highlighted in one of our ideas is building an organizer center. Where people can find out about the tools available to them. So for some organizers, their problems are, I don't have the tools I need. For others, maybe I actually have the tools I need, but it took me a really long time to find them. It's a lot of work to train new folks and how to use them. So we want to bring these two kind of pain points together and organize our center. And so for one function of the organizer center, it'll be about discovery and mentorship and training around tools. And then the other may also feature new tools to build over time or improvements to existing tools. Because also regarding existing tools, some of them have worked for a while, but they might need some improvements or they may have some lags and maintenance. And then there's others that don't serve the needs for certain types of campaigns or certain kinds of organizers. So we really want to dig into that space and see how we can improve the ecosystem overall. That's great. There's kind of a related question from Ngozi Asadebi that says, the strategies need to take notice of the different situations for different campaign organizers. Do you have a thought about that? Yeah. So that was one of the reasons I talked to the 50 campaign organizers before launching the project. As I already knew there were different types of campaigns, but it's one thing for me to just instinctively know it. It's another for me to talk to a bunch of people. So I talked to organizers who work on very small campaigns. I talked to organizers who work on these global meta campaigns where they're kind of regional or country related organizers. And then it goes up to the talk to global organizers. I talked to people who do photography campaigns who do editathons. There are so many different campaign types. We know that because there are so many different campaign types, we want to try to build thinking about this larger ecosystem rather than one specific campaign. We're going to have to learn over time. I'm sure even in the 50 organizers I talked to, we didn't cover everything, but we are really going to try to do our best to bring in folks. And that's why it's important to us to have things like office hours and a lot of conversation, the talk page and the help desk that we're going to have with the media is we really want to talk to everyone. So please share. If you see the talk page or on the project page that the kind of campaigns you're interested in or you run represented yet, please share and let us know because we want that included. Let's see. This is also, I think, for you, Ilana, where can we sign up for updates on the registration program? Yeah, I think there are two places or two ways to get updates. First is our project page. If you add it to your watch list, you'll be able to see updates that way. Or you can sign up for our notifications list. So you'll get a mass message to your talk page for when we post updates. Great. So there's someone in the chat is asking how we can add persons with disabilities, especially deaf people, because I'm a professional sign language interpreter. I don't know if that's a question to the production crew here or a general question to the panel. But maybe we can speak about it in context of our strategy. Yeah. While we wait for your clarity, we can address accessibility in the product strategy. And actually, I'm going to hand it back to you here in a minute, Margie, because I think as our lead for user experience and research design, I think you are well qualified to speak to this. But I will say to start with that, we are considering people with disabilities and accessibility as a key component of the audience that we would be addressing for this strategy as well. When we think about the sum of the knowledge, this does include everyone, no matter what their abilities are. So in terms of how to actually execute on this, I will hand this over to Margie. Yeah. So a related strategy that we've been working on, which we will be talking about later in Wikipedia, is trying to figure out a way to create more inclusive product development. So how to improve our processes at the foundation so that we are being more inclusive of all the potential users that could be on our platform that maybe are not able to be served adequately now. So a big piece of that effort is going to be about, for example, setting really clear accessibility goals early on in a project. So currently we don't have specific accessibility goals. We follow general accessibility guidelines. But team by team, we are not setting explicit goals. That's one of the promises that we're planning to commit to as we roll this more inclusive product development process forward. The other kinds of things we'll be doing are things like explicitly testing with specific populations with specific types of disabilities. So as we set our accessibility goals, we will be making sure that we're testing with the folks that we're trying to reach. And then kind of a different form of accessibility. We also need to make sure that whatever community that we're trying to reach, that we're really understanding what typical internet performance is in these areas and being better about doing Q&A testing to make sure that our performance is actually a good experience given the kind of the technical context that people will be consuming your content in. Let's see. This seems to be a question for Carol. Will we move from strategic plan to action plan to resource loaded action plan with metrics? Yes. And I love the phrasing of the question. Resource loaded. So yeah, you could see in the presentation itself, we've walked you through kind of different levels of the strategy. We have a high level, three step, ten year strategic plan to get to the 2030 vision, we broke that down into how we school things forward a little bit, gave example projects. Amanda took you through the four pilots that are actually part of the annual plan for this year. And then we took you through a very specific example with the Launa's team on campaigns and the plans there. And so the way that the strategy is embodied, fleshed out, resource loaded, to use your phrase, in the annual plan. You can actually see that in the annual plan. That was published about a month ago, I think, is when we actually put the annual plan out on VETA. So you can actually see those connections there. You'll see campaigns in that plan. You will see newcomer experience in that plan. You will see Wiki stories in that plan. You'll see moderator tools in that plan. So those are the specific ways that we are allocating resource towards executing on the strategy. Great. And the next question is for Launa, I think we just need a reminder for where the link is for signing into the campaign page. Yes. So on our team page, if you go to our team page where the foundation product team for campaigns, and then you just go backslash subscribers, and you'll be able to see the sign up list also in the ether pad. If you can access it, there are links in the ether pad to that. Thank you. Okay. Looks like we worked through the questions from Rimo. Last anybody else has any last minute questions? Or any of the panelists have last minute comments? I'll have a quick comment while people are thinking if they have any remaining questions. We very much want your feedback on the strategy. We put up a meta page that describes the strategic narrative that you heard today. We have opportunities for question and answer here, of course. And depending on the activity on the meta page, we can hold office hours moving forward as well. Once again, I do love the question of how do we actually think about making this strategy real? How do we allocate resources towards it? How do we actually create a bigger impact in the world? And so that very much is the connection between the product platform strategy and the annual plan we published last year, the plan you'll see next year, et cetera. We very much want to see this realized over the next nine and a half years as we get to the 2030 movement strategy vision. So please come to the meta page. Sorry. One more question looks like has come in. So how will moderating tools impact the existing administrative tools? That's a great question. The moderator tools work right now. It's in a research stage. If you remember how Amanda was describing how each of the different pilots is in a different stage of maturity, essentially, the moderator tools is in the very beginning stage, which means understanding. What's our methodology of understanding is talking to a lot of different people around the world for understanding what their needs are. And so, you know, my quick question, my quick answer is I don't know yet because we're doing research. I don't anticipate us changing necessarily what exists in the more established communities. This is really about how do we make sure that as we add new people and new content to the smaller and medium sized wikis, how do we make sure that we don't overload the system? How do we make sure that we don't create vectorish hervandalism? How do we make sure that the small number of administrators and moderators on those sites don't become overwhelmed by the new content and new people, new people who don't know the processes, procedures, norms, et cetera, of that community? So that's what we are working to understand right now is what kind of support we can help develop and build out for the smaller and medium wikis in research stage. Okay, so I have another question. If I read your flyable model right, the main way in is through content awareness and consumption. Campaigns, on the other hand, often target content creation. Is there more we could do on these early steps or do we feel that content awareness and accessibility are already largely solved? I love the question because it shows you are thinking about the flywheel and understand the relationship between all of those components. I would say that the word solved is probably never going to be used in this kind of context. So what I mean by that is there is always optimization at each of those stages that you could do, that we could do together. Part of the value of having a product platform strategy is that it allows us to focus. You can't boil the ocean. We can't do everything all at once. We do have to create focus for the teams to really collaborate together and work through specific problem sets. Over time, as you can see in the three-step plan, we actually move along the flywheel a little bit. So initially that first step is focusing on contributors. And if you think about, you know, you're asking for sort of these early stages, if you think about the relationship between, let's say, campaign and newcomer experience, there actually is a lot they can do together once they understand their own individual areas better and build out tools and systems and experiences that help people achieve success in those areas. New newcomer experience is something that campaigns could funnel people into. So there is a lot of optimization we can do in this sort of newcomer area. Campaigns is one way in, content awareness is one way in. We could always optimize around the circle. Amanda, did you want to comment on that? Yeah, if I may. I just wanted to say, as part of the New Readers program a couple of years ago, we did a lot of awareness campaigns. We did marketing. We did some rapid grants with outreach stuff. And we did find that people came, came to Wikipedia, but they didn't stay. And one of our hypotheses around that was that they didn't stay because we didn't have the content that they wanted in their language. And so one of the things we're doing now is to see if we can create more content in both languages that they want to read if we can make that connection around the flywheel. Yeah, and I'll build off of that a little bit as well. When we think about the content that people want to experience, the Wikimedia Foundation does not create the content as we know, right? It is the volunteer contributors around the world. This is why we are focused on contributors in these different emerging communities. We want to understand what tools, systems, capabilities, resources they need in order to grow the content and community locally, because then the consumers locally would have the content locally, right? So we really are focused on creators, contributors, organizers working locally in these emerging communities. I also have one quick note about campaigns. Some campaigns are more heavily focused on content generation, especially those that target experienced editors, but there are also many campaigns that target newcomers. And those campaigns will, for example, a classic example being edited that has a lot of the days focused on really a training to introduce Wikimedia in terms of its principles and values and what it is as a movement. And so it's sort of like a combination of both an editing event and an awareness event. And those two really go hand in hand and they help bring on new people who might not otherwise join. So that's something to also, I think, take into account with campaigns. Great. Well, it looks like we are at the end of our questions. Thank you all for your participation and for your attendance. And we look forward to seeing further comments on the product platform strategy meta page. Thank you all. Thank you everybody.