Enablement narrow MR rate has been below the Development Department consistently. Now that the observation shows a consistent pattern, it's time to gain insights by analyzing impacting factors and collecting data to prove/disprove the hypothesis. The goal of this exercise is to identify opportunities for improvement and land a consensus what makes sense for Enablement with regard to MR rate. **References**: - [Development Narrow MR Rate](https://about.gitlab.com/handbook/engineering/development/performance-indicators/#development-department-narrow-mr-rate) - [Enablement KPI](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/) - [Sub-department](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/#development-indicators) - [Database](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/#database-group-development-indicators) - [Distribution](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/#distribution-group-development-indicators) - [Geo](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/#geo-group-development-indicators) - [Global Search](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/#global-search-group-development-indicators) - [Memory](https://about.gitlab.com/handbook/engineering/development/performance-indicators/enablement/#memory-group-development-indicators)