T283505 will introduce a fixed "sticky" site header. to the desktop reading experience.
To start, the sticky header will //NOT// contain editing functionality, per T294383.
Before editing functionality is addedThis task represents the work with running an A/B test to evaluate the impact introducing an edit affordance within desktop reading experience's fixed "sticky" site header has on the following:
1. The speed and ease with which contributors, across experience levels, we will need to define how we will evaluate the impact of doing socan begin making a change to the content they are wanting to affect
2. This evaluation is important because it will help us decide whether the change needs to be undone,How likely people are to publish the edits they start making
3. iterated upon,Peoples' awareness of their ability to edit the content they are consuming
4. or exposed to a larger number of people.The rate at which people make destructive changes to wikis
=== Decision to be made
This A/B test will help us make the following decision: **Should edit affordance(s) within the sticky header be made available to more people?**
//Note: we have yet to define what "more people" means in this context and defining it depends on knowing all of the people who have access to the sticky header at the time the test is run.//
=== GuardrailsHypotheses
//To help evaluate the impact of incorporating editing functionality within the stickyTo help evaluate the impact of the impact of introducing an edit affordance within desktop reading experience's fixed "sticky" site header, **we will analyze the following...//ould like to know if doing so...**
|ID|ScenarioHypothesis|Metric(s) for evaluation
|---|---|---|---
|KPI|**...causes** people, across experience levels, to publish a greater number of edits on desktop because they will need to expel less effort to start an edit to fix something they noticed while reading. | //TBD. Metrics will be defined in T296264.//
|Curiosity #1| **...causes** people to begin making a change to content more quickly and with greater ease because they will be able to locate the content they opened the editing interface seeking to affect with less effort.| //TBD. Metrics will be defined in T296264.//
|Curiosity #2| **...causes** a greater number of people to open/explore editing because there will be an omnipresent edit affordance reminding them of the ability they have to affect the content they are consuming.| //TBD. Metrics will be defined in T296264.//
⚠️@mneisler and @ppelberg to populate⚠️|Guardrail #1|**...does not cause** a sustained decrease in the rate at which people publish the edits they initiate. | //TBD. Metrics will be defined in T296264.//
|Guardrail #2|**...does not cause** a sustained increase in the rate at which people publish destructive edits. | //TBD. Metrics will be defined in T296264.//
=== Decision Matrix
|ID|Scenario|Plan of action
|---|---|---
|1.| People with access to the edit affordance within the sticky header publish a significantly **higher number** of edits than those who do not have access to the affordance | //TBD//
| 2. |People with access to the edit affordance within the sticky header publish a significantly **lower number** of edits than those who do not have access to the affordance | //TBD//
| 3. | People with access to the edit affordance within the sticky header publish a **nominally different number** of edits than those who do not have access to the affordance | //TBD//
//Note: all of the scenarios above assume there is NOT a sustained decrease in the rate at which people publish the edits they initiate or a sustained increase in the rate at which people publish destructive edits.
=== Done
- [ ] A report is published that evaluates the `===Hypotheses` above