Skip to content

Updating user type: adding CISO

Kyle Mann requested to merge kmann-master-patch-83737 into master

Adding the user type "Chief Information Security Officer". We have talked about this user type as someone we are solving for, but it is not documented. As we get more data-driven by our research efforts, I'd like to continually evolve these user types: tools they use, relevant JBTD/tasks, data that interest them, and how security affects them (perhaps short text-descriptions?). I think it's great to start documenting here because then it's visible, accessible, and easy to build on. Though if identify a better place, we can always change as we go.

Few other thoughts for consideration-awareness:

  • I opened this epic to take steps to improve our info/data viz foundations. It all starts with the user type (step 1 of the epic), then based on that identify what data is important to that type
  • Being precise about the user type helps clarify our research recruiting effort. Who are we testing precisely, then having more crisp feedback
  • As we evolve the user type descriptions, we can add them to issues, such as "Users we are designing for" (something like that) then we know who the problem-solution is specifically being solved for

Awareness, feedback, or concerns to the proposed MR and notes: @andyvolpe @tlavi @loriewhitaker

(Assigned MR to @vkarnes)

Merge request reports