[go: up one dir, main page]
Skip to content

Import stage — JTBD

Overview

The goal of this issue will be to create and iterate on the Jobs to be Done and their corresponding job stories for the Import stage. Our goal is to utilize the jobs theory to better understand our buyers' and users' needs. As part of the product development workflow, we will select prioritized job stories for problem and solution validation. We will then move the validated solutions to the build track, and launch the feature.

Currently there are no JTBD documented for the Import stage.

Goals

Create and validate JTBD for the Import group.

Utilize JTBD and job stories to:

  • Understand our users' motivations
  • Validate identified use cases and solutions
  • Continuously test and iterate features to ensure we are meeting our customers' and users' needs.
  • Create a transparent view for our stakeholders into the current and future state of the product.

Challenges

  • (Our assumption is) Importing is a one-time task, so it might be hard to speak to customers close to the action.
  • There isn't a large amount of existing research in this area.
  • There may be many job stories that need to be validated. We will need a good way of deciding which to bring into the validation track.

Links and resources

Handbook

Existing issues/comments

The following comments, epics and issues contain useful context and inspiration.

Existing research

Edited by Dan MH