Remove Leading Organizations from Engineering-owned handbook pages

1. [Internship Pilot](/handbook/company/working-groups/internship-pilot/)

1. [Isolation](/handbook/company/working-groups/isolation/)

1. [Issue Prioritization Framework](/handbook/company/working-groups/issue-prioritization-framework/)

1. [Leading Organizations](/handbook/company/working-groups/leading-organizations/)

1. [Learning Experience](/handbook/company/working-groups/learning-experience/)

1. [Learning Restructure](/handbook/company/working-groups/learning-restructure/)

1. [Licensing and Transactions Improvements](/handbook/company/working-groups/licensing-transactions-improvements/)

---

title: "Leading Organizations Working Group"

description: "The charter of this working group is to scale the Leading Organizations intiative."

status: active

---

## Attributes

| Property        | Value             |

|-----------------|-------------------|

| Date Created    | 2022-11-09        |

| End Date        | 2024-01-31        |

| Slack           | [#wg_leading-organizations](https://gitlab.slack.com/archives/C03KC7N184D) (only accessible from within the company) |

| Google Doc      | [Agenda](https://docs.google.com/document/d/1D5JdVVOMshVWp-9DANaRKFgLlLCrT4LAqQDo6_vJCdo/edit) (only accessible from within the company) |

| Issue Board     | [Epic](https://gitlab.com/groups/gitlab-com/-/epics/1880)             |

### Business Goal

Increase the number of unique monthly contributors by recognizing and incentivizing organizations who are among our most active contributors. This will create internal experts at GitLab organizations and ensure customers see it as their own product. This initiative supports our mission and our dual flywheel strategy where increasing wider community contributions leads to more users, thus higher revenue.

### Proposed Exit Criteria

Build scalable model to activate 100 Leading Organizations by the end of FY24-Q4.

### Plan

1. Develop robust pipeline

   1. Execute nurture campaigns and digital marketing playbooks to generate interest

   1. Integrate into strategic account segmentation and sales enablement

   1. Create customer success referral machinery

1. Faster time to value

   1. Increase conversion rate of workshops

   1. Reduce time to activation

1. Recognize and amplify success

   1. Publish case studies, blog posts and fireside chats with members about co-creation

   1. Amplify Leading Organizations' contributions at industry conferences

1. Increase capacity and improve attribution

   1. Increase reviewer/maintainer capacity in product areas with high number of contributions

   1. Improve contribution tracking, customer segmentation and attribution

## Roles and Responsibilities

| Working Group Role             | Team Member     | Functional Title                           |

|--------------------------------|-----------------|--------------------------------------------|

| DRI                    | Emilio Salvador   | VP, Developer Relations and Community          |

| Executive Stakeholder          | Ashley Kramer   | Chief Marketing & Strategy Officer         |

| Functional Lead: Contributor Success | Nick Veenhof | Director, Contributor Success           |

| Functional Lead: Developer Advocates | John Coghlan | Director, Developer Advocacy       |

| Functional Lead: Marketing Campaigns  | Jackie Gragnola | Sr. Manager, Marketing Campaigns and ABM |

| Functional Lead: Product Marketing  | Nicole Smith | Director, Product Marketing — Customer Advocacy |

| Functional Lead: Customer Success | Jamie Reid  | Manager, Strategic CSMs                     |

| Member                         | Sid Sijbrandij    | Chief Executive Officer                  |

* Rate limiting: once per requester/MR per day

* Processor: <https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/triage/processor/community/command_mr_feedback.rb>

#### Leading Organizations labeler

* Automation conditions:

  * MR was opened or updated

  * The MR does not have the `Leading Organization` label set

  * The MR author is from a [leading organization](/handbook/engineering/workflow/code-review/#leading-organizations) based on the data we have on Sisense

* Automation actions:

  * Adds the `Leading Organization` label

* Processor: <https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/triage/processor/community/label_leading_organization.rb>

#### Hackathon labeler

* Automation conditions:

of the company:

- From GitLab team members: Review-response SLO < 4 business days

- From authors of [Leading Organizations](/handbook/engineering/workflow/code-review/#leading-organizations): Review-response SLO < 6 business days

The team aims to return to the company-wide SLO standard dependent upon expanding the team and paying down technical debt.

of the company:

- From GitLab team members: Review-response SLO < 4 business days

- From authors of [Leading Organizations](/handbook/engineering/workflow/code-review/#leading-organizations): Review-response SLO < 6 business days

The team aims to return to the company-wide SLO standard dependent upon expanding the team and paying down technical debt.