Discuss adjustments required for updated Customer User Personas
Summary
From @nk312:
We now have Customer User Personas mapped directly to Gitlab Use Cases on this handbook page. This should help provide insights into which types of personas interact with Gitlab and our many use cases, potentially helping in the creation of targeted workshops, trainings, programs, or onboarding materials.
As next steps, we're hoping to enrich our contact records in SFDC by adding these personas into the registration flow (specifically the Role dropdown) for web customers in the near future. For now, I will be working alongside SAs and CSMs in identifying and mapping Business Personas <> Use Cases, specifically for our Programs team which should help curate targeted marketing/onboarding material to help accelerate the expansion/add-on cycles
Current State
Today, one way 'Role' is collected for SFDC records is via the Gitlab.com Registration Flow for free & trial signups on Step 4 /welcome
This Role (and JTBD) data is synced to our marketing systems (Marketo/Iterable/SFDC) today.
From a Growth lens, we have strategic plans to leverage these Roles in product as well in the future to customize onboarding.
For the future
We would want to narrow down the list of 18 personas to the most common personas (maybe like top 5), especially ones that interact with the most use cases. The three additional I would recommend are:
- Platform Engineer
- Infrastructure Operations
- Release Manager
My assumption is that we also want to align the Roles in this dropdown to the Personas we list above.
Questions
- If we go down the path of just adding the 3 new Roles from the Persona list, what do we do with the other Roles we present?
- If we alter this list what happens to Marketing Ops and Product data?