The Common Issue Tracker serves as a comprehensive tool intended to standardize quality across the entire pool. It is designed to identify, document, and communicate major, recurring or otherwise important issues with the whole pool, providing relevant examples and comments. The tracker is stored in the pool’s Shared Folder on Drive and is accessible to every linguist in the pool.
When logging issues in the Common Issue Tracker, it's crucial to categorize them effectively to ensure clarity and actionable insights. With that in mind, the Common Issue Tracker structure is simple and accessible. It contains 6 columns to track only the most essential information:
Column name | Description |
# | Internal issue ID for easier tracking. It’s already filled for you. |
Category | A dropdown with the main issue categories: Linguistic, Technical, Creative Language, Sensitive Language, Other. |
Issue | Brief issue description. |
Incorrect Usage | Specific examples of incorrect usage (may be more than 1). |
Correct Usage | Specific examples of correct usage (may be more than 1). |
Comment | Any additional info, details or clarifications. |
The following types of issues should be logged:
Major and Blocker linguistic and technical issues: These are high-priority issues that significantly impact the quality and viewer experience. This category includes severe grammatical errors, mistranslations that alter meaning or critical display issues.
Issues repeating across the pool: Identifying recurring problems is essential for pinpointing systemic weaknesses or common misunderstandings. If a particular error, query, or challenge appears multiple times across different team members, it indicates a need for broader guidance, updated documentation, or a process improvement. Logging these helps to address the root cause rather than just individual instances.
Issues that could be easily avoided if correct reference materials and rules are followed: This category highlights a need for better adherence to existing guidelines or improvements in the accessibility or clarity of those guidelines. These issues often point to training gaps, insufficient onboarding, or hard-to-find reference materials.
Any other issues the Language Lead wants to communicate with the whole pool: This serves as a catch-all for any other observations, concerns, or areas for improvement that the LL deems important for the entire team to be aware of. This could include best practices, new insights, potential future challenges, or areas where collective effort is needed. It promotes open communication and ensures everyone is on the same page regarding project quality and processes.