Change Details

== Background - We would like to run an experiment on the UI of the empty state of search. This ticket will cover investigating different options for the set up for this experiment and making a recommendation for the best option == User story - As a developer, I would like to know what the best way to deliver an experimental version of the empty search state is so that I can understand whether the empty state of search is an effective placement for recommendations == Requirements NOTE: to be used in pt2. Leaving here for reference === Metrics requirements The experiment designed should allow us to track the following (or as much as the following as possible) **Quantitative metrics - high priority** [] Search sessions initiated [] Impressions of search suggestion [] Clicks on suggestions [] Text types into search - i.e. we would want some way to know whether a session was completed using a suggestion, completed using search (they began typing and selected a result), or abandoned **Qualitative metrics - nice to have** [] Overall interest in search suggestions [] Overall satisfaction with UI of feature [] Ease of use of functionality itself === Other constraints [] The experiment should take no more than 2 weeks to build and set up [] The experiment cannot run for more than 2 weeks [] Nice to have - a group large enough to test on as to render the results statistically significant [] Nice to have - the ability to compare the results to similar results from features such as related pages [] Nice to have - the ability to measure external referrals for the pages of the test == Acceptance criteria [] Create a list of previously completed experiments/ways this or other teams has presented new features to users/(adding new ideas of potential ways we could do this is also acceptable) [] Document this list == Communication criteria - does this need an announcement or discussion? [] Define communication criteria for experiment == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //

== Background - We would like to run an experiment on the UI of the empty state of search. This ticket will cover investigating different options for the set up for this experiment and making a recommendation for the best option == User story - As a developer, I would like to know what the best way to deliver an experimental version of the empty search state is so that I can understand whether the empty state of search is an effective placement for recommendations == Requirements NOTE: to be used in pt2. Leaving here for reference === Metrics requirements The experiment designed should allow us to track the following (or as much as the following as possible) **Quantitative metrics - high priority** [] Search sessions initiated [] Impressions of search suggestion [] Clicks on suggestions [] Text types into search - i.e. we would want some way to know whether a session was completed using a suggestion, completed using search (they began typing and selected a result), or abandoned **Qualitative metrics - nice to have** [] Overall interest in search suggestions [] Overall satisfaction with UI of feature [] Ease of use of functionality itself === Other constraints [] The experiment should take no more than 2 weeks to build and set up [] The experiment cannot run for more than 2 weeks [] Nice to have - a group large enough to test on as to render the results statistically significant [] Nice to have - the ability to compare the results to similar results from features such as related pages [] Nice to have - the ability to measure external referrals for the pages of the test == Acceptance criteria [] Create a list of previously completed experiments/ways this or other teams has presented new features to users/(adding new ideas of potential ways we could do this is also acceptable) [] Document this list == Communication criteria - does this need an announcement or discussion? [] Define communication criteria for experiment == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //

== Background - We would like to run an experiment on the UI of the empty state of search. This ticket will cover investigating different options for the set up for this experiment and making a recommendation for the best option == User story - As a developer, I would like to know what the best way to deliver an experimental version of the empty search state is so that I can understand whether the empty state of search is an effective placement for recommendations == Requirements NOTE: to be used in pt2. Leaving here for reference === Metrics requirements The experiment designed should allow us to track the following (or as much as the following as possible) **Quantitative metrics - high priority** [] Search sessions initiated [] Impressions of search suggestion [] Clicks on suggestions [] Text types into search - i.e. we would want some way to know whether a session was completed using a suggestion, completed using search (they began typing and selected a result), or abandoned **Qualitative metrics - nice to have** [] Overall interest in search suggestions [] Overall satisfaction with UI of feature [] Ease of use of functionality itself === Other constraints [] The experiment should take no more than 2 weeks to build and set up [] The experiment cannot run for more than 2 weeks [] Nice to have - a group large enough to test on as to render the results statistically significant [] Nice to have - the ability to compare the results to similar results from features such as related pages [] Nice to have - the ability to measure external referrals for the pages of the test == Acceptance criteria [] Create a list of previously completed experiments/ways this or other teams has presented new features to users/(adding new ideas of potential ways we could do this is also acceptable) [] Document this list == Communication criteria - does this need an announcement or discussion? [] Define communication criteria for experiment == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //