Skip to content
Snippets Groups Projects
Open Update Secure & Protect User Personas
  • Update Secure & Protect User Personas

  • Open Epic created by Michael Oliver

    What's this issue all about? (Background and context)

    This Epic will be used to track research issues following the process listed in the Handbook Page on How to Create a User Persona.

    Updating, & Validating Secure and Protect user personas, Creating additional personas if necessary. This research came from a synced meeting with @sam.white in which he related the shortcomings of the current secure & protect personas, which were lacking accuracy compared to the industry and client outreach. Primary areas of concern are:

    1. The JBTD and tools for multiple persona would more accurately belong to one or several other personas. With the Security Operation Engineer (Alex) persona being researched in the past with both internal (issue #358 and external participants, it is more likely that this research will focus the Security Analyst (Sam) persona.

    2. There are several personas missing that could provide significant usefulness to both secure and protect groups. These include Application Security Engineer and Infrastructure Security Engineer.

    What are the overarching goals for the research?

    1. To update any personas as needed with more relevant & useful information. Since these concerns have been felt for some time (which was confirmed through multiple team members), it is likely that substantial changes may be necessary as the outcome of the research surface.

    2. To create any persona as needed, to build a more clear picture of our users. A possible sub-goal for this may be to investigate other avenues for displaying the JTBD for each persona, as early feedback indicates that there is significant variance from company to company which may depend on the size or maturity of the company.

    3. To gain a deeper understanding of the user personas in secure and protect, including ones not currently existing in the handbook. Specifically, to gain familiarity with the common frustrations, tools, and workflows of those personas. A priority for this goal is to create a neutral perspective for each persona, rather than a gitlab-centric perspective. Gitlab specific details will be surfaced only when necessary. The practical reason for this being that a neutral perspective will eventually help identify areas of growth for gitlab software.

    What research questions are you trying to answer?

    Fundamentally, all goals should be fulfilled by answering these major questions:

    • What are all of the relevant User Personas necessary for my stakeholders
    • What are the Jobs to be Done (JTBD) for each persona?
    • What are a the tools for each persona?
    • What are the key frustrations for each persona?
    • What are the additional core values, motivations, workflows, and associated teams in their workplaces for each persona?

    What persona, persona segment, or customer type experiences the problem most acutely?

    • Sam (Security Analyst)
    • Alex (Security Operations)

    Potential additional personas:

    • Applications Security Engineer
    • Infrastructure Security Engineer

    What business decisions will be made based on this information?

    Product Designers will use these personas to provide context for the use cases concerning each design by understanding the JTBD or intersecting software workflows.

    Product Managers will use these personas to provide context for product direction and potential areas of improvements by using the frustrations, JTBD, and motivations.

    What, if any, relevant prior research already exists?

    A previous Epic was created which resulted in numerous persona - related outcomes by using external interviews.

    Internal interviews have also been conducted, which was linked to the same study as described above.

    What timescales do you have in mind for the research?

    Who will be leading the research?

    @moliver28

    Relevant links (opportunity canvas, discussion guide, notes, etc.)

    This HB page on How to Create a User Persona will help guide this research.

      1. A-sync stakeholder conversation sheet
      • Create issue to track stakeholder conversation sheet.
      • @molive28 Fill in Stakeholder Conversation template to prepare for stakeholder
      • Give Stakeholder Conversation sheet to stakeholders, @ them through this issue.
      • Have stakeholders fill out sheet by 12/17/21
      • Summarise the information given.
      1. Internal Interviews
      • Create new issue to track internal interviews.
    ✓ 6 of 6 checklist items completed · Edited by Michael Oliver

    Linked items 0

  • Link items together to show that they're related or that one is blocking others.

    Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first