Change Details

key components * March deployment * brief: https://docs.google.com/document/d/1SPrfaeX35sqWfUMwRctBLa3clZSX66-2gLWdPtnIqhk/edit#heading=h.wa6t6efaafc4 * irene/mike notes doc with discussion: https://docs.google.com/document/d/16Bi24LIV9R4HMAs4kcyio457fHFQYOSRxWvLo6ykomg/edit#heading=h.bq8pms66tw9a * > There appear to be four different questions here... > 1. MVP questions to answer > 2. MVP data to collect > 3. mid-term questions to answer and data collected which will answer those questions > 4. Where can Irene support > MVP priority is to make sure the extension is functional and being installed: i.e. we want to be able to track how many users are installing it to reach our minimal goals for enough experimental data. We also want to know that they are able to use the extension successfully: e.g. it's not timing out, they are not abandoning it due to latency, they are getting results to their queries. Ideally these are all metrics we can try to directly influence to get more people using the extension: e.g. try to reduce latency; increase search results, etc Elias is also working on logging some operational metrics, so we should touch base with him. After MVP, we will want to be able to look at logged historical queries and their results in order to do an internal quality audit of how well the extension is performing. We will also want to make sure we're logging the right metrics in order to have some signals to help answer the major experimental questions. This can be in conjunction with qualitative surveys

key components * March deployment * brief, Product Planning doc: https://docs.google.com/document/d/1SPrfaeX35sqWfUMwRctBLa3clZSX66-2gLWdPtnIqhk/edit#heading=h.wa6t6efaafc4 * irene/mike notes doc with discussion: https://docs.google.com/document/d/16Bi24LIV9R4HMAs4kcyio457fHFQYOSRxWvLo6ykomg/edit#heading=h.bq8pms66tw9a * > There appear to be four different questions here... > 1. MVP questions to answer > 2. MVP data to collect > 3. mid-term questions to answer and data collected which will answer those questions > 4. Where can Irene support > MVP priority is to make sure the extension is functional and being installed: i.e. we want to be able to track how many users are installing it to reach our minimal goals for enough experimental data. We also want to know that they are able to use the extension successfully: e.g. it's not timing out, they are not abandoning it due to latency, they are getting results to their queries. Ideally these are all metrics we can try to directly influence to get more people using the extension: e.g. try to reduce latency; increase search results, etc Elias is also working on logging some operational metrics, so we should touch base with him. After MVP, we will want to be able to look at logged historical queries and their results in order to do an internal quality audit of how well the extension is performing. We will also want to make sure we're logging the right metrics in order to have some signals to help answer the major experimental questions. This can be in conjunction with qualitative surveys Components: [x] Understand and prioritize Fact Checker questions to answer [x] Discuss questions with PM to understand the crux of the questions’ intention, how important is that question, can we answer that question with the information available…and what is the cost of answer that question [x] Help PM define which questions are best answered with product quantitative vs qualitative data [x] Review sample logging data to make intro rough level logging requests/recommendations [x] Review plugin key components to ensure key analytics tracking details are carried over to the Fact Checker code base [x] Identify MVP data to collect from OpenAI logging [] Identify which data sources can answer which questions (whether with full conviction or as a signal or proxy) [] Define where Irene support in February/March (note product launches in March…what date?) [] Note tiers of work involved (short term vs mid term)

key components * March deployment * brief, Product Planning doc: https://docs.google.com/document/d/1SPrfaeX35sqWfUMwRctBLa3clZSX66-2gLWdPtnIqhk/edit#heading=h.wa6t6efaafc4 * irene/mike notes doc with discussion: https://docs.google.com/document/d/16Bi24LIV9R4HMAs4kcyio457fHFQYOSRxWvLo6ykomg/edit#heading=h.bq8pms66tw9a * > There appear to be four different questions here... > 1. MVP questions to answer > 2. MVP data to collect > 3. mid-term questions to answer and data collected which will answer those questions > 4. Where can Irene support > MVP priority is to make sure the extension is functional and being installed: i.e. we want to be able to track how many users are installing it to reach our minimal goals for enough experimental data. We also want to know that they are able to use the extension successfully: e.g. it's not timing out, they are not abandoning it due to latency, they are getting results to their queries. Ideally these are all metrics we can try to directly influence to get more people using the extension: e.g. try to reduce latency; increase search results, etc Elias is also working on logging some operational metrics, so we should touch base with him. After MVP, we will want to be able to look at logged historical queries and their results in order to do an internal quality audit of how well the extension is performing. We will also want to make sure we're logging the right metrics in order to have some signals to help answer the major experimental questions. This can be in conjunction with qualitative surveys Components: [x] Understand and prioritize Fact Checker questions to answer [x] Discuss questions with PM to understand the crux of the questions’ intention, how important is that question, can we answer that question with the information available…and what is the cost of answer that question [x] Help PM define which questions are best answered with product quantitative vs qualitative data [x] Review sample logging data to make intro rough level logging requests/recommendations [x] Review plugin key components to ensure key analytics tracking details are carried over to the Fact Checker code base [x] Identify MVP data to collect from OpenAI logging [] Identify which data sources can answer which questions (whether with full conviction or as a signal or proxy) [] Define where Irene support in February/March (note product launches in March…what date?) [] Note tiers of work involved (short term vs mid term)