← to blog

Telling a good Job Story. User Story alternative to uncover user’s voice

User Stories are considered a standard for the requirements catching. I see them mentioned in every open job. You have to tell them if you want to be a PM, PO, or a BA. But what if I tell you they’re not the only and they’re not the best to catch the value of a new feature?

The next text heavily cites Evan Zamesin, a Russian enterpreneur and JBTD researcher. I respect his approach to study and uncover new knowledge and thank Evan for showing me the Job Stories value and usage on his course.

The main issue of a User Story

User Stories exist in IT for a pretty long time (I have already mentioned, that they’re the standard now). I always thought they were first introduced in 2004 in the book “User Stories applied”, but Wikipedia says the come from 1997 [1]. User Stories are written in a specific an short form: “As %stakeholder%, I want %solution%, so that I %value%”. The problem, in my opinion, is that this format doesn’t catch a lot of context for the ‘story’ and that is why we add lots of other info to a Jira entity.

And this flaw is solved by the newer format (year 1999 according to Wikipedia [2]) called Job Stories.

Just mentioning other ways to catch the customer’s value

  • Gherkin Scenarios allow us to describe usage scenarios in all details. They concentrate on solution, and forget need and value — but speaking sincerely Gherkin is not built for it [3].
  • Acceptance criteria say us what qualities should a feature contain in order to be good enough [4].
  • Use Cases show how a feature should work, who uses it, and the flows, ‘unhappy’ scenarios are included [4].

Attempting to define the Job

Russian product manager and entrepreneur Evan Zamesin says, that a job is an aim created by our brain to satisfy a deep psychological need [5]. Zamesin mentions also, that a catching person’s psychological need is something only an experienced UX researcher could catch, as they lie deeply under many layers of a person’s life, trauma, and other experiences. Job at the same time are located not far from the ‘highest’ layer and can be easily caught by a researcher.

For me Zamesin’s definition doesn’t work from first and even second reading, so I tried to find some synonyms. And we can use Job meaning Task and Sub-Task. Look at this phrase by Van Neistat who is not an IT or product person: “They start: looking for their keys, lacing up their shoes, opening Google Maps — all the hundreds of little tiny JOBS they have to do to get there on time” [6]. He uses the term Job exactly in a sense of a task: this is what has to be done in order to complete a bigger task (job).

Job stories are written based on interviews’ results. Interviewee indicates all the parts of a statement during the interview. That is why in the next parts of the article I will use term ‘interviewee’ instead of ‘user’ which is more traditional and familiar to an aspiring researcher’s ear.

Recruiting a product (solution) and creating solution’s value

Jobs to be done is based on one important idea that is worth mentioning [7]. People recruit product to complete jobs. If an existing solution doesn’t work well or has issues, people tend to open the job and start looking for better candidates. When found, they move to it. Why could someone move to another solution? Let’s take a look on some (not all!) mechanics you could use to create value of your product.

1. Kill unnecessary jobs needed to get the job done [5]

New solution’s value could consist in having less smaller jobs needed to accomplish the initial one. For example, when I send something using Polish InPost service I tend not to print the label: they allowed sending without adding the label. That eliminated a job (or the job was given back to the service) and makes less steps to complete the initial one. Saves time and nerves (and sometimes even money).

An example could be catering services, they have : When I want to eat healthy food AND I don’t want to spend time cooking (I don’t know how to prepare food, I don’t want to select what to cook), I want my dish to be delivered to me, so I can

2. Uncover new jobs [5]

Zamesin calls this type of Jobs ‘sleeping’ [5]. A customer, future user doesn’t know that these even exist and that they would need something for this need. This same notion is also mentioned by Drucker. He says: “Markets are not created by God, nature, or economic forces but by businesspeople. … The want may have been unfelt by the potential customer; no one knew that he wanted a Xerox machine or a computer until these became available. There may have been no want at all until business action created it — by innovation, by credit, by advertising, or by salesmanship. In every case, it is business action that creates the customer” [8].

