J
Joseph Ghafari
We operate in a multilingual environment, where some stakeholders require OKRs to be defined in different languages. Currently, we work around this by adding translations directly to the titles of objectives, key results, and initiatives. However, this approach results in cluttered and unnecessarily verbose titles.
We propose a feature that would allow us to set alternative titles in various languages for OKR plans, which would make the platform more flexible and user-friendly.
Proposed Feature:
1. Default Language Setting:
Enable setting a default language for each plan.
2. Alternative Titles/Descriptions:
Allow us to assign alternative titles and descriptions for objectives, key results, and initiatives in other languages. If an alternative title is not provided, it will default to the title in the plan’s default language.
3. User Language Preferences:
When a user views the plan, they will see the titles and descriptions in their preferred language (if available). If their language is not supported, the titles will default to the plan’s default language.
.
This feature would streamline multilingual support and improve clarity, especially in diverse teams where language barriers can impact understanding and collaboration.
Note:
While providing machine translation for things like check-ins may be acceptable, for the plan itself we need to have human translations to make sure we have actual alignment between all the stakeholders and avoid the risk of miscommunication.