# Daily Check in Chats - Good Example 2

### ***Example 2:*** [Eng.Feature](https://docs.google.com/spreadsheets/d/1oLK2tP6k4ZalKM2P64z022zP6dSG2E5EddHhJCNSs7A/edit#gid=142906438)

***Status & driving question(s)***

* [Link](https://docs.google.com/spreadsheets/d/1oLK2tP6k4ZalKM2P64z022zP6dSG2E5EddHhJCNSs7A/edit#gid=142906438) to manager's worksheet
* [24/32](https://docs.google.com/spreadsheets/d/1oLK2tP6k4ZalKM2P64z022zP6dSG2E5EddHhJCNSs7A/edit#gid=142906438) (75%) many Check In Chats completed
* Driving questions during CICs: *“Are your Verification FTAR and Code Review FTAR 100%? If NOT, What specific actions will you take to address the gap?”*
  * *If you’re not at 100% for Verification and Code Review, are you on track? If NOT, are your obstacles, and how will you overcome them?”*

***Top 3 insights and actions:***

***Insight 1*****:** Code Review FTAR fails to reach 100% due to a critical bottleneck in [Product Chief Architect(PCA) capacity](https://drive.google.com/open?id=1HcuBll_EZffYQ5Dhlc2nta3-U-3sQ8qC). Specifically, seven ICs are able to access only one PCA.

**Action 1:** In an effort to improve the quality of the review requests reaching the PCA, and to improve the [PCA Code Review FTAR by 7.5%](https://drive.google.com/open?id=1GqIrNcSlt37pmGOQQeRRnOScvfXBbl9H)*,* we will implement the [EQB Implementation Plan](https://docs.google.com/spreadsheets/d/1oLK2tP6k4ZalKM2P64z022zP6dSG2E5EddHhJCNSs7A/edit#gid=447117371) by establishing the Eng.Feature.QE team. This will throttle the input levels for PCA as the [new IQBs pass only 47%](https://docs.google.com/spreadsheets/d/1oLK2tP6k4ZalKM2P64z022zP6dSG2E5EddHhJCNSs7A/edit#gid=447117371) of the PRs.

***Insight 2*****:** The team currently relies on peer-reviews and self-review the complete the 5-Point Code Review Checklist prior to submitting implementations for PCA Code Review

**Action 2:** In an effort to improve improve [PCA Code Review FTAR by 7.5%](https://drive.google.com/open?id=1GqIrNcSlt37pmGOQQeRRnOScvfXBbl9H), we’ll roll out a new Internal QB “[Implementation Review Complete](https://docs.google.com/spreadsheets/d/1oLK2tP6k4ZalKM2P64z022zP6dSG2E5EddHhJCNSs7A/edit#gid=447117371\&range=A49:B49)” to track quality across implementations.

***Insight 3*****:** Check-In Chat status of [“OnTrack - 93%”](https://drive.google.com/open?id=1afWizhFxwzojgrOs5GKCW60_1Wdrqii7) is misrepresenting the lower values of [PCA CodeReview FTAR of 93%](https://drive.google.com/open?id=1afWizhFxwzojgrOs5GKCW60_1Wdrqii7) and a [T4W Avg productivity of 51%](https://drive.google.com/open?id=1jrKDSCFDW36QnQUL_Jy24jnyJvkYc9ej).

**Action 3:** In an effort to [improve the Code Review FTAR% by 23%](https://drive.google.com/open?id=1rDbvrQT9p-_F5A0JCT-rTxV73ZSMvnSy), we’ll align the [Check-In Chat status](https://drive.google.com/open?id=1kOxQxoPDwW5TQzcXFqa16_GQiqQffnBz) to enable the SEM to make corrective actions and avoid repeating incidents such as “Lack of PCA engagement.”


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://remoteu.gitbook.io/manager-remoteu/day-2/day-5-examples/great-daily-check-in-chats-example-2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.