JTBD for Authentication
What did we learn?
Results |
---|
1-3 job stories |
Dovetail Project link, FigJam link |
What is Jobs to Be Done (JTBD)?
Jobs to Be Done (JTBD) is a framework that describes the user's intention when user a solution for a problem. We use the JTBD Canvas to organize all the job elements to get the most out of the framework. The JTBD Canvas can inform category maturity scorecards, usability benchmarking, heuristic evaluation, UX themes for roadmaps, and more.
The output of this issue, a JTBD Canvas, must be product-agnostic to get the most use of the framework. This means the job statement, needs, and process will be written without GitLab features in mind so that we may later build innovative features in addition to iterative design improvements.
What's this issue all about? (Background and context)
This issue seeks to discover/validate the Authentication jobs.
What are the overarching goals of the research?
- Discover/Validate user needs and inform the new product strategic direction for the next 12-18 months
- Create a JTBD Canvas for
<Stage group>
, which describes the job statement, needs, process, and more.- A separate JTBD Canvas will be made for each job statement.
What research questions are you trying to answer?
- Understanding the desired outcomes and main job
- What action is the job performer doing?
- What is the job performer trying to achieve with that action?
- Understand the process of executing the jobs
- What are the beginning, middle, & end steps in the job?
- How does the job performer define success?
- Understanding the circumstances and related jobs
- In what situations does the job performer act differently?
- Are there any jobs that often overlap with this job?
- Are there any social or emotional factors that influence this job?
What are the assumptive Jobs to Be Done?
(Fill out as much as possible and repeat as needed)
1. Job Statement (Verb + Object + Clarifier)
- Persona: Developers
- Category: Error Tracking (GA)
- Feature(s):
- Desired Outcomes:
- Circumstances:
- Job Stories:
- When I am <circumstance>, I want to <job statement>, so that I can <desired outcome>
- Highlight of job steps:
- Beginning steps, middle steps, end steps
Source of information:
Confidence level: High/Medium/Low/No Idea
Note:
Who is the target audience?
The subject matter expert for the feature or group must answer: <@Stakeholder(s)>
- What job titles would you expect the user to have?
DevOps Engineers, CI/CD Engineer, etc...
- How does the user get the job done right now?
Job Statement
- Do you know if there are any other users to consider? *
What business decisions will be made based on this information?
A JTBD Canvas may be used to steer product strategy, shape the product design, and help define circumstances to validate against. See the How to Use JTBD at GitLab page for more information.
What, if any, relevant prior research already exists?
- GitLab's JTBD overview and deep dive handbook pages.
- Spread user-centered innovation process at GitLab (&11424)
- Job to Be Done Playbook by Jim Kalbach
Who will be working on the research?
Primary DRI: <@Stakeholder(s)>
Assist by moderating interviews: TBD.
Subject matter expert to provide contextual knowledge: TBD.
Will anyone be OOO during this research?
Who will be moderating and/or assisting with interviews?
Name | Timezone & ideal date range for interviews | Ideal number of interviews in that timeframe | Role(s) (moderator, note taker, both) |
---|---|---|---|
<UX Researcher w/JTBD Experience> |
|||
<@Stakeholder> |
Checklist
Assumptive JTBD information
(est. 1-2 weeks)
Part 1: -
Fill out as much information as possible in the assumptive job and target audience sections. -
Put assumptive JTBD information into copies of the script and screener templates. - Link to completed script
- Link to completed screener
-
Put assumptive JTBD information into a copy of the Assumptive JTBD Canvas template - Link to JTBD Canvas
Prepare for interviews
(est. 1 week)
Part 2: -
<@stakeholder(s)>
fill out the stakeholder availability section above -
Create dovetail project - Link to dovetail project
-
Finalize script and screener -
<@stakeholder(s)>
review screener -
UXR Team to review screener
-
-
Interview moderator(s) meet with UX Researcher w/JTBD experience -
Practice moderating JTBD interviews -
Review Assumptive JTBD Canvas
-
-
Create recruitment issue - Link to recruitment issue
Begin interviews
(est. 2-3 weeks)
Part 3: -
Launch recruitment -
Start interviews - If you have low confidence in the JTBD Canvas, the first 1-3 interviews will be focused on defining the main job statement and desired outcomes.
-
(optional) <@stakeholder(s)>
meet after the first 3 interviews to review presumptive insights. -
Finish 5 interviews -
Finish all interviews (8 - 12)
Summarize and share
(est. 1-3 weeks)
Part 4: -
Complete a JTBD Canvas for each participant -
Summarize all canvases into a completed JTBD Canvas -
Summarize answers for the remaining questions in the script -
Put completed JTBD Canvas into a copy of the JTBD Discovery Report - Link to report
-
<@Stakeholder(s)>
Review findings in the report -
Create report recording - Link to recording
-
Share findings in relevant Slack groups and meeting -
Put JTBD Canvas in the stage group's Figma folder -
Link Figma file in in roadmaps and applicable handbook pages -
Put job statement, desired outcome, and circumstances in results section -
Close issue