Skip to content

Rename Enablement to Core Platform

Joshua Lambert requested to merge jl-rename-enablement into master

The rationale for this change is two key reasons:

  • Enablement is a confusing name internally and externally.
    • Most people who first hear the name think of responsibilities like Sales or Product Enablement. This is inefficient for ourselves and our customers, and frequently requires further explanation for clarity.
  • Platform groups/engineering have become more widely known and recognized in the industry.
    • Platform is a better description of what we do than Enablement
    • In fact, there are now conferences popping up devoted to platform engineering: https://platformcon.com/.

Note, this is the minimal change to rename Enablement to App Platforms. There will be many other places we need to update, but this can be used to get approvals in a lower change rate area. If approved, we can then go quickly update other areas with less risk for conflicts due to approval cycles.

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

  • Chief Product Officer @david
  • VP of Infrastructure @meks
  • VP of Product @mflouton
  • The Product Director relevant to the affected Section(s) @joshlambert
  • The Engineering Director relevant to the affected Section(s) @cdu
  • Director of Product Design @vkarnes

The following people need to be on the merge request so they stay informed:

  • Vice President of Infrastructure/Quality @meks
  • Vice President of User Experience @vkarnes
  • The Product Marketing Manager relevant to the stage group(s)
  • Director of Technical Writing @susantacker

After Approvals and Merge

Edited by Joshua Lambert

Merge request reports