## Research Goals Uncover JTBD for Security Operations (SecOps) engineers, and get an understanding of their day to day work and frustrations. ## Methodology We conducted 5 one-hour long interviews with our internal SecOps team. We also held short follow up sessions with some of the participants. ### An important note on the fidelity of the findings Having only 5 participants, all working for the same organization (GitLab), is far from ideal for this type of study. The sample size is relatively small, and the fact that all participants work for GitLab means we only really learnt about SecOps work the way it is done in GitLab. Nevertheless we chose this approach knowingly, as sourcing SecOps engineers for UXR studies is difficult and as Product preferred a relatively quick turnaround time. Therefore this study should be viewed merely as a first iteration on this topic. ## Results * [Security Operations Engineer persona (Alex)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer) * [SecOps Day in the Life](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/Day_in_the_Life_SecOpsEngineer_Persona.html) * [Incident response flow](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/assets/Incident_Response_Flow_SecOpsEngineer.pdf) * Detailed insights can be found in the issues added to this epic ## Appendix #### Planning * [Planning issue](https://gitlab.com/gitlab-org/ux-research/issues/358) * [Script](https://docs.google.com/document/d/10NryosQDsGrvA1MuI8Qu4kLQLHNDoF38SZ1fOGCbjf0/edit?usp=sharing) #### Analysis * [Full video recordings](https://drive.google.com/drive/folders/1I7w5ug0dlFjdQao2SMjgMtur-plIRxW-?usp=sharing) * [Notes (see the 'Analysis' sheet for analysis)](https://docs.google.com/spreadsheets/d/15yYB7C7nQBKZnOyPzT_xGxewvlw6qw-rPiCyHQMYKh4/edit?usp=sharing) * [Recording of the debrief meeting](https://drive.google.com/drive/folders/1sQY2pNuSAgGoga8b6XNXxwnr_3tfsM-P?usp=sharing)