Creating a comprehensive list of Job Statements for Secure

What is this about?

In GitLab we use the JTBD framework to guide product strategy, assess product maturity ratings, and align team members around what our users want to get done. Specifically in Secure, we want to take a collaborative approach to generating our Job Statements, and view the very activity of creating Job Statements to be an important aspect of team alignment process.
This issue maps out our plan for creating a comprehensive list of stage-level Job Statements.

What is the game plan?

To create Job Statements and start putting them to use, we’ll follow these steps:

  1. Each designer will note down Job Statements in a Google Doc, and share that doc with @tlavi. Due Date: Oct 26th. Already have Job Statements written? Great! (please send them over). Don’t have them yet? Here’s how to go about this:
    1. In your 1:1 with your PM, please spend some time brainstorming and writing down Job Statements you both consider to be relevant to your category, whether directly or indirectly.
    2. The format for a Job Statement is: When [situation], I want [Job], so that [outcome/need]. Having said that, please don’t worry too much about whether you’re writing Job Statements “correctly” or whether you’re hitting the “right” level of granularity. This step is more around capturing your perspective and thoughts, rather than crafting perfectly worded Job Statements.
    3. Please work separately with your PM, and avoid comparing notes with other designers - there’s power in each category thinking about this independently at first!
  2. All of Secure UX will participate in a sync workshop, where we’ll review what we have and bring it all together, to create our comprehensive assumptive list of Job Statements for Secure.
  3. Tali to do some minor clean up, and create an issue to ask PMs for async feedback.
    1. Optional (but likely) step: PMs and PDs to break down selected stage-level Job Statements into Category-specific User Statements, to make them more immediately actionable. Due Date: we will decide on whether this step is needed following the sync workshop. If deemed required, 1 week will be allocated for this step.
  4. Once internally validated by PMs, Tali will create an MR to add our Job Statements to the handbook.
  5. From this moment on, all of Secure’s PMs and PDs start using our Job Statements:
    1. Use them to aid in developing product strategy.
    2. Use them for Category Maturity Scorecards.
    3. Use them as inspiration for inter-stage collaboration opportunities.
    4. Mention them in issues to remind ourselves of the user Job that your issue addresses.
  6. Simultaneously, UXR to initiate further studies to complete validation of top Job Statements.

Todo

  • All Secure PDs: submit Job Statements to @tlavi (please check the box + unassign yourself from this issue once you’ve sent your Job Statements). Due Date: Oct 26th
  • All Secure UX: participate in 1st sync workshop. Date: Nov 9th
  • @tlavi Tidy up outputs from 1st workshop. Due date: Nov 10th.
  • All Secure UX: participate in 2nd sync workshops. Date: Nov 12th
  • @tlavi: Tidy up Job Statements and request feedback from PMs. Due date: Nov 16th
  • Due date for async PM feedback: Nov 23rd
  • @tlavi: Create an MR to add Job Statements to the handbook. Due Date: Nov 25th

cc @jmandell @david

Edited by Tali Lavi