Every quarter, we work on [team Objectives and Key Results (OKRs)](https://gitlab.com/gitlab-com/gitlab-OKRs/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=division%3A%3AMarketing&label_name%5B%5D=OKR&label_name%5B%5D=Department%3A%3ADeveloper%20Relations&first_page_size=20) that align with company OKRs.
For each quarterly objective and key results, the Developer Relations team will assign a [DRI](/handbook/people-group/directly-responsible-individuals/). For our team, we have responsibilities that build upon the GitLab guidance on achieving and [updating](/handbook/company/okrs/#maintaining-the-status-of-okrs). Typically, People managers are the DRIs for objectives while ICs are the DRIs for key results.
- Objective DRI Responsibilities
- Own strategy for achieving objectives including supporting the DRIs for key results that will help to achieve our objectives.
- Collaborate with the owners of the key results that contribte to your objective to set a plan to deliver on the KRs and objective.
- Maintain communication with KR owners - synchronous or asynchronous - throughout the quarter as needed.
- Provide bi-weekly updates in the epic and in the Developer Relations bi-weekly team meeting agenda on the objective including completion percentage and status. We recognize that there will be no change from the previous report at times.
- Present overview and status updates in team business reviews.
- Escalate any urgent needs to your manager.
- Key Results DRI Responsibilities
- Create and manage strategy for achieving the key results. Manage dependencies, set actions, and define how your items will be scored.
- Provide bi-weekly updates in the issues in the [GitLab OKRs project](https://gitlab.com/gitlab-com/gitlab-OKRs/) including completion percentage and status. The issues are the single source of truth for your KR. We recognize that there will be no change from the previous report at times.
- Ensure key result information is up-to-date for team business reviews.
- Escalate any urgent needs to your manager.
#### How we update our OKRs
To update our [list of current OKRs](https://gitlab.com/gitlab-com/gitlab-OKRs/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=division%3A%3AMarketing&label_name%5B%5D=OKR&label_name%5B%5D=Department%3A%3ADeveloper%20Relations&first_page_size=20):
1. Follow the [OKRs in GitLab handbook](/handbook/company/okrs/okrs-in-gitlab/)
1. Create OKRs, and KR items.
1. Add the following labels: `Division::Marketing`, `Department::Developer Relations`, `OKR`.
**OKR Health:** We use [issue health](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#health-status) indicators to help people understand an OKRs status at a glance. These status indicators are:
-`on track`
-`needs attention`
-`at risk`
**Progress**: Edit the `progress` attribute in KRs to indicate how much progress has been made.
### Developer Relations KPIs
The Developer Relations team monitors several [Key Performance Indicators and related Performance Indicators](/handbook/marketing/developer-relations/performance-indicators/).
@@ -81,7 +81,7 @@ We recognize these KPIs and metrics don't capture the impact of the diverse rang
When we are reviewing opportunities or requests for support, we must be able to answer yes to each of these questions to move forward with the work:
1. Will this work support, grow, and/or engage GitLab customers and community members?
1. Is there a measurable impact against one of our team's KPIs? Because of GitLab's [global optimization subvalue](/handbook/values/#efficiency-for-the-right-group), we'll also consider requests that influence a company KPI or contribute to progress on an OKR.
1. Is there a measurable impact against one of our team's KPIs? Because of GitLab's [global optimization subvalue](/handbook/values/#efficiency-for-the-right-group), we'll also consider requests that influence a company objective.
1. Has an issue been created to define the work and assign a DRI?
If the answer to any of the above questions is "no", we ask the requestor to take one of the following actions:
@@ -7,7 +7,11 @@ title: "Developer Relations Workflows and Tools"
<!-- Keep this incoming anchor for compatibility -->
<aid="community-response-workflows"></a>
### Team Workflows
### Team objectives
For more information on how objectives are set and managed in GitLab today please review the internal only [GitLab Operating Model](https://internal.gitlab.com/handbook/company/gitlab-operating-model/) Handbook page. Developer Relations objectives are labeled with [the `Owner::DevRel-Strategy` label](https://gitlab.com/groups/gitlab-operating-model/-/work_items?sort=created_date&state=opened&label_name%5B%5D=Owner%3A%3ADevRel-Strategy&type%5B%5D=epic&first_page_size=50) in an internal only group.
### Team workflows
-[Code of Conduct Enforcement](/handbook/marketing/developer-relations/workflows-tools/code-of-conduct-enforcement/)