There is no way to systematically uncover sleeping jobs. This combines a lot of factors like luck, entrepreneur talent, and just having good skills of observation. If you find a way to uncover these type of jobs, I could only congratulate you: you’re a millionaire now.

3. Get rid of ‘tax’ jobs [5]

Tax jobs are those that a person does saying ‘meh’ instead of ‘yeah’. When you get rid of it, more ‘yeah’ could appear, or at least less barriers are encountered in your product. If we get back to the AirPods, then Apple has removed wires: now you don’t have to unravel them before talking. They also added a better mic so that you don’t have to hold the mic right way to be heard.

4. Open new segments for the same jobs [5]

When you already have your product, you can make segment pivot to completely change your user persona. But you can also enhance your persona vision by adding a new segment and incorporate their jobs into your product. Going to AirPods again. Apple has added new segment by adding Pro and Max products to their line. Fun fact: IT people hire AirPods Max so that they look better on calls, not for any quality like reason (someone has made a research on it).

5. Add new jobs to your product [5]

Probably, the simplest one. When you already have a product that covers some set of jobs, you can (probably) make this product better by enhancing it with more jobs it covers for users.

Job Stories: a framework to describe jobs

Job Story consists of three main parts: when, want, so [5]. Additionally, a good Job Story could contain details like solutions already in use and issues of these solutions.

Examples:

When an order is submitted, I want to see a warning message so I can avoid resubmitting the order.

When I am looking for a new place to live AND I have a dog AND I live with my partner, I want to find a place to live that will close all my needs, so we can have a good level of life.

When I don’t have enough money AND I see a new pair of shoes AND I am having an important meeting in real life I want to buy that pair So I feel confident about the meeting.

When

“When” is where we describe the context where the interviewee exists. This person is not a usr yet: our solution may not exist, but in their context they already have the pain and already do this job. In context we can place emotion (When I am sad…), economic or life state (When I have no money on my account OR When I am looking for a new flat…), or any other things describing context where the interviewee lives (When we’re a family with three kids OR When my relationship with my boyfriend are being destroyed). You can also combine the “contexts”: emotions + economic state + any other things. The only rule here is: the more information we have here the better [5].

Want

“Want” part represents the understandable results which a person wants to get in the context specified previously. These are the exact state interviewee wants to achieve when they’re in the context specified previously. Unlike in User Stories, this part can but mustn’t concentrate on the solution. It is exactly about the need or a problem a person has and wants to ‘heal’.

So

This part shows why the want part is actually needed. It may unveil a higher-level job or need. Like ‘be happy’ or ‘feel good’. But in real life you will likely not see examples like these. They will be precise, but will still identify a higher-level job for you.

When I finish my article…

When I finish my article AND I tend to do UX research job I want this article to be helpful to my readers, so I feel like I’ve done good job.

Hope I’ve demonstrated the value teams could gain from using Job Stories for their product’s backlog. I also hope that more teams will use interviews as a cheap and fun method to gain data on their products. Thanks for reading.

Sources

  1. “User Story”, — Wikipedia. URL: https://en.wikipedia.org/wiki/User_story
  2. “Outcome-Driven Innovation”, — Wikipedia. URL: https://en.wikipedia.org/wiki/Outcome-Driven_Innovation
  3. “Agile Extention to BABOK Guide. 2nd edition”, — IIBA.
  4. “Business Analysis Body Of Knowledge. 3rd edition”, — IIBA.
  5. “How to make a product, a course”, — Evan Zamesin.
  6. “Your tardy friends suck. 7 Principles”, — Van Neistat. URL: https://www.youtube.com/watch?v=Hm4mr7jzSpQ
  7. “Data-driven Product Management Simulator”, — Go Practice.
  8. “The Essential Drucker”, — Peter F. Drucker.

Originally published on Medium on October 18, 2023.

— Aliaksei