Operate First Personas + Info graphic

[HumairAK]

The websites WG meeting today discussed a need for an info graphic that details the different Operate First Personas and how they complement/interact with each other. But attendees were also not clear on what these different personas are that Operate First encompasses. So let's discuss the different personas here, then these will be converted to an info graphic by @stefwrite .

Please provide the personas you see the Operate First initiative covers. Follow this template:

---

Role:

Goal:

Pain Points:

---

[HumairAK]

I'll start:

---

Role: Operate First Cloud SRE

Goal:

• Operate and Manage clusters on the Operate First Cloud
• Provision new clusters
• Onboard users, teams to Operate First Cloud
• Maintain cluster stability, security, and health
• Respond to user issues

Pain Points:

• Cloud operations are too closed and opaque. There is no standard for operating platforms like OCP and K8S in an Open Source way.
• Operation efforts are hard to scale as workloads and users increase
• Knowledge is too easily siloed
• Developers and Operations can have conflicting goals

[HumairAK]

Please add any personas you feel should be here. If you feel the template should add more/less feel free to suggest alternatives.

[HumairAK]

@oindrillac @MichaelClifford could you provide some personas that you expect from data science perspective that you envision the website should target/keep in mind

@hpdempsey can you provide an intern/coop persona(s) ?

similarly @quaid / @durandom can you provide personas from community perspective that is not covered above?

[banthedev]

I wanted to post the Personas I added to the community repo via markdown files https://github.com/operate-first/community/pull/164

All the personas created can be found in https://github.com/operate-first/community/tree/main/users

Though following your format Humair

Role: Undergraduate Student

Goals:

• Learn new skill (whether it be for their resume or self-knowledge)
• To add new experience contributing to an Open-source community to their resume
• Learning about Open Source software and communities
• Students learn about Cloud computing and Cloud operations '
• Students will be tasked smaller issues/tasks
• Experienced students will help new users of the community

Pain Points:

• Could be unfamiliar with the cloud, specifically kubernetes and OpenShift
• Might have a hard time understanding docs
• Students would require more assistance when familiarizing with Operate First as an initiative and a platform (OPF philosophy and the technical aspect)

[quaid]

The websites WG meeting today discussed a need for an info graphic that details the different Operate First Personas and how they complement/interact with each other. But attendees were also not clear on what these different personas are that Operate First encompasses. So let's discuss the different personas here, then these will be converted to an info graphic by @stefwrite .

I brought up some existing content, let me share with several caveats:

• I'm immersed in the way personas and user stories are used in Agile processes, that is not the intention of this work.
• These personas are from a marketing perspective, which is why they are useful for website design and content decisions.
• The lead on creating these was @ghaff and he conducted interviews with senior people in each of the fields.

These are the personas and some ideas of their relationship to Operate First; the ones converted to MarkDown from the original spreadsheet are hyperlinks.

• Academic Researcher
• Academic Administration
• Architect / IT Decision Maker
• Application Developers and QE
• Data Scientist
• Data Engineer
• General Public
• [Line of Business Owner](https://github.com/operate-first/community/blob/main/users/lineofbusiness.md]
• Open Source Developer
• SRE / Cloud Operator
• Sysadmin
• Undergrad Student

Please provide the personas you see the Operate First initiative covers. Follow this template:

Role:

Goal:

Pain Points:

We need to do two things first/alongside:

1. Merge the user persona template fields.
2. Clarify more about the personas that have many, many different versions in the real world.

An example of the second is, a person who is educated in data science and then works at Red Hat on open source data science tools has a very different role, goals, and pain points than a data scientist working in a corporation doing modeling for business functions.

[stefwrite]

Given that this is a long list, is there a way to group these personas into groups based on the ways they'll be using Operate First (and/or accessing resources at the Op1st website)? Maybe if for each persona we come up with answers to these questions:

• Who am I?
• Why is Operate First interesting to me?
• What will I be doing in Operate First?
• What would I like Operate First to be able to do that it can't yet do?

Those answers would set us up to find common ways that personas are using Operate First. We could also use this to inform and prioritize any work in progress.

@quaid ^ I've incorporated what we talked about in ContribX Docs WG.

[schwesig]

/area user /kind documentation /kind handbook /kind experience /kind user-story

[ghaff]

We started to do that initially, e.g. with developers/QE.

Probably requires some thought but I'd probably bucket together the developer roles, the academic roles, maybe the data roles (though they are somewhat distinct, maybe sysadmin with SRE...

On Mon, Apr 25, 2022 at 1:27 PM Stephanie E. Watson < @.***> wrote:

Given that this is a long list, is there a way to group these personas into groups based on the ways they'll be using Operate First (and/or accessing resources at the Op1st website)?

— Reply to this email directly, view it on GitHub https://github.com/operate-first/community/issues/180#issuecomment-1108845477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALYS7BUIDCMQVASG65F27DVG3IYVANCNFSM5TZZH2XQ . You are receiving this because you were mentioned.Message ID: @.***>

[sesheta]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[schwesig]

/close changed priorities

[op1st-prow[bot]]

@schwesig: Closing this issue.

In response to [this](https://github.com/operate-first/community/issues/180#issuecomment-1600560715): >/close >changed priorities Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.