Drive down new tickets on common problems by making our top-15 highest-traffic documentation pages & top 15 support linked documentation pages accurate, informational, and easy to read. When MR is ready for TW review, please assign according to the [spreadsheet](https://docs.google.com/spreadsheets/d/1DqjMC4D83zOmkFANx9PKnsaNV02UlalYV5x5G_fZSZE/edit#gid=0) ## Calculation - [x] areas identified 10% - [x] assigned 10% - [x] MRs submitted 40% : 29/30 = 97% > of total: 39% - [x] MRs merged 40% : 29/30 = 97% > of total: 39% ## Timeline The current **due date** for the support issues are for when docs MR should be submitted. It will be up to the docs team to review and work with the support team member to have them completed by the [docs OKR due dates](https://gitlab.com/groups/gitlab-com/-/epics/445). Please set the MR to close your issue; or you can close it when you've submitted the MR. ## Good: - Power of leadership and collaboration from Lee Matos and Cynthia Ng, Tech Writing team, and from dozens of Support Engineers and Tech Writers. - Prioritized list based on top access by customers to increase impact - Result ties into Ticket Deflection work that is dependent on documentation correlation to customer problems/solutions ## Bad: - During the process it was hard to know state of completion. A number of people spent time with ‘no progress’ then knocked it out in 2 days or so. ## Try: - Make sure to validate problem space and expected result for objectives - More checkpoint due dates in process to allow for smoother completion and to more easily identify potential problems to delivery.