jobstories   31

The forces at work when choosing a product
A quick overview of the progress making forces diagram, a crucial component of the jobs-to-be-done framework.
jobstobedone  userstories  jobstories  diagram 
february 2018 by garrettc
5 Tips For Writing A Job Story
"A Job Story is a powerful way to facilitate team conversation and discovery when designing products. They are meant to cut right to the job to be done by eliminating distractions. The job story encourages the product’s design process to focus on context, causality and motivations instead of assumptions, subjectiveness, personas and implementations."
agile  jobstobedone  jobstories  business 
february 2018 by garrettc
User, Job, and Epistemic Stories
"The whole idea is to provide a greater understanding of the design problem without leading the design. Even the best designed proverbial cart works better behind the horse. By listing an action, the temptation to micromanage a designer is high."
userstories  jobstories  agile  webdevelopment  business 
february 2018 by garrettc
5 Tips For Writing A Job Story – Jobs to be Done
Job Stories can only come from real customer interviews. Before designing a feature or new product, you must talk to real people and uncover all the anxieties and contexts which were in play when they used your or a competitor’s product. If you are interested in learning about techniques on how to conduct an interview, listen to the The Mattress Interview with Chris Spiek and Bob Moesta. Chris, Bob and Ervin also have a Udemy course on jobs-to-be-done customer interviews. Design Modular Job Stories Which Features (Solutions) Can Plug Into. When designing job stories, it’s important to not commingle them with solutions. This is another important distinction from user stories which encourage defining implementation.
agile  ui  ux  jobstobedone  jobstories 
september 2017 by dlkinney
The Effectiveness of Job Stories
To designers, job stories are the most effective tool to understanding the user and the problem that they need solved. We should never think that the app we are designing is, in and of itself, the thing that the user wants or needs. What we can only hope to do is to provide them with a tool that is the best, given all of the constraints, at delivering the outcome the user desires.
jobstobedone  jobstories 
june 2017 by dlkinney
Twitter
The process of building has a lot in common with . Interesting approach
uxbri  JTBD  jobstories  affinitydiagrams  from twitter_favs
november 2016 by smack416
How we accidentally invented Job Stories - Inside Intercom
Personas have their place. In political environments where people only pay lip service to customers actual needs, I found them useful to get buy-in; they can drive a stronger connection to actual users of a product.

But personas are;

laborious to create well
focus too much on the differences between people
and are hard to remember and reference.
Turns out:

many people with diverse attributes have very similar motivations
those motivations are fast to research
and the focus on what you build can be captured in a series of short, memorable sentences.
If that doesn’t convince you, remember that personas artificially constrain the total market for your product. We’re all in on Job Stories.
productmanagement  productdevelopment  personas  critique  jobstories  jobstobedone  author:PaulAdams  Intercom  2016 
july 2016 by inspiral
Replacing The User Story With The Job Story — Jobs To Be Done — Medium
Bit of a straw man argument, but the JOB Stories seem valuable in and of themself.
agile  userstories  jobstobedone  jobstories 
november 2015 by boxman
The forces at work when choosing a product
For someone to move from their existing behavior (a product they’re currently using) to new behavior (switching to a new product), there are two types of forces at work: progress-making forces, and progress-hindering forces. Progress-making forces move people from their existing behavior to the new behavior, and consists of the push of the current situation (things they’re not happy with in the current product) and the pull of the new idea (things that sound appealing about the new product). Progress-hindering forces, on the other hand, hold people back from switching to new behavior. It consists of allegiance to the current behavior (things they really like about the current product) and the anxiety of the new solution (worries about learning curves and not being able to accomplish their goals with the new solution).
design  change  ux  requirements  jobstobedone  jobstories 
april 2015 by dlkinney
Replacing The User Story With The Job Story — Jobs To Be Done — Medium
I’ve come across a great way to use the jobs to be done philosophy to help define features. I call them Job Stories. The idea comes from the really smart guys at intercom. Here is what is they say: "We frame every design problem in a Job, focusing on the triggering event or situation, the motivation and goal, and the intended outcome: 'When _____ , I want to _____ , so I can _____ .'" For example: When an important new customer signs up, I want to be notified, so I can start a conversation with them.
agile  ux  design  userstories  stories  requirements  jobstobedone  jobstories 
april 2015 by dlkinney
Converting To Jobs Stories
We have used user stories as part of our design and development process for many years. You could find several mentions of them throughout our playbook. We used user stories to give designers and developers context to the problems that the user is having and give space for them to solve that problem while building the product.
agile  ux  jobs  stories  thoughtbot  user  requirements  jobstobedone  jobstories 
january 2015 by dlkinney

related tags

2016  affinitydiagrams  agile  author:pauladams  business  change  critique  design  diagram  dropbox  experience  intercom  interesting  jobs  jobstobedone  jobstory  jtbd  leanux  management  methodology  personas  process  prodmgmt  product  productdevelopment  productmanagement  requirements  stories  talks  thoughtbot  ui  user  user_needs  usercentereddesign  userstories  ux  uxbri  videos  webdev  webdevelopment 

Copy this bookmark:



description:


tags: