Emphasize the Importance of Dogfooding

We name our internal customers, and define dogfooding as a product principle, but we should be more explicit within Product (and our Internal Customers) about the outsized value of dogfooding. This outsized value includes:

• Reduced cost because we don't have to build and maintain internal tool "ourselves"
• Increased revenue because the tool isn't

This could extend to be more explicit when we choose NOT to dogfood and instead develop additional tools outside of GitLab. Perhaps a statement from internal customers after issues are submitted that they are pursuing creating an "Outside of GitLab" tool for designated reasons, and the further use of the rebuild in GitLab label.

Actions

• MR to Product Handbook to express outsized value of dogfooding
• Communication in Product Team call - Set for Tuesday 19/01/29
• Request PMs inform/review with internal customers - Set for Tuesday 19/01/29
• Add to company call agenda - Set for Monday 19/01/28
• Mention in #general on slack - https://gitlab.slack.com/archives/C0259241C/p1548449268840600
• Documenting the "Not Dogfooding" process - not sure where?