Growth/Engage with the Growth team

Share your experience
Please post on the team’s talk page or the talk pages for our projects! We want to hear about what is working and what is not working. We also want to hear any reactions, questions, or opinions on our work.

Report a bug

 * If you think you have spotted a bug, create a ticket in Phabricator and use the tag.
 * For bugs, please include steps to reproduce (see How to report a bug) with corresponding screenshot(s), gif, or video of the bug, so we can test the issue. If this bug is blocking a process at your wiki, let us know on the team’s talk page as well.
 * To suggest a new feature, or improve an existing feature, see below.

Working with Communities
Please see our Frequently Asked Questions page for quick answers.


 * We are looking for information and input from various other places and demographics. Here are some ways you can help us through some useful resources on how to interact with newcomers or how to get the tools we create on your wiki.
 * If you wish to see Growth features being deployed at your wiki, please check on our documentation.
 * If you want to suggest a feature improvement or a new feature, please contact us on our team talk page. Please explain:
 * The context in which your idea would be used (wiki, workflow, …)
 * The evidence that conducted you to think about this improvement (“at my wiki, I see X newcomers being blocked by…”, “data shows that…”, “this research project shows that…”, etc.)
 * How beneficial it would be for communities and newcomers.

Internally request work from the Growth Team

 * If you work for the Wikimedia Foundation and want to request any work from the Growth team outside of the annual planning process, please use Phabricator (see Phabricator) to do this. Create a [https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=Growth-Team&description=%2A%2ADescription%2A%2A%0A....%0A%0A%0A%2A%2AAcceptance%20Criteria%2A%2A%0A%20%20%23%20Should%20be%20able%20to%20....%0A%20%20%23%20....%0A%0A%23%23%23%23%20Completion%20checklist%0A%0A%2A%2AFunctionality%2A%2A%0A%5B%5D%20The%20patches%20have%20been%20code%20reviewed%20and%20merged%0A%5B%5D%20The%20task%20passes%20its%20acceptance%20criteria%0A%0A%2A%2AEngineering%2A%2A%0A%5B%5D%20There%20are%20existing%20and%20passing%20unit%2Fintegration%20tests%0A%5B%5D%20Tests%20for%20every%20involved%20patch%20should%20pass%0A%5B%5D%20Coverage%20for%20every%20involved%20project%20should%20have%20improved%20or%20stayed%20the%20same%0A%0A%2A%2ADesign%20%26%20QA%2A%2A%0A%5B%5D%20If%20the%20task%20is%20UX%2FDesign%20related%3A%20it%20must%20be%20reviewed%20and%20approved%20by%20the%20UX%2FDesign%20team%0A%5B%5D%20Must%20be%20reviewed%20and%20approved%20by%20Quality%20Assurance.%0A%0A%2A%2ADocumentation%2A%2A%0A%5B%5D%20Related%20and%20updated%20documentation%20done%20where%20necessary%0A%0A%20%20-%20Internal%20technical%20changes%3A%20internal%20repository%20documentation%20must%20be%20updated%20%28README.md%2C%20JSDoc%2C%20PHPDoc%29%0A%20%20-%20Infrastructure%20technical%20changes%3A%20technical%20changes%20that%20reflect%20on%20environment%2C%20infrastructure%2C%20endpoints%20or%20any%20other%20area%20of%20interest%20for%20technical%20contributors%20should%20be%20reflected%20on%20%5B%5B%20https%3A%2F%2Fwww.mediawiki.org%2Fwiki%2FExtension%3AGrowthExperiments%20%7C%20Extension%3AGrowthExperiments%20%5D%5D%20or%20%5B%5B%20https%3A%2F%2Fwww.mediawiki.org%2Fwiki%2FExtension%3AGrowthExperiments%2FTechnical_documentation%20%7C%20Extension%3AGrowthExperiments%2FTechnical%20documentation%20%5D%5D%20pages. detailed Phab task] with a clear explanation of the problem and what is needed from the Growth team:
 * Tag the Growth team (#growth-team) on the Phab task
 * Include links, code, pictures, etc. if they can help us
 * Include deadlines (where applicable)
 * Add Tech Lead, Product Manager  , and TPgM    to the ticket by tagging all three of them in the task (in a comment or in the description)
 * Please allow for at least 5 business days before following up with the team
 * If a follow-up is needed, please send Technical Program Manager, Mariya Shilova, a Slack message with a link to your Phab task
 * If your team is blocked on a Phab task, please ping us on Phab. Feel free to reach out to our Technical Program Manager, Mariya Shilova, on Slack as well
 * If you need Growth Team’s help with an unanticipated project that was not on Growth Team’s roadmap or with a request larger than a simple Phab task:
 * Please reach out directly to our Technical Program, Manager Mariya Shilova, on Slack or via email at mshilova@wikimedia.org.
 * From here, our TPgM will escalate to our Product Manager and coordinate a meeting between Product Managers and other necessary team members to clarify the request, identify stakeholders, and discuss possible timelines and impacts.
 * Please reach out at least one quarter in anticipation so that we can accommodate both teams’ roadmaps and goals